Proofpoint Essentials setup
Proofpoint Essentials: SPF fails for outbound mail
The envelope sender's SPF policy may not contain the Proofpoint value assigned to the organization and route.
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 outbound mail is meant to leave through Proofpoint Essentials.
- Open Connection Details in Proofpoint and copy the current SPF value for your organization.
- Merge that value into the existing v=spf1 TXT policy before the final all mechanism.
- Keep one SPF policy and preserve every other active sender.
- Send a new message and confirm spf=pass for the same envelope domain.
Common causes
The Proofpoint value is missing, was copied from another region, appears after -all, was added to the visible From domain instead of the envelope domain, or was published as a second SPF record.
What the check proves
MailFixIt can expose duplicate policies, invalid syntax, broken dependencies, and unauthorized resolved addresses. It cannot prove which outbound route a historical message used.
Frequently asked questions
Which Proofpoint SPF value should I publish?
Use the value shown in Connection Details for your Proofpoint Essentials organization. Do not copy a value from another tenant or an old article.
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: Proofpoint Essentials: what SPF is and how to check it.