All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Fangrui Song <maskray@google.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
	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 12:31:59 -0700	[thread overview]
Message-ID: <CAFP8O3LTKizPJnGdtkTY8TQ+FjwCHd-b2oP8GDCEMKneRh83xA@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdkmy47RKjp8KeTN8L-y4jS-MtzyCCwoiBkAWHTDSixXXw@mail.gmail.com>

On Mon, Jul 11, 2022 at 12:30 PM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> On Mon, Jul 11, 2022 at 12:27 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> >
> > On Mon, Jul 11, 2022 at 11:30:31AM -0700, Nick Desaulniers wrote:
> > > Any chance the error message could say something like:
> > >
> > > The message at
> > > https://lore.kernel.org/llvm/0.0.3.735.1D894A7973BDB9A.0@absceraw.gazzettait.com/
> > > could not be delivered to you; it may be spam but you might want to verify.
> >
> > Unfortunately, mlmmj doesn't give me access to the message-id of the bouncing
> > message (see http://mlmmj.org/docs/readme-listtexts/).
> >
> > I will tweak the wording to offer a bit more explanation, though, something
> > like:
> >
> >     Some messages to you could not be delivered. This usually happens if we
> >     have accepted a spam message that is being rejected by your mail host when
> >     we try to deliver it, but may also be due to other reasons. Please review
> >     the public list archives to check if you are missing any legitimate mail.
> >
> >     If you're seeing this message it usually means that things are back to
> >     normal and no further action is required from you.
> >
> >     Here is the list of the bounced messages:
> >     - %bouncenumbers%
> >
> > -K
>
> LGTM; thanks Konstantin!
>
> --
> Thanks,
> ~Nick Desaulniers

LGTM. Thanks!

      reply	other threads:[~2022-07-11 19:32 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     ` [sysadmin] " Konstantin Ryabitsev
2022-07-11 18:30       ` 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 [this message]

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=CAFP8O3LTKizPJnGdtkTY8TQ+FjwCHd-b2oP8GDCEMKneRh83xA@mail.gmail.com \
    --to=maskray@google.com \
    --cc=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.