From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Thomas Schwinge <thomas@schwinge.name>, thomas.schwinge@siemens.com
Subject: Re: GCC email not getting through
Date: Mon, 5 Jun 2023 10:36:51 -0400 [thread overview]
Message-ID: <20230605143651.GD3687@redhat.com> (raw)
In-Reply-To: <87r0qqx9lb.fsf@euler.schwinge.homeip.net>
Hi -
Thanks for the report. It appears as though something broke our
reverse DNS, and other mailers consider this sus. Investigating.
- FChE
next prev parent reply other threads:[~2023-06-05 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 14:33 Thomas Schwinge
2023-06-05 14:36 ` Frank Ch. Eigler [this message]
2023-06-05 21:38 ` Resolved: " Mark Wielaard
2023-06-14 21:52 ` Mark Wielaard
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=20230605143651.GD3687@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=thomas.schwinge@siemens.com \
--cc=thomas@schwinge.name \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).