From: Benjamin LaHaise <ben@communityfibre.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Qian Cai <cai@redhat.com>, Michal Hocko <mhocko@suse.com>,
hannes@cmpxchg.org, riel@surriel.com,
Thanos Makatos <thanos.makatos@nutanix.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: can't register to linux-mm
Date: Tue, 15 Sep 2020 20:55:10 -0400 [thread overview]
Message-ID: <20200916005510.GU28450@kvack.org> (raw)
In-Reply-To: <20200915164228.c27bf7ed8355e2ccc882c380@linux-foundation.org>
On Tue, Sep 15, 2020 at 04:42:28PM -0700, Andrew Morton wrote:
> On Tue, 15 Sep 2020 15:51:17 -0400 Qian Cai <cai@redhat.com> wrote:
>
> > On Thu, 2019-05-30 at 14:21 +0000, Thanos Makatos wrote:
> > > I've been trying to register to linux-mm for the past few days and it's not
> > > working, I don't receive the confirmation email from majordomo. I also tried
> > > with different email addresses (e.g. gmail) and it's still not working. I'm
> > > simply sending a plain text email (subscribe linux-mm) to majordomo@kvack.org.
> > > Am I doing something wrong?
> > >
> >
> > Same issue here recently. It seems majordomo@kvack.org does not response to any
> > command at all. Does anybody know what's going on and who should be able to
> > resolve the issues there?
>
> Ben should be able to help?
>
Last email from thanos.makatos@nutanix.com I can see was in May 2019. I'm
guessing it gets spam filtered before it even hits majordomo. I'll need a
message id and logs from the mail server that was attempted to send the
request to track it down.
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2020-09-16 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 14:21 can't register to linux-mm Thanos Makatos
2020-09-15 19:51 ` Qian Cai
2020-09-15 23:42 ` Andrew Morton
2020-09-16 0:55 ` Benjamin LaHaise [this message]
2020-09-16 1:23 ` Qian Cai
2020-09-16 1:33 ` Benjamin LaHaise
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=20200916005510.GU28450@kvack.org \
--to=ben@communityfibre.ca \
--cc=akpm@linux-foundation.org \
--cc=cai@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=thanos.makatos@nutanix.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).