-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Levine wrote:
In this case, the problem is that the recipient system is using a
broken authentication scheme that rejects useful mail that it should
accept. Fans of SPF keep trying to redefine SPF's failure cases to be
the fault of people who send mail in ways that SPF can't handle,
rather than as a failure of SPF.
I have as poor opinion of the SPF koolaid as even you, John.
But, DKIM and virtually any other message authentication method would
fail in this too.
This is really no different than sticking a spam filter up in front of a
spam reporting address, or content munging inbound signed email, and
expecting it to pass signature checking.
Application design error.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows 2000)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQCVAwUBRBro/p3FmCyJjHfhAQIbPwP/UZWFLKc06ZwhSMaccopXTMDSToHQRymh
Wyek+cohlnbg9dWJohg6WCC0j71SelJj4T2lM4rhIMK5UZFhYHQkrcvqD2coSZc5
NYrvAjFHqCZFS0CB5uIpYGl2uSZLld0OE4A58dznNmhxePBecBs1Brds1d6fpdF1
BxeiPybWw9k=
=3dSL
-----END PGP SIGNATURE-----
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg