[Mimedefang] MaxRecipientsPerMessage

WBrown at e1b.org WBrown at e1b.org
Wed Apr 14 07:28:47 EDT 2004


mimedefang-bounces at lists.roaringpenguin.com wrote on 04/13/2004 03:47:36 
PM:

> The problem with this option is that if you are using a single host 
> or configuration for both inbound and outbound mail, then the limit 
> will also apply to your users. If you use it, 5 is probably as good 
> of value as any under these circumstances.

The system is an inbound relay only, so it is not going to affect internal 
users sending mail out.

> There are probably better solutions to this problem than using 
> MaxRecipientsPerMessage. A couple of alternative strategies we have 
> found more effective are:
>    Bouncing any email that has even a single invalid recipient name 
> (this is trivial to do in sendmail rules -- and fast too!)
>    Using BAD_RCPT_THROTTLE to slow down connections that send to 
> bogus users (set to 1).

The problem is that the system filters for 20+ destination mail servers, 
with no common directory.  I may try to implement LDAP lookups in sendmail 
in the future, but that will be complicated by tryinig to figure out how 
to query the right server depending on the destination domain.
 
> If you have separate inbound and outbound MTAs, then you can set 
> MaxRecipientsPerMessage to the lowest possible number that will not 
> cause your average non-spam to fail -- something like 2 or 3.

yesterday, I set it to 25, without seeing any immediate problems.  Not 
sure it it's helping any though.



More information about the MIMEDefang mailing list