-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 4, 2007, at 3:38 PM, Keith Moore wrote:
the problem I have with DKIM filtering is that it is only effective for domains that can reasonably insist that all of the mail originated by users at that domain go through that domain's submission servers. this is a corner case, not the general case. sure the spammers will learn to not use DKIM domains, but they'll just move to other domains, and the vast majority of domains won't be able to use DKIM without seriously impairing their users' ability to send mail. of course, some of the large ISPs and MSPs like it that way.
well, at some point it seems to me that we can take the next step, which is to require all email to IETF lists to be signed. Offer to accept DKIM, Microsoft's (as in "gmail"), PGP, and S/MIME, but require the signature and require it to verify.
We're probably not yet at that point, but for companies that follow the kind of policy in question, we can take a step.
-----BEGIN PGP SIGNATURE----- iD8DBQFHBUsNbjEdbHIsm0MRAnojAKD5IKz4vVvaZ5Qm7JImgxfHzNPmMACeJt5K /45ux7qbMKmV2CdbBK7acSg= =N1+N -----END PGP SIGNATURE----- _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf