All users getting disabled after upgrade of mailman3
Hello,
We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method).
Now everyone's having their addresses disabled due to "bounce" errors. This is odd, because I'm disabled, even though I received the 2 emails I sent to the list today (and that's the only list traffic today).
I used the mailman shell command from <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/XPIQI3O3NDLCLHJMSWYGHZAIXPUU3BTA/> to see who has been disabled. I had to make one fix to it, it should be m.list_name not mlist.list_name.
Confirmed that dozens of valid users have had their sub disabled.
In the logs I see:
Jan 18 19:25:17 2024 (952) Member quanah@fast-mail.org on list openldap-technical.openldap.org, bounce score = 1.
Jan 18 19:37:11 2024 (952) Member quanah@fast-mail.org on list openldap-technical.openldap.org, bounce score = 2. Jan 18 19:37:11 2024 (952) Disabling delivery for quanah@fast-mail.org on list openldap-technical.openldap.org by bounce Jan 18 19:37:11 2024 (952) Member quanah@fast-mail.org on list openldap-technical.openldap.org, bounce score 2 >= threshold 2, disabling delivery.
Jan 18 10:05:42 2024 (938) Peer: ('127.0.0.1', 36100) Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) handling connection Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'LHLO hypatia.openldap.org' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'MAIL FROM:<openldap-commit-bounces@openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) sender: openldap-commit-bounces@openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'RCPT TO:<openldap-commit-owner@openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) recip: openldap-commit-owner@openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'DATA' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'QUIT' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) connection lost Jan 18 10:05:42 2024 (938) Connection lost during _handle_client() Jan 18 10:05:45 2024 (940) <170557233590.937.7274928299237969540@hypatia.openldap.org> post to openldap-commit@openldap.org from openldap-commit-owner@openldap.org, 20265 bytes Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376@hypatia.openldap.org> low level smtp error: [Errno 111] Connection refused Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376@hypatia.openldap.org> delivery to quanah@openldap.org failed with code 444, [Errno 111] Connection refused
But... postfix is working fine, and I've had hundreds of emails generated *by* mailman about it disabling people due to bounces.
Thoughts on how to proceed appreciated.
Regards, Quanah
--On Thursday, January 18, 2024 3:08 PM -0800 Quanah Gibson-Mount <quanah@fast-mail.org> wrote:
Hello,
We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method).
sorry meant to put the version in here:
mailman3: 3.3.8-2~deb12u1
python3-django-mailman3: 1.3.9-1
python3-mailman-hyperkitty: 1.2.1-5
--Quanah
--On Thursday, January 18, 2024 3:11 PM -0800 Quanah Gibson-Mount <quanah@fast-mail.org> wrote:
--On Thursday, January 18, 2024 3:08 PM -0800 Quanah Gibson-Mount <quanah@fast-mail.org> wrote:
Hello,
We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method).
Additionally:
*) My personal email account has been disabled *again* despite there being NO list traffic since I sent out 2 list emails earlier today *) Neither of the emails I sent to the list show up in the list archives, even though I received copies of them from mailman before I got disabled
I don't get where the connection refused is coming from. mailman.cfg has:
smtp_host: localhost smtp_port: 25
lmtp_host: 127.0.0.1 lmtp_port: 8024
both of those are listening:
SMTP:
tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN tcp6 0 0 :::25 :::* LISTEN
LMTP:
tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN
--Quanah
On 1/18/24 15:08, Quanah Gibson-Mount wrote:
Hello,
We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method).
Now everyone's having their addresses disabled due to "bounce" errors. This is odd, because I'm disabled, even though I received the 2 emails I sent to the list today (and that's the only list traffic today).
Did you upgrade mailman core from a version older than 3.3.1?
If so, see this post <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/IC3LXQMANJGOVUOCVUBHIOGYZ4PA24F7/>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
--On Thursday, January 18, 2024 6:09 PM -0800 Mark Sapiro <mark@msapiro.net> wrote:
On 1/18/24 15:08, Quanah Gibson-Mount wrote:
Hello,
We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method).
Now everyone's having their addresses disabled due to "bounce" errors. This is odd, because I'm disabled, even though I received the 2 emails I sent to the list today (and that's the only list traffic today).
Did you upgrade mailman core from a version older than 3.3.1?
If so, see this post <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess age/IC3LXQMANJGOVUOCVUBHIOGYZ4PA24F7/>.
That's it! Thank you so much Mark! Excellent help as always.
Regards, Quanah
participants (2)
-
Mark Sapiro -
Quanah Gibson-Mount