[Mailman-Users] problem with mailman and qmail-ldap

[Mark Sapiro]

gabo wrote:
> Mark Sapiro wrote:
> 
>> gabo wrote:
>>  
>>
>>> I have run mailman with an qmail-ldap server.Once or twice per day, 
>>> mailman not delivery mail.
>>> The mails are received in qmail-ldap server and it calls  
>>> /var/lib/mailman/mail/mailman post listname.
>>> I checked it, qmail receive the mail, however the mailman not send. 
>>> Then i restart mailman and all mails received are sending.
>>>   
>>
>>
>> This seems to indicate that the mail reaches Mailman and is queued, but
>> there is some problem with one or more of the qrunners. Look at the
>> Mailman logs 'error' and 'qrunner' to see if qrunners are dying and
>> what might be causing it.
>>
>>  
>>
> nothing abount this in the error and qrunner log, only shuting and smtp 
> cannot connection, error messages.
<log messages snipped>

The next time this occurs, look in qfiles/* and see where the 
undelivered messages are. Don't worry about shunted messages in 
qfiles/shunt, or the archive/, bad/, bounces/, commands/, news/ or 
virgin/ queues either. Undelivered messages that will be delivered 
automatically following a mailmanctl restart will almost certainly be in 
one of in/, out/ or retry/.

Once you've located the messages, check the state of the corresponding 
runner. A command like

$ ps -fwu mailman

or whatever the equivalent is on your system normally gives something like:

UID        PID  PPID  C STIME TTY          TIME CMD
mailman   1564     1  0 Jul02 ?        00:00:00 /usr/bin/python 
/var/mailman/bin/mailmanctl -s -q start
mailman   1565  1564  0 Jul02 ?        00:33:00 /usr/bin/python 
/var/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman   1566  1564  0 Jul02 ?        00:00:53 /usr/bin/python 
/var/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
mailman   1567  1564  0 Jul02 ?        00:00:23 /usr/bin/python 
/var/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
mailman   1568  1564  0 Jul02 ?        00:03:31 /usr/bin/python 
/var/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
mailman   1569  1564  0 Jul02 ?        00:00:09 /usr/bin/python 
/var/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
mailman   1570  1564  0 Jul02 ?        00:08:01 /usr/bin/python 
/var/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
mailman   1571  1564  0 Jul02 ?        00:01:32 /usr/bin/python 
/var/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
mailman   1572  1564  0 Jul02 ?        00:00:00 /usr/bin/python 
/var/mailman/bin/qrunner --runner=RetryRunner:0:1 -s

If the specific qrunner isn't there, that's the problem. Maybe some 
system log can help determine why it died. If it is there, maybe you 
have tools to help figure why it isn't doing what it should be.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan