-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Scott Kitterman wrote:
Julian Mehnle wrote:
It is practically impossible to predict how people are going to react
to PermError/Unknown. As for a practical solution to this user's
problem, he could manually include the semantics of the GoDaddy record
in his own record.
We you all will hopefully decide tonight, but if you don't know what the
sender policy is, I don't see how you do anything but admit that SPF
gives you no answer and move [on].
Neither publishers nor we as the spec designers are supposed to
second-guess receivers. What we as the spec designers need to do is to
precisely define the meaning of the record syntax and of the result codes.
Based on that, receivers can precisely determine what a result means with
regard to a given message, and then decide what to do about it.
I don't think publishers need to know exactly how receivers are going to
handle the various result codes. I mean, in order to say "this message
abuses my identity" or "I can't tell you whether this message is legit", I
don't have to know what the receiver is going to do about it. Also, for
the sake of my (i.e. SPF-as-a-whole's) credibility, I should not base my
declaration on what the receiver is likely to do.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCkSmAwL7PKlBZWjsRAsgIAJ90F8EfhfLObMQFEOHr8DumFuuhnACfYp4V
DumqtqaFpLjAneK1t+hyf5o=
=4N1h
-----END PGP SIGNATURE-----