I am installing Mailman for the first time and running into a strange
problem. The system is running FreeBSD 6.2-STABLE and sendmail is
configured thus:

Version 8.14.1
Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7
NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING SASLv2
SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG


The system is using MailScanner to process mail and check for spam
(spamassassin) and viri (clamav).

When I tell mailman to send all the users their passwords, it starts firing
up a bunch of messages which are immediately rejected with:

ruleset=check_relay, arg1=localhost, arg2=127.0.0.1, relay=localhost
[127.0.0.1], reject=421 4.3.2 Connection rate limit exceeded.

But, I have turned off rate throttling for localhost in my access file:

# Throttling Defaults

# GreetPause: 2000 # Set in the .cf file
ClientRate: 10
ClientConn: 10


# Don't throttle 127.0.0.1 or LAN traffic

GreetPause:127.0.0.1 0 # Time to wait before 220 msg
ClientRate:127.0.0.1 0 # Connections/interval
ClientConn:127.0.0.1 0 # Concurrent connections

GreetPause:192.168.0 0 # Time to wait before 220 msg
ClientRate:192.168.0 0 # Connections/interval
ClientConn:192.168.0 0 # Concurrent connections


Ideas anyone?
------------------------------------------------------------ ----------------
Tim Daneliuk tundra [at] tundraware.com
PGP Key: http://www.tundraware.com/PGP/

Tim Daneliuk wrote:
> I am installing Mailman for the first time and running into a strange
> problem. The system is running FreeBSD 6.2-STABLE and sendmail is
> configured thus:
>
> Version 8.14.1
> Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7
> NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING
> SASLv2
> SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG
>
>
> The system is using MailScanner to process mail and check for spam
> (spamassassin) and viri (clamav).
>
> When I tell mailman to send all the users their passwords, it starts firing
> up a bunch of messages which are immediately rejected with:
>
> ruleset=check_relay, arg1=localhost, arg2=127.0.0.1, relay=localhost
> [127.0.0.1], reject=421 4.3.2 Connection rate limit exceeded.
>
> But, I have turned off rate throttling for localhost in my access file:
>
> # Throttling Defaults
>
> # GreetPause: 2000 # Set in the .cf file
> ClientRate: 10
> ClientConn: 10
>
>
> # Don't throttle 127.0.0.1 or LAN traffic
>
> GreetPause:127.0.0.1 0 # Time to wait before
> 220 msg
> ClientRate:127.0.0.1 0 # Connections/interval
> ClientConn:127.0.0.1 0 # Concurrent connections
>
> GreetPause:192.168.0 0 # Time to wait before
> 220 msg
> ClientRate:192.168.0 0 # Connections/interval
> ClientConn:192.168.0 0 # Concurrent connections
>
>
> Ideas anyone?
> ------------------------------------------------------------ ----------------
>
> Tim Daneliuk tundra [at] tundraware.com
> PGP Key: http://www.tundraware.com/PGP/

Oh - it also seems to do this intermittently when I post to a mailing list with
a sufficient number of users - presumably because the connection rate is again
being violated...


--
------------------------------------------------------------ ----------------
Tim Daneliuk tundra [at] tundraware.com
PGP Key: http://www.tundraware.com/PGP/

Tim Daneliuk wrote:
> Tim Daneliuk wrote:
>> I am installing Mailman for the first time and running into a strange
>> problem. The system is running FreeBSD 6.2-STABLE and sendmail is
>> configured thus:
>>
>> Version 8.14.1
>> Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7
>> NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS
>> PIPELINING SASLv2
>> SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG
>>
>>
>> The system is using MailScanner to process mail and check for spam
>> (spamassassin) and viri (clamav).
>>
>> When I tell mailman to send all the users their passwords, it starts
>> firing
>> up a bunch of messages which are immediately rejected with:
>>
>> ruleset=check_relay, arg1=localhost, arg2=127.0.0.1, relay=localhost
>> [127.0.0.1], reject=421 4.3.2 Connection rate limit exceeded.
>>
>> But, I have turned off rate throttling for localhost in my access file:
>>
>> # Throttling Defaults
>>
>> # GreetPause: 2000 # Set in the .cf file
>> ClientRate: 10
>> ClientConn: 10
>>
>>
>> # Don't throttle 127.0.0.1 or LAN traffic
>>
>> GreetPause:127.0.0.1 0 # Time to wait before
>> 220 msg
>> ClientRate:127.0.0.1 0 # Connections/interval
>> ClientConn:127.0.0.1 0 # Concurrent connections
>>
>> GreetPause:192.168.0 0 # Time to wait before
>> 220 msg
>> ClientRate:192.168.0 0 # Connections/interval
>> ClientConn:192.168.0 0 # Concurrent connections
>>
>>
>> Ideas anyone?
>> ------------------------------------------------------------ ----------------
>>
>> Tim Daneliuk tundra [at] tundraware.com
>> PGP Key: http://www.tundraware.com/PGP/
>
> Oh - it also seems to do this intermittently when I post to a mailing
> list with
> a sufficient number of users - presumably because the connection rate is
> again
> being violated...
>
>

Oh ... and one other interesting point. If I change the localhost settings to:

GreetPause:127.0.0.1 0 # Time to wait before 220 msg
ClientRate:127.0.0.1 1000 # Connections/interval
ClientConn:127.0.0.1 1000 # Concurrent connections

It works fine. It seems that the '0' argument is not being understood as
"unlimited" for some reason. Just for completeness sake, here is the relevant
portion of the .mc file:

FEATURE(`ratecontrol', ,`terminate')dnl
FEATURE(`conncontrol', ,`terminate')dnl
FEATURE(`greet_pause', `2000')dnl
define(`confBAD_RCPT_THROTTLE', `2')dnl


TIA for any insight you fine folk could offer on this ...
------------------------------------------------------------ ----------------
Tim Daneliuk tundra [at] tundraware.com
PGP Key: http://www.tundraware.com/PGP/