Hello All,

I've recently upgraded a Mailman 3 server from Debian 10.12 to Debian 11.4 [1].

In that process, I've also upgraded Mailman 3 from version 3.3.4 to version 3.3.5. I think the following guide was originally used when setting up Mailman 3 on the present server: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 .

After that upgrade process, I've noticed that at least one mailman process and one postgres process were at something like 40 %CPU or higher for extended periods of time (seen using top command). Upon further inspection, and through some research online, it seemed like the issue might have to do with bounces (maybe not processing or something) [2][3][4][5][6][7][8].

In my logcheck logs, I was seeing this message multiple times a second: Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>

I ended up trying to clear out the /opt/mailman/mm/var/queue/bounces and /opt/mailman/mm/var/locks directories to see if that would help.

There seemed to be some sort of positive change, because the log message "spamming" seemed to decrease. The high %CPU for the mailman and postgres processes in question also seemed to go down over time. But the related mailman process would still run at a high %CPU from time to time. I tried checking the mailman process using strace at some point, but I didn't see an easily evident cause for what was going on—from what I remember, there was something about a "POLLIN" or something that kept looping. When I go to check the same mailman process with strace today, I just see occasional messages like this: select(0, NULL, NULL, NULL, {tv_sec=45, tv_usec=43171}) = 0 (Timeout)

My Questions:

Is it normal to see large amounts of Running detector: <class 'flufl.bounce._detectors.dsn.DSN'> lines in logs?

Should there normally be other detectors listed in the logs beyond the DSN one?

If so, is there a setting I can change somewhere to make this happen?

For reference, I can only find one other logcheck log that shows a Running detector: <class 'flufl.bounce._detectors.dsn.DSN'> line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere):

Here is an example of previous log lines: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector: Running detector:

Thank you for your time, Andy

Web References:

[1] https://www.debian.org/News/2022/2022032602 [2] https://mail.python.org/archives/list/mailman-developers@python.org/thread/3... [3] https://phabricator.wikimedia.org/T282348 [4] https://mail.python.org/archives/list/mailman-users@python.org/thread/MISUMX... [5] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/M... [6] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... [7] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... [8] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/L...