--On Friday, October 31, 2003 3:27 PM -0600 Bob Apthorpe
<[EMAIL PROTECTED]> wrote:
> You could track the IP addresses of systems sending you spam from your
> mail logs, drop those into a sendmail access list, then reject (5xx) or
> tempfail (4xx) those systems for an hour or so, and reject more
>
On Fri, 31 Oct 2003 11:30:29 -0800 "Josiah DeWitt" <[EMAIL PROTECTED]> wrote:
> I just installed SpamAssassin and got it working, but it just drops or
> marks spam after it has already accepted it. While this /dev/null type
> behavior is great, I would rather discourage spammers by refusing the
>
look at spamass-milter or a similar milter-level plugin to sendmail. They
can generally be configured to issue a 5xx level error at the end of the
SMTP DATA phase if the SA score is over some threshold level.
At 02:30 PM 10/31/2003, Josiah DeWitt wrote:
I just installed SpamAssassin and got it w
On Fri, Oct 31, 2003 at 11:30:29AM -0800, Josiah DeWitt wrote:
> I just installed SpamAssassin and got it working, but it just drops or marks spam
> after it has already accepted it. While this /dev/null type behavior is great, I
> would rather discourage spammers by refusing the connection peri
In most cases I can think of, spamc doesn't get the message until after
the connection is already finished. A milter is the only way I can
think of you can get a result from SA before Sendmail's finished
receiving the mail, and all the milters I'm aware of are capable of just
the sort of behav
I just installed SpamAssassin and got it working, but it just drops or marks spam
after it has already accepted it. While this /dev/null type behavior is great, I
would rather discourage spammers by refusing the connection period.
I was wondering if there is a way of using spamd/spamc to reject
