On 1/7/22 4:32 PM, Mark Sapiro wrote:
On 1/7/22 3:41 PM, David Newman wrote:
There are 24 messages in the shunt queue, the most recent of which is a digest from 0000 hours today. The test messages I sent later today are not there.
There are also 13 messages in the out queue. I can't read these as the filenames appear to change on every invocation of ls.
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.
I've changed ownership to mailman:mailman and restarted the mailman3 service.
As soon as I fixed this, my inbox filled with test messages...
Are there errors and tracebacks in var/logs/mailman.log?
Every message in the shunt queue should have an exception and traceback logged in mailman.log.
But the Postfix log doesn't show it being distributed to me or anyone else.
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.
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.
Oddly, neither of the two list owner emails (me and someone else) show this message in the archive via the admin panel. However if I log in as the list owner directly to the archives:
https://lists.domain.tld/archives/
I can see today's test posts if logged in as the list member, but do not see the posts if logged directly into the archive as the Django superuser.
That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can.
Seems OK now. The superuser sees all posts after the unshunt action.
Thanks very much for your help with this.
dn
The nondelivery of list mail is more serious than the archive problem, though.
Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why?
I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory.
I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with
mailman qfileand unshunt (reprocess) them withmailman unshunt.