Next week I'll be going offline for 3 weeks (two of them being really off
the grid, I'm going to the European equivalent of the Burning Man
festival...), so I'd like to check with you what errors I've seen our
production Mailman3 instance do these last weeks.
I think that the main issue I haven't fixed yet is the fact that sometimes,
for an unknown reason (yet), the archiving process dies, and email isn't
archived anymore. The posts are still relayed to the subscribers, but the
email are not archived. This can be detected by two ways:
* there is no running process called "/usr/bin/python3.4
/usr/libexec/mailman3/runner --runner=archive:0:1 -C /etc/mailman.cfg" (see
the "runner" option on the command line)
* the "/var/spool/mailman3/archive/" directory starts filling up with
files. It's usually empty.
The best way to fix this is currently to restart the mailman process with
"systemctl restart mailman3". Then the unarchived emails in the backlog
will be processed, the speed is variable but it's around 1 or 2 per second.
The other problems that I've been pinged about recently are really
specific, it's either configuration problems or bugs that I've fixed now.
When it's about emails being rejected, it's usually a good idea to start
looking at the list's header filters (in Postorius).
If you have any questions, feel free to ask me. I'm leaving for the desert
on June 30th, I'll start being mildly reacheable on July 13th, and will be
back on Monday 18th.