On Tue, 27 May 2008, Frank Ellermann wrote:
I'm not sure about your statement. Of course receivers can check
whatever they like. They just have no business to say "nxdomain"
when they got "nullmx", "SPF FAIL", or anything else that is not
the same as "nxdomain".
I am talking about checks such as recognizing MX 0 . or treating
MX-points-to-RFC1918 as invalid.
Arguably these checks are fine, but they are no part of ADSP, and
I don't get why anybody would wish to say "ADSP result nxdomain"
when it actually is some kind of "bogusmx". Why not simply reject
"bogusmx", and don't bother to check ADSP ?
You seem to be arguing that if an implementer thinks the NXDOMAIN check is
too weak, then they should use whatever validity check they think is
suitable.
That is what draft-levine-dkim-adsp-00 says.
The whole point of ADSP's domain validity check is to define when an
implementation should not bother to check ADSP.
Tony.
--
f.anthony.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
BAILEY: EASTERLY 4 OR 5, INCREASING 5 TO 7. SLIGHT OR MODERATE, INCREASING
MODERATE OR ROUGH. SHOWERS. MODERATE OR GOOD.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html