[qmailtoaster] Mailman gotcha with CHKUSER_RCPTLIMIT

2006-11-16 Thread Quinn Comendant
Surprise!

If you run mailman with the qmail toaster, chkuser will block mailman's sending 
of messages with the following error:

2006-11-16 15:12:54.424020500 CHKUSER rejected intrusion: from [EMAIL 
PROTECTED]:: remote two.strangecode.com:unknown:72.32.88.155 rcpt [EMAIL 
PROTECTED] : rcpt ignored, session over INTRUSION threshold

Mailman apparently does not send from 127.0.0.1 so I needed to add the 
following line to /etc/tcprules.d/tcp.smtp: 

72.32.88.155:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private

In other words, no CHKUSER_RCPTLIMIT is specified. 72.32.88.155 is the IP 
address that I route mail from (my primary server IP seemed to have trouble 
with blacklisting). Actually, maybe mailman normally *does* send messages from 
127.0.0.1 but my routing rules have changed this. Can anybody confirm this?

If mailman normally sends messages from an IP other than 127.0.0.1, should we 
include this exception in /etc/tcprules.d/tcp.smtp ?

Quinn


-
Strangecode :: Internet Consultancy
http://www.strangecode.com/
+1 530 624 4410

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[qmailtoaster] Mailman gotcha with CHKUSER_RCPTLIMIT

2006-11-16 Thread Quinn Comendant
Surprise!

If you run mailman with the qmail toaster, chkuser will block mailman's sending 
of messages with the following error:

2006-11-16 15:12:54.424020500 CHKUSER rejected intrusion: from [EMAIL 
PROTECTED]:: remote two.strangecode.com:unknown:72.32.88.155 rcpt [EMAIL 
PROTECTED] : rcpt ignored, session over INTRUSION threshold

Mailman apparently does not send from 127.0.0.1 so I needed to add the 
following line to /etc/tcprules.d/tcp.smtp: 

72.32.88.155:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private

In other words, no CHKUSER_RCPTLIMIT is specified. 72.32.88.155 is the IP 
address that I route mail from (my primary server IP seemed to have trouble 
with blacklisting). Actually, maybe mailman normally *does* send messages from 
127.0.0.1 but my routing rules have changed this. Can anybody confirm this?

If mailman normally sends messages from an IP other than 127.0.0.1, should we 
include this exception in /etc/tcprules.d/tcp.smtp ?

Quinn


-
Strangecode :: Internet Consultancy
http://www.strangecode.com/
+1 530 624 4410

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]