linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Slade Watkins <slade@sladewatkins.com>,
	Cong Wang <xiyou.wangcong@gmail.com>
Cc: Lijun Pan <lijunp213@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Networking <netdev@vger.kernel.org>
Subject: Re: Unsubscription Incident
Date: Wed, 27 Oct 2021 12:29:34 -0700	[thread overview]
Message-ID: <1d5ccba0-d607-aabc-6bd1-0e7c754c8379@infradead.org> (raw)
In-Reply-To: <CA+pv=HPK+7JVM2d=C2B6iBY+joW7T9RWrPGDd-VXm09yaWsQYg@mail.gmail.com>

On 10/26/21 5:02 PM, Slade Watkins wrote:
> Hi,
> On Mon, Oct 25, 2021 at 4:10 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>>
>> On Fri, Oct 22, 2021 at 10:53:28AM -0500, Lijun Pan wrote:
>>> Hi,
>>>
>>>  From Oct 11, I did not receive any emails from both linux-kernel and
>>> netdev mailing list. Did anyone encounter the same issue? I subscribed
>>> again and I can receive incoming emails now. However, I figured out
>>> that anyone can unsubscribe your email without authentication. Maybe
>>> it is just a one-time issue that someone accidentally unsubscribed my
>>> email. But I would recommend that our admin can add one more
>>> authentication step before unsubscription to make the process more
>>> secure.
>>>
>>
>> Same here.
>>
>> Fortunately I just switched to lei:
>> https://josefbacik.github.io/kernel/2021/10/18/lei-and-b4.html
>> so I can unsubscribe all kernel mailing lists now.
> 
> Not a bad workaround! I may consider trying this out. Thanks for
> sending this along.
> 
> I'd still love to figure out why the whole "randomly unsubscribing
> people who want to be subscribed" thing is happening in the first
> place, though.

Then you should try <postmaster@vger.kernel.org> for assistance.

-- 
~Randy

  reply	other threads:[~2021-10-27 19:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 15:53 Unsubscription Incident Lijun Pan
2021-10-22 15:54 ` Vladimir Oltean
2021-10-25  4:43   ` Benjamin Poirier
2021-10-25 17:04     ` Slade Watkins
2021-10-25 18:08       ` Metztli Information Technology
2021-10-25 19:47         ` Slade Watkins
2021-10-25 18:34       ` Shannon Nelson
2021-10-25 19:44         ` Slade Watkins
2022-02-20 23:54           ` Metztli Information Technology
2022-02-23  3:06             ` Slade Watkins
2021-10-27 19:34         ` Jakub Kicinski
2021-10-27 19:40           ` Shannon Nelson
2021-10-27 20:42           ` John 'Warthog9' Hawley
2021-10-28  0:27             ` Slade Watkins
2021-10-28  4:05               ` John 'Warthog9' Hawley
2021-10-25 19:32 ` Cong Wang
2021-10-27  0:02   ` Slade Watkins
2021-10-27 19:29     ` Randy Dunlap [this message]
2021-10-27 23:07       ` Richard Cochran

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=1d5ccba0-d607-aabc-6bd1-0e7c754c8379@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=lijunp213@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=slade@sladewatkins.com \
    --cc=xiyou.wangcong@gmail.com \
    /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 NNTP newsgroup(s).