On Tue, Nov 25, 2003 at 05:36:47PM -0000, Aaron Stone wrote: > It's something that end users, who are writing their Sieve scripts or using > interactive web happy Sieve editors, should take into account! It's not > something that I would want to ban programmatically, however, because of the > messy compexities and general klugey borkage it would involve.
I wasn't saying that tools like Sieve should prevent bouncing spam, but that administrators should prevent (or at least make it difficult) users from configuring their sorting rules to bounce spam. > Aaron > > > Bill Hacker <[EMAIL PROTECTED]> said: > > > Christian G. Warden wrote: > > > > > On Tue, Nov 25, 2003 at 04:57:59PM -0000, Aaron Stone wrote: > > > > > >>I believe that the best way to handle spam is by using an MTA based spam > > >>checker which adds identifying headers, prefixes the subject line, or > > >>otherwise marks the incoming email without disrupting the MTA path towards > > >>DBMail delivery. > > >> > > >>At delivery time, use a Sieve script to put all of the spam into a > > >>folder, or > > >>discard it, or keep it in INBOX, or bounce it back, or call you pager, > > >>etc. > > > > > > > > > You should *not* bounce spam as the sender is always forged (or often > > > enough that it's safe to say always). Either keep it, discard it, or > > > reject it at SMTP time. > > > > > > xn > > > _______________________________________________ > > > Dbmail-dev mailing list > > > Dbmail-dev@dbmail.org > > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > > > > > > > > Second the 'not bounce' as too often the spam-bastards even have clever > > forgeryways to utilize a mis-directed 'bounce' to propagate their garbage... > > > > Bill Hacker
