On 1/7/22 6:07 PM, David Newman wrote:
On 1/7/22 4:32 PM, Mark Sapiro wrote:
I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/*
Bingo. This list had regular and digest footer templates with 0644 permissions owned by root:root, and there was an exception and traceback for the most recent message in shunt about the permissions issue.
That comes from running mailman import21 as root. Always run
mailman commands as the Mailman user.
I've changed ownership to mailman:mailman and restarted the mailman3 service.
As soon as I fixed this, my inbox filled with test messages...
Good!
Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log?
Yes, lots. This might or might not be a different issue.
It is exactly this issue which is now corrected.
As I mentioned earlier, the most recent message in shunt was from 0000 hours today. There are many "Cannot connect" messages since then, but none since fixing the issue above.
The Cannot connect messages are from the issue of ownership of the templates and Mailman's out runner continually retrying the send. This is separate from the shunted messages.
Seems OK now. The superuser sees all posts after the unshunt action.
So it appears that you ran mailman unshunt and the shunted messages
were successfully processed, so whatever caused them to be shunted in
the first place is fixed. Individual messages don't get shunted because
of this template ownership issue, but it may be that digests do get
shunted for this reason.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan