Sendmail before MailScanner

[S Mohan]

Use access. The order of the rules matter. Put the deny or reject from
IP before domain. I do not think combinations would work.

Mohan

-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
Behalf Of Raymond Dijkxhoorn
Sent: Thursday, March 06, 2003 2:29 AM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: Sendmail before MailScanner


Hi!

> Yet, this is my problem too. I wish MailScanner would be able to
> handle. Our gateway accepts daily thousands of messages, just to
> receive in turn a 550 user unknown from the internal mail hubs. This
> messages are generated in our case by SPAM, pretending to be generated

> by our university domain...
>
> The best would be to reject the message before enters the queue, but
> this is a Sendmail problem I can hardly handle (LDAP routing?).
> However, a rule something like this would help a lot: drop all
> messages containing in the body a line with
> "Received: from ...unitbv.ro" and not "(193.254.23"
> would stop the chain reaction for each of this messages (thousands of
> postmaster notify, returned message, etc. in the root mailbox). Can
> this be put in sendmail "acces" db? Or in  SpamAssassin's? Thank you,

If you like do do that, use ldap for example and let your relays be away
of the users that DO exsist. Its a mailer problem, and you can configure
that. Not mailscanner.

Bye,
Raymond.