Mailman receives, archives, acks message but does not send to list
The server was set up a year ago and has been functioning properly. But recently it no longer broadcasts to the list. The smtp log only shows the acknowledgement message, but no multi-recipient broadcasting message. Can anyone give a clue? Thanks in advance.
wqin
Wei Qin wrote:
The server was set up a year ago and has been functioning properly. But recently it no longer broadcasts to the list. The smtp log only shows the acknowledgement message, but no multi-recipient broadcasting message. Can anyone give a clue?
Search the Mailman FAQ Wiki for "troubleshooting".
-- Brad Knowles <brad@shub-internet.org> If you like Jazz/R&B guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at <http://tinyurl.com/y8kpxu> http://preview.tinyurl.com/bigsbytracks
Brad Knowles wrote:
Wei Qin wrote:
The server was set up a year ago and has been functioning properly. But recently it no longer broadcasts to the list. The smtp log only shows the acknowledgement message, but no multi-recipient broadcasting message. Can anyone give a clue?
Search the Mailman FAQ Wiki for "troubleshooting".
Thanks. I tried everything on the page http://wiki.list.org/display/DOC/4.78+Troubleshooting-+No+mail+going+out+to+...
but nothing helps. Permission is correct. The qrunners and the MTA are all up and running. Log shows that it is sending out acknowledgements, auto responses, and daily digests fine, but it somehow skips sending the message itself.
I tried to strace the outgoingrunner, it does the following when a message is posted.
- opens the message file in the out folder,
- opens config.pck,
- opens another message file in the out folder (seems user notification)
- opens config.pck again,
- establish socket connection and sends a message.
Apparently, it skips sending the original message file after reading config.pck. I went through the configuration options but couldn't see any option that could have turned off message delivery. What could have gone wrong?
Thanks,
wqin
Wei Qin wrote:
Thanks. I tried everything on the page http://wiki.list.org/display/DOC/4.78+Troubleshooting-+No+mail+going+out+to+...
but nothing helps. Permission is correct. The qrunners and the MTA are all up and running. Log shows that it is sending out acknowledgements, auto responses, and daily digests fine, but it somehow skips sending the message itself.
Does the list have any eligible recipients? I.e. is there at least one list member who is a regular, not a digest member, who has delivery enabled, who is not in a To: or Cc: of the message unless avoid dups is not set and who is not the poster if the poster is not set to receive own posts?
I tried to strace the outgoingrunner, it does the following when a message is posted.
- opens the message file in the out folder,
- opens config.pck,
- opens another message file in the out folder (seems user notification)
- opens config.pck again,
- establish socket connection and sends a message.
Apparently, it skips sending the original message file after reading config.pck. I went through the configuration options but couldn't see any option that could have turned off message delivery. What could have gone wrong?
Try stopping OutgoingRunner with a SIGTERM. Then send a post and look at the entries in the out queue with Mailman's bin/dumpdb. dumpdb will show two objects, the message and it's metadata. Is there an entry for the outgoing post? If so, is there anything in the 'recipients' list in the metadata. If so, the post should be sent to those addresses when OutgoingRunner is restarted. If not, either the CalcRecips handler didn't find any eligible recipients or AvoidDups removed them.
The cleanest way to restart after this is to stop and then start mailman with bin/mailmanctl.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you, Mark. The problem is resolved now. It was due to the selection of the "not metoo" option, and also the mysterious message loss related to gmail's inbox.
wqin
Mark Sapiro wrote:
Wei Qin wrote:
Thanks. I tried everything on the page http://wiki.list.org/display/DOC/4.78+Troubleshooting-+No+mail+going+out+to+...
but nothing helps. Permission is correct. The qrunners and the MTA are all up and running. Log shows that it is sending out acknowledgements, auto responses, and daily digests fine, but it somehow skips sending the message itself.
Does the list have any eligible recipients? I.e. is there at least one list member who is a regular, not a digest member, who has delivery enabled, who is not in a To: or Cc: of the message unless avoid dups is not set and who is not the poster if the poster is not set to receive own posts?
I tried to strace the outgoingrunner, it does the following when a message is posted.
- opens the message file in the out folder,
- opens config.pck,
- opens another message file in the out folder (seems user notification)
- opens config.pck again,
- establish socket connection and sends a message.
Apparently, it skips sending the original message file after reading config.pck. I went through the configuration options but couldn't see any option that could have turned off message delivery. What could have gone wrong?
Try stopping OutgoingRunner with a SIGTERM. Then send a post and look at the entries in the out queue with Mailman's bin/dumpdb. dumpdb will show two objects, the message and it's metadata. Is there an entry for the outgoing post? If so, is there anything in the 'recipients' list in the metadata. If so, the post should be sent to those addresses when OutgoingRunner is restarted. If not, either the CalcRecips handler didn't find any eligible recipients or AvoidDups removed them.
The cleanest way to restart after this is to stop and then start mailman with bin/mailmanctl.
-- Wei Qin
Assistant Professor ECE Department Boston University 8 St. Mary's Street Boston, MA 01760 (617)358-3641
participants (3)
-
Brad Knowles -
Mark Sapiro -
Wei Qin