Difference (from prior major revision)
(no other diffs)
Paragraph 50
Paragraph 50
The first rule would be activated by any from address ending with "@example.com", and would validate such an email only if it comes from an IP address associated with an MX record for "example.com". The second rule would be activated by a HELO identification of "mailserver.example.com", and would validate the email only if it comes from the IP address associated with that server.
The first rule would be activated by any from address ending with "@example.com", and would validate such an email only if it comes from an IP address associated with an MX record for "example.com". The second rule would be activated by a HELO identification of "mailserver.example.com", and would validate the email only if it comes from the IP address associated with that server.
Another reason to take HELO names into account has to do with [[#all-domains|Publish null SPF records for your domains that don't send mail]]. Suppose you follow the advice in that FAQ but don't think about HELO names, you could inadvertently deny servers the right to send email. An example: a cloud of webservers send email forms out, using "webform@example.com" as the sender's address. Each webserver uses (as it should) its own name as the HELO parameter.
> <pre>www.example.com. IN TXT "v=spf1 -all"
web01.example.com. IN TXT "v=spf1 a -all"
web02.example.com. IN TXT "v=spf1 a -all"
web03.example.com. IN TXT "v=spf1 a -all"</pre>
Eventhough there are no email addresses like "user@web03.example.com", the name "web03.example.com" <strong>is</strong> used for email!
If you don't publish an SPF policy for such domains, they are game for spoofers. And if you do publish an SPF policy, you better allow your host to use its own name.
=== [[##all-domains]] Publish null SPF records for your domains that don't send mail
=== [[##all-domains]] Publish null SPF records for your domains that don't send mail