[89906] in North American Network Operators' Group
Re: Spam filtering bcps [was Re: Open Letter to D-Link about their NTP
daemon@ATHENA.MIT.EDU (Matthew Sullivan)
Wed Apr 12 08:16:30 2006
Date: Wed, 12 Apr 2006 22:11:49 +1000
From: Matthew Sullivan <matthew@sorbs.net>
In-reply-to: <bb0e440a0604111950x37cc11d6wb95488a4d3896e47@mail.gmail.com>
To: Suresh Ramasubramanian <ops.lists@gmail.com>
Cc: Matthew Black <black@csulb.edu>, nanog@merit.edu
Errors-To: owner-nanog@merit.edu
Suresh Ramasubramanian wrote:
>On 4/11/06, Matthew Black <black@csulb.edu> wrote:
>
>
>>Are you suggesting that we configure our e-mail servers to notify
>>people upon automatic deletion of spam? Frequently, spam cannot be
>>properly identified until closure of the SMTP conversation and that
>>final 200 mMESSAGE ACCEPTED...or do you think that TCP/IP connection
>>should be held open until the message can be scanned for spam and
>>viruses just so we can give a 550 MESSAGE REJECTED error instead of
>>silently dropping it?
>>
>>
>>
>
>You can reject right after DATA, at the <CR><LF>.<CR><LF> stage, before QUIT
>
>That's still an in line smtp reject rather than an accept + bounce DSN.
>
>Exim with the spamassassin patches (sa-exim) does this, for example.
>
>-srs
>
>
Of course Postfix can be setup (using spampd) with spamassassin to do
exactly the same.
I believe Sendmail+MimeDefang+Spamassassin will also reject inline if
set to do so.
Regards,
Mat
