[Mailman-Users] Mailman stopped delivering mail
msapiro at value.net
Tue Nov 22 20:07:57 CET 2005
Eric Evans wrote:
>>What if anything do you have in mm_cfg.py for SMTPHOST and SMTPPORT? If
>>nothing, Have you perhaps changed them in Defaults.py (Nothing in
>>Defaults.py should ever be changed)?
>The mm_cfg.py contains
>SMTPHOST = '<126.96.36.199>'
>which is the IP address of the server that is running Mailman.
>There is no SMTPPORT in the mm_cfg.py.
When you ran the test script and it delivered mail, did you specify
SMTPHOST = '<188.8.131.52>' in the test script, or did you leave it
as SMTPHOST = 'localhost'? If the latter, you could see if the test
script fails to deliver with SMTPHOST = '<184.108.40.206>', or you
could just remove SMTPHOST = '<220.127.116.11>' from mm_cfg.py and
let it default to 'localhost'.
>>3) you are not running the test script as the same user:group as
>How can I check to see what user & group the Outgoing Runner is running
>as? I don't know exactly what executable program that corresponds to.
A command like
ps -Awf | grep python
should show all the runners and their names and pids. It will also show
the command used to invoke bin/mailmanctl. If this command does not
contain the -u/--run-as-user option, then you can safely assume all
runners are running as the 'mailman' user and group which would be the
I suspect the problem isn't that though. I suspect the script will fail
if you tell it SMTPHOST = '<18.104.22.168>', and Mailman will work
if you remove SMTPHOST = '<22.214.171.124>' from mm_cfg.py.
>No, Mailman doesn't send anything at all. Interestingly I can email myself
>easily enough from this host using the mail command
Which is probably using sendmail and not trying to connect to an SMTP
server at <126.96.36.199> (which BTW is if anything, a name and not
an IP address).
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users