North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Spam filtering bcps [was Re: Open Letter to D-Link about their NTP vandalism]

  • From: Suresh Ramasubramanian
  • Date: Tue Apr 11 22:51:47 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=Wraw+KDVLz1+ovHU+hLnY5ztpAxIhuAn1AtI5VUDD5wP/aXGsfFYMoMw7vup5COFdc7zrnxBvGNqmcYphGy32cN3tUc8PGaTRdxghe4oRVluDWipwTjfM2v379z+cyp1rSshLNJkHcHrGYrB5TsKQweAFS1cth/dk/C4rQBBdnI=
On 4/11/06, Matthew Black <[email protected]> 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