From: Bruno Moreira-Guedes <codeagain@codeagain.dev>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: Testing Only - Ignore
Date: Sat, 02 Apr 2022 00:54:36 -0300 [thread overview]
Message-ID: <1c7a7e6e77cff87e6ae268318bc71306ac68091d.camel@codeagain.dev> (raw)
In-Reply-To: <20220401221251.GA1188492@alison-desk>
On Fri, 2022-04-01 at 15:12 -0700, Alison Schofield wrote:
> This mailing list is very small (since it's so new), and friendly,
> so I'm spamming it with my private email test.
>
> Not even sure this is a reasonable test.
>
> Mail in which I am in the To: is not coming through to my Intel
> email.
> For example, Bruno's last email I see when I browse w Lore, but I
> didn't get it in my @intel.com INBOX.
I think what you saw might be caused by issues on my side. The last
two days I kept trying to fix the problem, but my mail provider is
having serious delivery issues. They use a SMTP re-routing service for
cases where delivery fails, but I have to request them case-by-case
after it happens. To don't risk fragmenting my patch submissions I
found an alternative SMTP service, but I failed to add it also to my
mail client, and that's likely the reason you didn't receive it.
>
> It reminded me of something Stefano mentioned about mail getting
> de-dup'd and then you wind up with nothing.
If the e-mails get de-dup and my mail provider failed the delivery, my
best guess is that you won't receive it at all, since my post would be
the only one (my greatest fear in the last couple of days).
I hope it stops happening now!
next prev parent reply other threads:[~2022-04-02 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 22:12 Testing Only - Ignore Alison Schofield
2022-04-02 3:54 ` Bruno Moreira-Guedes [this message]
2022-04-04 5:47 ` Stefano Brivio
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=1c7a7e6e77cff87e6ae268318bc71306ac68091d.camel@codeagain.dev \
--to=codeagain@codeagain.dev \
--cc=alison.schofield@intel.com \
--cc=outreachy@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 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.