Even worse, users will learn what the button means by the effect (they
think) they obtain by hitting it, which may vary.
Web mail has had spam buttons for years, and the users seem to have
figured out how to use them. Can you explain exactly how the issues
with a spam button in a MUA would be different?
Regards,
John Levine, johnl(_at_)iecc(_dot_)com, Primary Perpetrator of "The Internet
for Dummies",
Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor
"More Wiener schnitzel, please", said Tom, revealingly.
I'd consider bringing up a confirmation dialog when disambiguation is
needed.
End-users can be a poor judge as to what is spam. Abuse desks receiving
complaints of unwanted email need to ascertain whether there is evidence
of spam, such as content clearly in the commercial interest of the
sender, and not the recipient, etc.
One key point is to establish which complaints require human
inspection and why. This can be done better deploying collaborative
interchange with trusted senders.
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg