[Mailman-Users] Mail getting stuck in queue

[Stefan Förster]

Am 06.06.2008 um 23:46 schrieb Laura Conrad:
>
>    Mark> If your Python is at least 2.4.x, you can follow the  
> instructions for
>    Mark> modifying Mailman/Handlers/SMTPDirect.py to produce more  
> debugging
>    Mark> output in Mailman's error log which may help you find more.  
> Do not do
>    Mark> this with Python 2.3.x for the reason mentioned in the FAQ.
>
> OK.  It isn't completely stuck, but it's taking a lot longer to send
> out a few messages than I'd expect.  Right now, the last post in the
> post log was at 16:30, and at 17:39, "tail error" says:
>
> Jun 06 17:37:59 2008 qrunner(14342): send:   'rcpt TO:<redacted at yahoo.com 
> >\r\n'
> Jun 06 17:38:29 2008 qrunner(14342): reply:   '250 ok\r\n'
> Jun 06 17:38:29 2008 qrunner(14342): reply: retcode (250); Msg: ok
> Jun 06 17:38:29 2008 qrunner(14342): send:   'rcpt TO:<redacted at gmail.com 
> >\r\n'
> Jun 06 17:38:59 2008 qrunner(14342): reply:   '250 ok\r\n'
> Jun 06 17:38:59 2008 qrunner(14342): reply: retcode (250); Msg: ok
> Jun 06 17:38:59 2008 qrunner(14342): send:   'rcpt TO:<redacted at yahoo.com 
> >\r\n'
> Jun 06 17:39:29 2008 qrunner(14342): reply:   '250 ok\r\n'
> Jun 06 17:39:29 2008 qrunner(14342): reply: retcode (250); Msg: ok
> Jun 06 17:39:29 2008 qrunner(14342): send:   'rcpt TO:<redacted at hotmail.com 
> >\r\n'
>
> Does this tell you anything?


Basically either your Postfix needs from 17:38:29 to 17:38:59 to  
accept a single recipient or Mailman needs 30 seconds to read the  
response. It if is Postfix, you will either notice something in your  
maillog right away or at least you will be able to produce valuable  
debugging output running

postconf -e debug_peer_list=127.0.0.1 && postfix reload (replace  
127.0.0.1 with the IP of your Mailman server if they don't run on the  
same box)

Aside from misconfiguration or server load, one thing that immediately  
comes to my mind are excessive errors - after more than  
smtpd_soft_error_limit, this kind of slowdown is exactly what happens.


Cheers
Stefan
-- 
Stefan Förster     http://www.incertum.net/     Public Key: 0xBBE2A9E9
Mac OS X ate my ~/.signature.