Inventory hosting mail, website applications, marketing services and any remote mailbox provider. Check authoritative DNS and save the current TXT policy. Different domains on one account may require different policies.

1. Open Administration > Mail Options > SPF and inspect the existing configuration.
2. Review the form’s scope carefully: the documented SiteWorx editor uses Update All Domains. Do not apply one policy across domains with different sending services.
3. Where a shared policy is correct, use the standard SPFv1 wizard or a validated advanced value. Include only authorised senders and avoid the obsolete PTR mechanism.
4. For a domain-specific policy or externally hosted DNS, edit the single intended TXT record at the authoritative DNS service instead. Merge required mechanisms into that policy rather than adding another SPF record.
5. Verify the public TXT response and send test mail through each legitimate route. Review the receiver’s authentication results and SPF DNS-lookup limits.

There should be one valid SPF policy at the relevant name, and authorised sending paths should pass. Unrelated TXT records must remain intact.

If mail fails after a change, compare the actual sending IP and envelope domain with the policy. Revert the specific incorrect change while investigating. SPF alone does not guarantee inbox placement or establish DMARC alignment for every message.

No. Multiple SPF policies at the same name cause an evaluation error. Combine the required authorised mechanisms into one valid policy within the lookup limit.

• Enabling and publishing SiteWorx domain signing records
• Adding a monitored DMARC policy through SiteWorx
• Moving SiteWorx domain email to a remote provider
• Deleting a SiteWorx mailbox without losing needed messages

• InterWorx: How To Create An SPF Record
• RFC Editor: Rfc7208