Home | Sitemap | Recent Changes | Login

SPF Logo

Sender Policy Framework

History of FAQ/Common receiver mistakes


Revision 5 . . (edit) 2008-04-12 10:51 (UTC) by Frank Ellermann [typo reported by Terry Zink]
Revision 4 . . (edit) 2007-05-17 14:40 (UTC) by Alex van den Bogaerdt [Changed title]
Revision 3 . . (edit) 2007-05-17 14:36 (UTC) by Alex van den Bogaerdt [added TOC entry; elaborating a bit]
Revision 2 . . 2007-05-17 14:01 (UTC) by Scott Kitterman [Added forwarder whitelisting.]
Revision 1 . . 2007-05-17 13:50 (UTC) by Alex van den Bogaerdt [Common mistakes, part deux]
  

Difference (from prior major revision) (minor diff, author diff)
Paragraph 1Paragraph 1

== Common mistakes when using an SPF record

== Common mistakes when checking incoming mail for SPF compliance

Paragraph 3Paragraph 3

* [[#border-only|Process SPF policies at the right place]]

* [[#border-only|Process SPF policies at the right place]]

* [[#whitelist|Checking SPF On Forwarded Mail]]

* [[#best-guess|Guessing is OK, provided that...]]

* [[#best-guess|Guessing is OK, provided that...]]

Paragraph 18Paragraph 19

* (for SPF: ) the sending host is your MX server, not the original contacting server

* (for SPF: ) the sending host is your MX server, not the original contacting server

===[[##whitelist]]Checking SPF On Forwarded Mail

Mail forwarding is set up by the receiver and so for forwarded mail, the border mail server (at which SPF should be checked) is the forwarder's mail server.  If you check SPF on your mail server it is coming from your forwarder and not from a mail server authorized by the sending domain.  Technically this is similar to checking SPF against mail relayed from your secondary MX like discussed in the previous item.  Authorized forwarders should be whitelisted against SPF checks to avoid this problem.

===[[##best-guess]]Enabling a "best guess" mode

===[[##best-guess]]Enabling a "best guess" mode