I received individual emails saying xxx unsubscribed.

One fellow figured it out and resubscribed.

It was just 100 unsubscribe emails, but that's a lot of work to add them back.

I only received two emails from people saying they didn't unsubscribe and wanted to know why they were unsubscribed. 

But it's still going to be a lot of work to add them all back. 

73

David

On Sun, Dec 22, 2024, 1:26 AM Scott Neader KA9FOX <ka9fox@qsl.net> wrote:
Hi David.  Are you saying you have received hundreds of emails from people, all saying they did not want to unsubscribe?  That would be contrary to what we believe to be true, so I'd like to get confirmation of this.

On another list I'm looking at, we sent test emails to a subset of those unsubscribed and, so far, 75% of those emails bounced back as undeliverable.  I suspect the others are still being retried (defunct servers,etc.). 

I believe the vast majority of those unsubscribed have bad email addresses and are rightly unsubscribed.  This is why I'd like to confirm that you've heard from hundreds of people, saying the opposite.  Please confirm.

- Scott KA9FOX

On Sat, Dec 21, 2024 at 10:34 PM D.J.J. Ring, Jr. <n1ea@arrl.net> wrote:
I have hundreds of unsubscriptions, they all say they never asked for unsubscribe. 

Isn't there a way to revert to what we had yesterday?

Best regards, 

David Ring N1EA 

On Sat, Dec 21, 2024, 10:30 PM Scott Neader KA9FOX <ka9fox@qsl.net> wrote:
Hi David.  Fortunately, there was no hacking involved!  But there was a Mailman problem that we recently fixed that was the cause of the barrage of unsubscriptions (for those with current or past email delivery issues). Let me explain:

We were recently notified that Mailman 'Digests' were not regularly being sent out to those that subscribe to them.  This led us to realize that, during a software update earlier this year, certain crons (automated routines) for the Mailman software were not firing on schedule.  George K5TR was able to fix the issue, however there was a large log jam of Mailman events that began to be processed, that had been queued up to run for some time.

I can only guess that Karl (the user below that was unsubscribed) had some type of temporary issue with his email, perhaps weeks or maybe months ago, so that Mailman was unable to deliver list mail to his address, for some period of time, and caused him to get an  unsubscription added to the queue.  Meanwhile, the issue with his email was probably resolved... but that unsubscription was already in the queue and was recently processed when the log jam was cleared.

I think the best plan is to either resubscribe those that you get notified about an unsubscription.... Or, better, would be to send them each an email and see if it bounces. If no bounce, it would be safe to resubscribe. If bouncing, then, of course, no need to resubscribe.

I'm sorry for the problem.

Scott KA9FOX 

On Sat, Dec 21, 2024 at 3:08 PM D.J.J. Ring, Jr. <n1ea@arrl.net> wrote:
A hacker got into qth.net and did a massive unsubscribe. 

I've notified Scott Neader, KA9FOX, owner of QSL/QTH net which hosts the email lists. 

Since it's happening to all lists, I'm hopeful Scott can roll things back to pre-hacker.

73

David N1EA 

On Sat, Dec 21, 2024, 11:34 AM <mailman-bounces@mailman.qth.net> wrote:
The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it.  This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).

For more information see:
http://mailman.qth.net/mailman/admin/cw/bounce




---------- Forwarded message ----------
From: Karl Zuk <karlzuk@hotmail.com>
To: "cw-bounces@mailman.qth.net" <cw-bounces@mailman.qth.net>
Cc: 
Bcc: 
Date: Sat, 21 Dec 2024 16:34:21 +0000
Subject: Re: You have been unsubscribed from the CW mailing list
I did not want to unsubscribe!  Karl Zuk  N2KZ

On Dec 21, 2024, at 10:11 AM, cw-bounces@mailman.qth.net wrote:

Thank you for belonging to the CW reflector, we wish you well and look
forward to the time when you return.

73

- Scott
__

Sent from my Samsung Galaxy S21. Please excuse brevity and typos.