On Tue, 25 Nov 2003 09:25:44 -0800, 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. >
If you are going to reject a message, then by RFC you should bounce it. Yes, most of the time the sender is forged, but it's that 1% of the time where the sender MUST be informed that their message did not reach the intended destination. Otherwise, you have not had a full accounting of the delivery. If you have sent someone's $10K contract into the bit bucket without letting the sender know, you will have a pretty p*d-off customer. Brian
