public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Mark Wielaard via Overseers <>
Subject: Re: Resolved: GCC email not getting through
Date: Wed, 14 Jun 2023 23:52:05 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


On Mon, Jun 05, 2023 at 11:38:08PM +0200, Mark Wielaard via Overseers wrote:
> On Mon, Jun 05, 2023 at 10:36:51AM -0400, Frank Ch. Eigler via Overseers wrote:
> > Thanks for the report.  It appears as though something broke our
> > reverse DNS, and other mailers consider this sus.  Investigating.
> For those on the list who haven't followed irc or
> this was indeed a rDNS issue with
> our network provider, now resolved. email flows again.

Note that tomorrow there will be another rDNS update for our
zone. Everybody is aware the previous update caused some issues and
the cause is known, so I don't expect any issues this time. But in
case you do notice something please let us know.



      reply	other threads:[~2023-06-14 21:52 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
2023-06-05 21:38   ` Resolved: " Mark Wielaard
2023-06-14 21:52     ` Mark Wielaard [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).