-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I will disagree with you there. DKIM allows the concept of a
corporate signature - "I'm Cisco and I know who my employee is" or
"I'm Yahoo and I know who my user is" - but it doesn't require it.
What it does require is that if you are not going to use the
corporate servers you need to provide and support the signature you
use. The former is, IMHO, an important step in scalability. The
latter is status quo with PGP and S/MIME.
On Oct 4, 2007, at 3:38 PM, Keith Moore wrote:
Hallam-Baker, Phillip wrote:
Absolutely, and in fact I see mailing list management as a natural
early adopter for DKIM filtering.
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.
frankly I don't think IETF should have backed a proposal that was so
unfairly biased toward a particular business model.
Keith
-----BEGIN PGP SIGNATURE-----
iD8DBQFHBUo8bjEdbHIsm0MRAj/5AJ9cUHumt53uReMxuHrxRvQeJCkvsgCg8UCq
I/+91c9ik2rREvhAwz1vMyk=
=G55s
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf