That's what I did at first, but after that I sent 2 emails to openstack-discuss-owner@lists.openstack.org, at these times (Eastern): Jan 26 at 8:19 PM Fw: Your subscription for openstack-discuss mailing list has been disabled Jan 27 at 4:58 PM Re: Your subscription for openstack-discuss mailing list has been disabled On Tuesday, January 28, 2025 at 12:57:50 PM EST, Jeremy Stanley <fungi@yuggoth.org> wrote: On 2025-01-28 17:08:49 +0000 (+0000), Albert Braden wrote:
Is anyone manning the openstack-discuss-owner mailbox? I've been writing to that address about the recent glitch that deleted my list subscription and account (and according to the error message, hundreds of others), but I'm not getting a response.
I am, but it looks like you replied to a VERP bounce address for a probe instead, which merely caused Mailman to mark the message you were replying to as bounced back. This functionality is intended to catch subscriber addresses which have become defunct, and disable delivery for them. The earlier bounce which was quoted as an example in the probe was due to an unfortunate interaction with an MUA that sent a message with overly-long lines and the MTA on the list server rejecting Mailman's attempt to forward that message to other subscribers. I'm hoping we can get that underlying issue that caused the earlier bounces fixed shortly with https://review.opendev.org/940248 but still, subscriptions should only get disabled if a message is returned to the VERP address of a subsequent probe message (the ones that say "this is a probe...here's a copy of an earlier bounce which caused this probe to be sent to you"). Messages to the actual openstack-discuss-owner@lists.openstack.org address are delivered directly to the list administrators, and should not result in subscriptions getting their delivery disabled. -- Jeremy Stanley