• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

Issue Mailman doesn't send out email, after migrated from Plesk 12 to 17.8

flaxton

Basic Pleskian
I do see the test messages I sent to a list sitting in /var/spool/mailman/in

There are no pending requests according to Mailman.

I sent the test messages and monitored the maillog, but nothing was sent out to the list members.

For example, I see one message sent to the list in the maillog here:

Dec 30 12:01:23 cloud04 postfix/pipe[5099]: 462A5C9AF3E: to=<[email protected]>, relay=mailman, delay=0.31, delays=0.23/0.01/0/0.08, dsn=2.0.0, status=sent (delivered via mailman service)
Dec 30 12:01:23 cloud04 postfix/qmgr[16596]: 462A5C9AF3E: removed


so apparently the message went to Mailman, which seems to be confirmed that it is in the "in" folder I mentioned above. But it never gets sent to the list members.

Any ideas?

Thanks!

Fred
 
OK, well I know why it isn't working - mailman is not running!

ps auxwf | egrep -i mailman

returned no running jobs.

On my other servers, it returned something like:

mailman 1370 0.0 0.3 249348 10932 ? Ss Dec04 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s start
mailman 1373 0.0 0.3 249220 13416 ? S Dec04 2:56 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman 1374 0.0 0.3 249200 13440 ? S Dec04 3:04 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
mailman 1375 0.0 0.3 249228 13536 ? S Dec04 2:56 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
mailman 1376 0.0 0.3 249220 13404 ? S Dec04 2:55 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
mailman 1377 0.0 0.3 249232 13496 ? S Dec04 2:55 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
mailman 1378 0.0 0.3 249204 13548 ? S Dec04 3:00 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
mailman 1379 0.0 0.3 249224 13412 ? S Dec04 3:01 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
mailman 1380 0.0 0.3 249224 13552 ? S Dec04 0:00 \_ /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s

So I manually started it with:

/usr/bin/python /usr/lib/mailman/bin/mailmanctl -s start

and that worked. But something isn't set up properly to start it.

It's not in cron. The cron.d entry says it isn't started from /etc/init.d like most services.

Any ideas?

Thanks!

Fred
 
maybe you might check /var/log/mailman/error logfile for relevant entrys to nearow down the issue

ussually the comands should work
Mailman
To start the service through the command line:

/etc/init.d/mailman start
To stop the service through the command line:

/etc/init.d/mailman stop
To restart the service through the command line:

/etc/init.d/mailman restart
 
There is no "mailman" in /etc/init.d - that was the first place I looked. So something is supposed to start it, but I don't know what.

My other 2 servers, running Plesk Onyx and CentOS 7, also do not have /etc/init.d/mailman either...
 
Back
Top