In
<Pine(_dot_)LNX(_dot_)4(_dot_)21(_dot_)0303062356410(_dot_)16780-100000(_at_)spiral>
Nate W <asrg(_at_)natew(_dot_)com> writes:
I've heard a similar objection to simple confirmation whitelists, and my
answer is "feature." If the sender values the message so little that they
won't do something simple to get it through to me, then there's no reason
that I should value it enough to read it.
One idea I have heard of to make this kind of system much more useful
in practice is to run a spam scanner (such as SpamAssassin) on the
email. If the email is classified as not-spam, don't send the
confirmation request.
The occasional false positive means that the sender has to jump
through a hoop. If your confirmation message explains that the spam
filter detected it as spam and why, people are going to be much more
understanding about why they are being requested to jump through a
hoop.
The occasional false negative means you need to blacklist that person.
Of course, SpamAssassin already has auto whitelists/blacklists.
-wayne
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg