On Wed, 28 Mar 2007 17:17:00 +0200 Frank Ellermann
<nobody(_at_)xyzzy(_dot_)claranet(_dot_)de> wrote:
Alex van den Bogaerdt 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.
Weird or not, it's consistent with <domain-spec>. And we can't
change <domain-spec> _again_, the last AUTH48 mutilation was bad
enough. I begin to hope that this change didn't break older SPF
implementations, AFAIK nobody reported problems with SPF policies
using the optional trailing dot in <domain-spec> so far.
Not all implementations support the trailing dot. Libspf is at least one
that does not.
Scott K
-------
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