[Mailman-Users] mailman not sending post

Noah admin2 at enabled.com
Thu Dec 28 02:39:03 CET 2006

> Make sure to take a look in the FAQ wizard -- there's lots of good 
> troubleshooting tips in there. In fact, I recommend that you search on 
> the word "troubleshooting", among other things.

Thanks Brad for the recommendation. I am still running into trouble.

I host about 200 mail lists and one mail list in particular is no longer 
sending out posts. It is able to process subscribe and unsubscribe 
requests via email just fine.

The name of the list is ‘announce’ I have entries for the list in my 
virtusertable file and I have entries in the aliases.mailman file.

The list name ‘announce2’ with a fairly basic configuration works fine 
was also entered in the aliases.mailman and virtusertable. Posts to 
‘announce2’ are sent just fine.

I searched through the mailman FAQ and found “3.14. Troubleshooting: No 
mail going out to lists members” And below is the output and status from the

Mailman-2.1.9_1 from FreeBSD /usr/ports

The mailman FAQ troubleshooting steps were not helpful for providing 
clues and/or correcting my current problem. I am wondering if there are 
other recommendations that I should consider. Here is the relevant 
output and troubleshooting steps I have taken so far:

0) check perms

# ~mailman/bin/check_perms -f
No problems found

1) check if mailmanctl is running

# ps auxww| grep mailmanctl |grep -v grep
mailman 97350 0.0 0.3 7628 6272 ?? Is 1:03AM 0:00.03 
/usr/local/bin/python /usr/local/mailman/bin/mailmanctl -s -q start

2) check aliases and virtusertable for list entries

# !grep
grep announce aliases*
aliases.mailman:announce: "|/usr/local/mailman/mail/mailman post announce"
aliases.mailman:announce-admin: "|/usr/local/mailman/mail/mailman admin 
aliases.mailman:announce-bounces: "|/usr/local/mailman/mail/mailman 
bounces announce"
aliases.mailman:announce-confirm: "|/usr/local/mailman/mail/mailman 
confirm announce"
aliases.mailman:announce-join: "|/usr/local/mailman/mail/mailman join 
aliases.mailman:announce-leave: "|/usr/local/mailman/mail/mailman leave 
aliases.mailman:announce-owner: "|/usr/local/mailman/mail/mailman owner 
aliases.mailman:announce-request: "|/usr/local/mailman/mail/mailman 
request announce"
aliases.mailman:announce-subscribe: "|/usr/local/mailman/mail/mailman 
subscribe announce"
aliases.mailman:announce-unsubscribe: "|/usr/local/mailman/mail/mailman 
unsubscribe announce"
Binary file aliases.mailman.db matches
# newaliases
/etc/mail/aliases.mailman: 390 aliases, longest 69 bytes, 26928 bytes total
/etc/mail/aliases.hosting: 3 aliases, longest 47 bytes, 137 bytes total
/etc/mail/aliases: 914 aliases, longest 51 bytes, 13353 bytes total
/etc/mail/aliases.rt: 13 aliases, longest 110 bytes, 1450 bytes total

# grep announce virtusertable
announce at domainname.here announce
announce-admin at domainname.here announce-admin
announce-bounces at domainname.here announce-bounces
announce-confirm at domainname.here announce-confirm
announce-join at domainname.here announce-join
announce-leave at domainname.here announce-leave
announce-owner at domainname.here announce-owner
announce-request at domainname.here announce-request
announce-subscribe at domainname.here announce-subscribe
announce-unsubscribe at domainname.here announce-unsubscribe

# make
# make all
# make restart
/bin/kill -HUP `head -1 /var/run/sendmail.pid`

3) check Smrsh

not running smrsh

# pwd
# grep "smrsh" sendmail.cf

4) Interface

Added SMTPHOST = '<ip of my mailserver>' to ~mailman/Mailman/mm_cfg.py

Also from ~mailman/Mailman/mm_cfg.py

SENDMAIL_CMD = '/usr/sbin/sendmail'

5) check qrunner

they are running fine. All other lists are deliverying mail.

# ps -auxww | grep qrunner
mailman 45370 0.0 0.3 7584 6232 ?? I 9:57AM 0:00.25 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=RetryRunner:0:1 -s
mailman 45369 0.1 0.4 8724 7396 ?? S 9:57AM 0:00.43 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=VirginRunner:0:1 -s
mailman 45368 0.0 0.4 8712 7340 ?? S 9:57AM 0:00.50 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=OutgoingRunner:0:1 -s
mailman 45367 0.0 0.3 7600 6276 ?? S 9:57AM 0:00.32 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=NewsRunner:0:1 -s
mailman 45366 0.0 0.4 8716 7388 ?? S 9:57AM 0:00.47 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=IncomingRunner:0:1 -s
mailman 45365 0.0 0.3 7588 6236 ?? S 9:57AM 0:00.33 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=CommandRunner:0:1 -s
mailman 45364 0.0 0.3 8656 7220 ?? S 9:57AM 0:00.85 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=BounceRunner:0:1 -s
mailman 45363 0.0 0.3 7588 6236 ?? S 9:57AM 0:00.34 
/usr/local/bin/python /usr/local/mailman/bin/qrunner 
--runner=ArchRunner:0:1 -s
root 47159 0.0 0.0 308 168 p0 R+ 10:01AM 0:00.00 grep qrunner

6) locks.

# ls -l ~mailman/locks
total 4
-rw-rw-r-- 2 mailman mailman 65 Dec 28 15:57 master-qrunner
-rw-rw-r-- 2 mailman mailman 65 Dec 28 15:57 

# ps auxww | grep 45362 | grep -v grep
mailman 45362 0.0 0.3 7624 6288 ?? Is 9:57AM 0:00.02 
/usr/local/bin/python /usr/local/mailman/bin/mailmanctl -s -q start

7) Logs.

The incoming post email to announce arrives and sendmail dumps a line or 
two to /var/log/sendmail to acknowledge receipt of the email. There are 
no relevant entries showing up in:

there is no file called /usr/local/mailman/logs/config

8) Qfiles.

Not able to find any “clogged” messages in ~mailman/qfiles – will keep 
on checking.


Did this already added an SMTPHOST = '<ip of my mailserver>' line to the 
~mailman/Mailman/mm_cfg.py file

10) Sendmail + mm-handler

When testing sendmail manually from the shell on the local machine. I 
still see the relevant log lines from sendmail in /var/log/maillog 
showing the email was received and piped to mailman but nothing ends up 
in the mailman mail logs. I checked:


there is no file called /usr/local/mailman/logs/config

More information about the Mailman-Users mailing list