SpamExperts setup
SpamExperts: SPF fails for outbound filtered mail
The envelope sender's SPF policy may not authorize the Hosted Cloud region or the Local Cloud delivery addresses.
The visible symptom is:
Authentication-Results: spf=fail smtp.mailfrom=example.com
Fix the SPF failure
- Read smtp.mailfrom or Return-Path and the connecting IP from a failed message.
- Confirm whether outbound filtering uses Hosted Cloud, a specific region, or Local Cloud.
- For Hosted Cloud, use the documented include for that route. For Local Cloud, authorize the public addresses that actually deliver mail.
- Merge the value into the existing v=spf1 TXT policy before the final all mechanism.
- Keep one SPF policy and preserve all other active senders.
- Send a new message and confirm spf=pass for the same envelope domain.
Common causes
The wrong regional include was used, the record contains the old route, the value appears after -all, or a second SPF policy was created.
What the check proves
MailFixIt can find public SPF syntax errors, duplicates, missing dependencies, and unauthorized resolved addresses. It cannot confirm the SpamExperts outgoing user or SMTP route.
Frequently asked questions
Which SpamExperts SPF value should I use?
Hosted Cloud commonly uses include:spf.antispamcloud.com, with regional alternatives. Local Cloud owners must authorize their own actual outbound addresses.
Does a correct DNS record prove the provider is using it?
No. The provider must also activate the matching route or signing policy. Confirm the result in its console and in a new message.
Related email diagnostics
Primary sources: SpamExperts: set up SPF.