The problem: subscribers are all receiving duplicate copies of the original
post and any replies.
Are you saying that each list member receives 2 copies of an original post
addressed only to the list?
Each and every list member receives 2 copies of the post. It is addressed to
the list AND CCed to the poster's own email address.
EG. FROM: Me via listn...@listdomain.com
TO: listn...@listdomain.com
CC: m...@mydomain.com
**********
Ensure you don't have multiple runners processing the same slice of their
queues. See https://wiki.list.org/x/4030715 for the procedure to stop ALL
Mailman processes and then start it only once.
I stepped through this (results below). After a reboot, there is only one
runner.
/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
**********
Examine the Received: headers of both copies to determine the paths that the
message takes from poster to recipient.
I "diffed" the headers of both emails to check, and the message paths are the
same.
**********
After the reboot, I posted a test to the list(just the list address, no CC) and
now just the one copy of the message is delivered (although it wrote my address
into the CC field).
FROM: Me via listn...@listdomain.com
TO: listn...@listdomain.com
CC: m...@mydomain.com
So far so good. I'll keep an eye on the qrunner over the next few days. It came
good last time I restarted the qrunner, then went bad. But as you say, there
may well have been more than one runner doing their bit.
Here are the steps and results I went through.
# service mailman stop
# ps -fAww |grep python
root 432 1 0 Oct01 ? 00:48:57 /usr/bin/python3
/usr/bin/fail2ban-server -xf start
nobody 5659 5658 0 00:25 ? 00:00:00 /usr/bin/python
/usr/local/bin/mpanel-memory-graph
root 5687 5642 0 00:26 pts/0 00:00:00 grep python
////// I SHOULD HAVE CHECKED THAT BEFORE STOPPING MAILMAN
# service mailman start
/////// FAILED TO START
...
Oct 18 00:30:12 syd systemd[1]: Starting Mailman Master Queue Runner...
Oct 18 00:30:13 syd mailmanctl[5791]: Starting Mailman's master qrunner.
Oct 18 00:30:13 syd systemd[1]: mailman.service: Can't open PID file
/run/mailman/mailman.pid (yet?) after start: No such file or directory
/////// oh? MAYBE IT LIVES SOMEWHERE ELSE
# find / -type f -iname "mailman.pid"
/////// NO RESULT
///////// hmmm, AM I PANICKING YET?
#reboot
///////// phew..., MAILMAN RUNNING AFTER REBOOT.
# pstree
systemd─┬─agetty
├─cron
..
├─mailmanctl───python
├─master─┬─anvil
│ ├─2*[bounce]
...
# ps -fAww |grep python
////////// LOOKS LIKE ONLY 1 RUNNER. So far, so good.
root 432 1 0 00:36 ? 00:00:00 /usr/bin/python3
/usr/bin/fail2ban-server -xf start
list 745 1 0 00:38 ? 00:00:00 /usr/bin/python
/usr/lib/mailman/bin/mailmanctl -s start
list 751 745 2 00:38 ? 00:00:04 /usr/bin/python
/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
nobody 913 911 0 00:40 ? 00:00:00 /usr/bin/python
/usr/local/bin/mpanel-memory-graph
root 921 908 0 00:40 pts/0 00:00:00 grep python
/////// DID THAT PID FILE REAPPEAR?
# find / -type f -iname "mailman.pid"
/////// NO RESULT. ... shrug ...
All seems well, the list is delivering single copies of the message (for now).
Thank you Mark for that advice. Very much appreciated.
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
