On Tue, Mar 27, 2007 at 08:51:02PM +0200, Frank Ellermann wrote:
| If the <target-name> after macro exapnsion is a single label
| (e.g. a top level domain ) with or without trailing dot, or
| an invalid domain (e.g. strings with adjecent dots), then the
| corresponding mechanism does not match.
This is weird. We're writing an add-on for email, not for RFC2821.
A domain is a domain. There's nothing special about a TLD, except
that it is not allowed to be all numeric. Please see the relevant
RFC, first listed normative reference in RFC4408.
According to STD1, SMTP is defined by STD10, currently RFC821.
2821 is a proposed standard only, and is currently under debate.
What if the RFC2821bis people suddenly change their mind and do
allow "user(_at_)ws" ?
The possible outcome:
(where I write 2821bis, I do mean 2821bis or an successor).
a) 2821, nor 2821bis, makes it. 821 allows TLD domains.
b) 2821bis makes it, but modified, not banning TLD domains.
c) 2821bis makes it, including banning TLD domains.
Should SPF be corrected to conform with STD13 (RFC103[45]) then
all three cases are covered (outcome c is not to be fed to SPF,
but would work nevertheless if it does reach SPF).
Should SPF not be corrected, then two out of three will mean
SPF is incompatible with the official internet protocol standard.
DNS caching should take care of "myhome" type of names. True, SPF
would do another query but a nearby cache will answer it after
this was cached when the SMTP server tried to verify this name
(HELO myhome) or this maildomain (MAIL FROM:<user(_at_)myhome>).
Alex
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to http://v2.listbox.com/member/?list_id=735