-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wayne Schlitt wrote:
The "SHOULD reject on PermError" is a creation from the MARID process.
While may are arguing that it is the right thing to do, I am more and
more convinced that it is a very wrong thing to do.
Well, I could be convinced to agree to "SHOULD be treated similar to None",
but certainly not to "MUST". It's receiver policy, and trying to strictly
prescribe it is of no use, because receivers simply won't care.
Given that all specs say PermError MUST be treated as None, the only
thing that would convince me to change this would be strong evidence
that existing implementations don't treat PermError as None.
SPF implementations do not "treat" result codes, they just return them.
As for MTA solutions (AKA receiver policy implementations), I don't think
any of those actually hard-code how SPF result codes are being treated.
My personal solution, using Courier MTA plus Courier::Filter, for
instance, is configured to reject on TempError (SMTP 4xx) and PermError
(SMTP 5xx).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD4DBQFCj1EkwL7PKlBZWjsRAqp0AJjen5xIBRl2UYWf3rzfnOea/O/SAJ9s/EUR
nhrpOwhYrYmuwTF/gu/ikw==
=3e4T
-----END PGP SIGNATURE-----