If Yahoo!, aol, MSN, hotmail, and comcast were to implement it, 90% of whom
I correspond with would be covered, excluding my mailing list buddies of
course! Also, there would be no messages from fake yahoo.com addresses
littering my mail box.
If you authenticate on envelope from there'd be no email messages
with a fake yahoo.com email address in the envelope. What goes in
the Return-Path: and From: is an entirely different matter. If you
authenticate on the headers you've got a major problem with
acceptance. I suspect Hotmail and Yahoo would actually fight the
system, since a large percentage of their users are probably sending
from their ISP, but using the web mail address as the return address.
> work and pay the cost. That's why I'm focused on the idea of
requiring authentication only for bulk mailers, and using existing
tools to identify what messages are bulk. I'm not convinced that it
will work. But I am convinced that it applies the changes in the
places where people are incented to make them.
The problem is, who is a bulk mailer? I can change my identity. What
messages are bulk? There are a lot more holes in that tin can than my idea.
I can vary the message a little for each destination. I can inter-twine
several different messages (porn, penis enlargement, fat reduction, repeat)
to throw off your detection. How are you going to force me to play by your
rules? Why should I care to play by them in the first place if my messages
end up in the trash can?
The mechanism assumes that we can successfully defeat checksum
breakers for long enough to bring more complete authentication on
board. I'm not sure if that is true or not.