-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frank Ellermann wrote:
The issue in this thread is about errors, one of the two queries
times out or results in an error, and the other gets "something",
but no record starting with "v=spf1 ".
Right, if "something" includes an empty answer packet with 0 RRs.
What RFC 4408 requires has been explained somewhere else in this thread
already.
If the sender has a new SPF RR, then they obviously support this
new 4408 feature. So if they don't have "v=spf1 " they really
don't want it => NONE, no later TempError for a TXT-timeout.
That's what RFC 4408 requires. But the rationale isn't quite sensible.
What if the SPF-type answer packet is completely empty and the TXT-type
query times out? You don't want to return "None" in that case, do you?
In other words the TempError is limited to those cases where old
implementations check only TXT.
No. Not even RFC 4408 says that. If you check both TXT and SPF types and
both time out (or RCODE != 0 or 3), or if you just check the SPF type
(which is very well allowed), there is also a TempError.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFpQc4wL7PKlBZWjsRAjWAAKDmUdtg0eTdNe02mxTx2gg/02yyqQCgxXx8
7wSDIRTc0Sp4sh1Qi9Pz2yg=
=f1s0
-----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