[Mailman-Users] Mailman receives, archives, acks message but does not send to list
mark at msapiro.net
Fri Jan 16 17:10:12 CET 2009
Wei Qin wrote:
>Thanks. I tried everything on the page
>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
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.
>1. opens the message file in the out folder,
>2. opens config.pck,
>3. opens another message file in the out folder (seems user notification)
>4. opens config.pck again,
>5. 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
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 at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users