spf-discuss
[Top] [All Lists]

[spf-discuss] Re: spam.co.nz

2006-08-30 10:58:02
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex van den Bogaerdt wrote:
Not resulting in a permerror but wrong nevertheless is the absence of a
catch-all (for instance -all) after include. 

How is a missing catch-all "all" wrong?  It isn't.  After the last 
mechanism has failed to match, and if there is no "redirect=" modifier,
a default "?all" is assumed.  See section 4.7 of the SPF spec.

Monte Hansen wrote:
I'll change it to throw permerror during parsing since the spec says
"SHOULD always use either a 'redirect' or an 'all' mechanism".

No, don't do that.

v=spf1 a mx ptr include:activehost.com\000

I ignore trailing nulls. In Windows, everything above the Win32 API
layer do this automatically. At the Win32 layer, it comes naturally to
strip trailing nulls since strings are generally null terminated.

That's wrong.  That way you accept SPF records that are rejected legiti- 
mately by standards-compliant SPF implementations.  That will only cause 
confusion, so don't do it.  Broken SPF records ought to be fixed sooner 
rather than later.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE9dFawL7PKlBZWjsRAuCOAJ9ffjKpfGkNZ+HJ1HL7lzA7FdgDAACguQf9
rPMW7lXnUI1f4meZMPnfQgQ=
=gwWM
-----END PGP SIGNATURE-----

-------
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com

<Prev in Thread] Current Thread [Next in Thread>