From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: postmaster@kernel.org, clang-built-linux <llvm@lists.linux.dev>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [sysadmin] Fwd: Bouncing messages from llvm@lists.linux.dev
Date: Mon, 11 Jul 2022 14:19:33 -0400 [thread overview]
Message-ID: <20220711181933.rcukzsnabiiowy7p@meerkat.local> (raw)
In-Reply-To: <CAKwvOd=u=77MQwFeyaBbc2T0JXSESKRDNrFtiaTTuRcm6K1BPg@mail.gmail.com>
On Mon, Jul 11, 2022 at 10:54:34AM -0700, 'Nick Desaulniers' via Systems Administrators wrote:
> Hi Post Master,
> Any idea what's up with the below message?
>
> To Fangrui, it sounded like his patch wasn't delivered to our list but
> the message Fangrui sent was indeed posted.
> https://lore.kernel.org/llvm/20220710071117.446112-1-maskray@google.com/
>
> Can the error be reworded possibly to elucidate what's going on?
This happens in a rare case when we mistakenly allow a spam message through,
which is this one:
https://lore.kernel.org/llvm/0.0.3.735.1D894A7973BDB9A.0@absceraw.gazzettait.com/
when we tried to deliver this message to maskray@google.com, Google's spam
filters rejected it, so we got back a bounce. When this happens, mlmmj follows
up with a probe email to make sure the address is still valid, which is the
message you received.
This behaviour is indeed a bit confusing, but it's not about the mail you sent
out, just the spam your MX refused to receive.
HTH,
Konstantin
>
> ---------- Forwarded message ---------
> From: Fangrui Song <maskray@google.com>
> Date: Mon, Jul 11, 2022 at 10:36 AM
> Subject: Fwd: Bouncing messages from llvm@lists.linux.dev
> To: Nick Desaulniers <ndesaulniers@google.com>
>
>
> ---------- Forwarded message ---------
> From: <llvm+owner@lists.linux.dev>
> Date: Sun, Jul 10, 2022 at 3:30 PM
> Subject: Bouncing messages from llvm@lists.linux.dev
> To: <maskray@google.com>
>
>
> Greetings!
>
> This is the mlmmj program managing the <llvm@lists.linux.dev> mailing list.
>
> Some messages to you could not be delivered. If you're seeing this
> message it means things are back to normal, and it's merely for your
> information.
>
> Here is the list of the bounced messages:
> - 11406
>
>
>
>
> --
> 宋方睿
>
>
> --
> Thanks,
> ~Nick Desaulniers
next prev parent reply other threads:[~2022-07-11 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1657492202-18435-mlmmj-51d729a7@lists.linux.dev>
[not found] ` <CAFP8O3+Lw0wKfWY-VA+tuAnVcjyN17E=yk6-VU5WcWG1xdH+UA@mail.gmail.com>
2022-07-11 17:54 ` Fwd: Bouncing messages from llvm@lists.linux.dev Nick Desaulniers
2022-07-11 18:19 ` Konstantin Ryabitsev [this message]
2022-07-11 18:30 ` [sysadmin] " Nick Desaulniers
2022-07-11 18:34 ` Fangrui Song
2022-07-11 19:27 ` Konstantin Ryabitsev
2022-07-11 19:30 ` Nick Desaulniers
2022-07-11 19:31 ` Fangrui Song
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=20220711181933.rcukzsnabiiowy7p@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=postmaster@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.