Re: domain literals
Frank Ellermann <[email protected]>
| Newsgroups | gmane.mail.spam.spf.devel |
|---|---|
| Organization | <URL:http://purl.net/xyzzy> |
| Message-ID | <[email protected]> |
Roberto Alsina wrote: > it's understood it should do that, but it's not explicit, unless I am > reading wrong (or at the wrong place): > 2.1. The HELO Identity [...] That might be a part of "oral history" (hidden in the list archives :-) that you've missed. At some point in time there was a draft saying that "weird" HELOs (also including domain literals) should be handled as PermError (or similar) because nobody wants them anyway. After some discussions that was dropped for several reasons: - The S in SPF is for "sender", not "receiver" - It's perfectly okay if a receiver accepts HELO [127.2.3.4] coming from a client with IP 127.2.3.4 - It's also okay if a receiver accepts domain literals where the IP doesn't match - And some receivers claim that they're even forced to accept crap like "oemcomputer" - As there is no "sender policy" for an IP, matching or otherwise, let alone for a "domain" oemcomputer, SPF is moot about this. - Receivers are free to do whatever they like, but they can't claim that IP literals or weirder HELOs are "SPF errors" Frank (still interested in two "HELO museum" test cases :-) ------- To unsubscribe, change your address, or temporarily deactivate your subscription, please go to http://v2.listbox.com/member/?list_id=1007