Re: [Asrg] Spam, defined, and permissions

> > > This is yet another reason why a fine-grained permissions-based
> > > approach, where the *recipient* can decide what E-mails they do and
> > > do not want to receive (based on who the sender is, and what the
> > > mail contains) is so decidedly the right way to pursue this problem.
> > So long as you are willing to spend an unlimited amount of money on
> > an e-mail infrastructure that accepts and stores terabytes of spam,
> Sorry, John, why would we have to accept and store all this unwanted
> mail?
Well, I didn't write what you responded to, but....

You'd have to accept it, and probably store it temporarily, because you
can't apply filters that test the content until you _have_ the content.
(I suppose you may be able to optimize that away for users that don't
have any content-dependent filters turned on, or if the user has an
"absolute" test (= "this is unwanted, no question" when it trips)
enabled that the mail fails before the content shows up.

If the message tests out as clearly unwanted, you don't need to store
it at all.  But I suspect few people would use that; most, I expect,
will want such mail not dropped on the floor, but rather put in some
kind of "spam folder", in which case you _do_ need to store it
semi-permanently.

Of course, that's a guess.  If anyone has any hard numbers for those
proportions, I'd love to see them.

/~\ The ASCII                           der Mouse
\ / Ribbon Campaign
 X  Against HTML               
mouse(_at_)rodents(_dot_)montreal(_dot_)qc(_dot_)ca
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg