-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Julian Mehnle wrote on spf-devel:
We were talking on #spf.
FYI, I brought up there the fact that Mail::SPF was generally RFC-
conforming except for one odd case:
| Currently, Mail::SPF ignores DNS errors on the SPF-type look-up but
| fully escalates them on the TXT-type look-up. So if "all look-ups
| that are made" get a DNS error (other than NXDOMAIN) or time out, then
| Mail::SPF does the right thing because the TXT look-up will throw a
| TempError.
|
| If at least one record is returned by the SPF-type look-up, no
| TXT-type look-up is performed (so nothing can go wrong with the
| TXT-type look-up in the first place).
|
| However, if the SPF-type look-up succeeds and returns 0 records, and
| the following TXT-type look-up errors or times out, then Mail::SPF
| throws a TempError even though it shouldn't.
I fixed this tiny bug already. Because it is so tiny, I won't make
another release immediately just for that.
FYI, this has now been fixed with the 2.003 release of Mail::SPF. From the
changelog:
| * Fixed a very minor bug where a "TempError" result would incorrectly be
| returned in the very rare case when the SPF-type look-up succeeded but
| returned 0 records, and the following TXT-type look-up errored or timed
| out. Now a "None" result is correctly returned in that case as
| demanded by RFC 4408.
While I'm sure this is what the spec requires, I'm no longer sure this is a
sensible behavior. Which means that there is probably a bug in the spec.
Any comments?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFpDaswL7PKlBZWjsRAnSWAKDDjUNhIRlFJ8nzbproqT1k4xyaDwCfRUr/
Ziv9vG9lz75PiacJpoSpZbU=
=OTX0
-----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/?list_id=735