From: Mike Snitzer <snitzer@redhat.com>
To: linux-lvm@lists.linux.dev
Subject: list unsubscribe confusion [was: You have been unsubscribed from the linux-lvm mailing list]
Date: Sat, 21 Oct 2023 12:32:28 -0400 [thread overview]
Message-ID: <ZTP9HNezNcl0IhSx@redhat.com> (raw)
In-Reply-To: <mailman.0.1697887231.3730022.linux-lvm@redhat.com>
You haven't been unsubscribed.
The list is now managed by lists.linux.dev
I think someone saw the auto-mail when i subscribed the new list
(linux-lvm@lists.linux.dev) to the old list (linux-lvm@redhat.com),
they were bad actors and decided to spoof the new list and unsubscribe
it from the old list (because confirmation was sent to the new list
they were able to successfully unsubscribe the new list from the old
mailman list).
I've since locked down unsubscribe requests from the old list. But
you should only receive mail from this list in terms of
lists.linux.dev moving forward.
The temporary forward from the old list to the new is just a stop-gap
tp catch people who still send to the old list. It will be
discontinued in ~2 weeks.
If you'd like to be extra sure you're still subscribed (to the new
list) please send mail to: linux-lvm+subscribe@lists.linux.dev
Sorry for any confusion.
Thanks,
Mike
parent reply other threads:[~2023-10-21 16:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.0.1697887231.3730022.linux-lvm@redhat.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTP9HNezNcl0IhSx@redhat.com \
--to=snitzer@redhat.com \
--cc=linux-lvm@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).