Mailman not delivering to members

[santrix]

When mailman sends out messages to list members, do these messages pass through exim (and therefor would appear in the exim_mainlog ?)

I am trying to trace a problem for a customer, and can't find any trace of the messages in the exim_mainlog. I see no bounce entried in the bounce log for mailman, and no obvious entries in the other mailman logs.

Cheers for any info

 

[JaredR.]

Messages sent to mailing lists are processed by Exim. There are transports defined in /etc/exim.conf for handling messages that are sent to Mailman lists.

Try this:

# exim -d -v destination_address@destination_domain.tld

This will simulate sending a message to the destination address, for example the mailing list address, and let you see how the Exim filters handle it.

You have probably checked it already, but since you mention seeing nothing in the logs, have you checked to make sure the domain's MX record(s) point to an A record that resolves to your server?

 

[santrix]

That's a handy tip... thanks... All check out fine domain/mx wise. I ended up running scripts/fixmailman, and the customer said that all of his customers who were on his mailing list suddenly got all of their messages... odd...

If it happens again, let me know what I should capture for analysis

 

[JaredR.]

Besides checking the Exim logs (especially /var/log/exim_mainlog, but don't forget /var/log/exim_paniclog and /var/log/exim_rejectlog), also check to make sure that the Mailman service is actually running. Use the ps command, and you should see something like this:

# ps aux|grep -i mailman
mailman   3044  0.0  0.4  10648  4340 ?        Ss   Sep22   0:00 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl -s start
mailman   3046  0.0  0.5  10356  6044 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman   3047  0.0  0.5  10364  6044 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
mailman   3048  0.0  0.5  10364  6048 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
mailman   3049  0.0  0.5  10424  6048 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
mailman   3050  0.0  0.5  10364  6080 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
mailman   3051  0.0  0.5  10384  6104 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
mailman   3063  0.0  0.5  10384  6048 ?        S    Sep22   0:01 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
mailman   3064  0.0  0.5  10384  6032 ?        S    Sep22   0:00 /usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
root     26584  0.0  0.0   4004   680 pts/0    R+   12:40   0:00 grep -i mailman

The exact number of processes may vary, but the output should be similar. If it is not running, you can try to start it using the following command:

# /usr/local/cpanel/etc/init/startmailman

This may give you meaningful errors that you might not see if you simply reinstall Mailman.

You can also stop mailman using:

# /usr/local/cpanel/etc/init/stopmailman