wayne wrote:
I don't think RFC4408 says type99 (SPF) is preferred over TXT.
It is hidden in the "Selection Records" section 4.5 logic:
2. If any records of type SPF are in the set, then all records of
type TXT are discarded.
Yes, but that's a scenario where both queries got replies. The
theory here is that the TXT records might be less complete than
the SPF records because there's more than only SPF you can do
with TXT.
In another article you said that TXT might result in a PASS and
SPF in FAIL (or v.v.), that's true but the problem of the sender,
publishers are supposed to create equivalent policies.
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 ".
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.
If the sender has an old TXT RR, they're supposed to publish an
equivalent "v=spf1 " as TXT RR, if they have a "v=spf1 " as SPF
RR. Therefore if their TXT reply has no "v=spf1 " it's the same
situation => NONE, no later TempError for an SPF-timeout.
In other words the TempError is limited to those cases where old
implementations check only TXT. New 4408 implementations query
both RR-types (simultaneously or sequentially), and then they'd
see either the TXT or the SPF without "v=spf1 " as above => NONE.
If a 4408 implementation says TempError both queries timed out.
Does that make sense ?
Frank
-------
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