public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* GCC email not getting through
@ 2023-06-05 14:33 Thomas Schwinge
  2023-06-05 14:36 ` Frank Ch. Eigler
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Schwinge @ 2023-06-05 14:33 UTC (permalink / raw)
  To: overseers; +Cc: thomas.schwinge

Hi!

I'm subscribed to a good number of GCC/Sourceware mailing lists via
<thomas@schwinge.name>.  As far as I can tell, I've had my last GCC email
delivered more than 10 hours ago: "Date: Sun, 04 Jun 2023 22:59:16 -0500"
(that is, 05:59 CEST).  That's... ;-) unusual.  In other words, I do see
emails on <https://inbox.sourceware.org/gcc/>,
<https://inbox.sourceware.org/gcc-patches/>, etc. that I do not have in
my mailbox.  A lot of other emails (from different sites) I've received
all day; so far found nothing missing but GCC mailing lists.

For example, per
<https://gcc.gnu.org/mailman/options/gcc/thomas%40schwinge.name>,
<https://gcc.gnu.org/mailman/options/gcc-patches/thomas%40schwinge.name>,
I'm subscribed and "Mail delivery": "Enabled".

Will you please check if there's anything wrong/queued/bounced/etc. for
<thomas@schwinge.name> on your side?


Grüße
 Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: GCC email not getting through
  2023-06-05 14:33 GCC email not getting through Thomas Schwinge
@ 2023-06-05 14:36 ` Frank Ch. Eigler
  2023-06-05 21:38   ` Resolved: " Mark Wielaard
  0 siblings, 1 reply; 4+ messages in thread
From: Frank Ch. Eigler @ 2023-06-05 14:36 UTC (permalink / raw)
  To: Overseers mailing list; +Cc: Thomas Schwinge, thomas.schwinge

Hi -

Thanks for the report.  It appears as though something broke our
reverse DNS, and other mailers consider this sus.  Investigating.

- FChE


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Resolved: GCC email not getting through
  2023-06-05 14:36 ` Frank Ch. Eigler
@ 2023-06-05 21:38   ` Mark Wielaard
  2023-06-14 21:52     ` Mark Wielaard
  0 siblings, 1 reply; 4+ messages in thread
From: Mark Wielaard @ 2023-06-05 21:38 UTC (permalink / raw)
  To: overseers

Hi,

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
https://fosstodon.org/@sourceware this was indeed a rDNS issue with
our network provider, now resolved. email flows again.

Cheers,

Mark

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Resolved: GCC email not getting through
  2023-06-05 21:38   ` Resolved: " Mark Wielaard
@ 2023-06-14 21:52     ` Mark Wielaard
  0 siblings, 0 replies; 4+ messages in thread
From: Mark Wielaard @ 2023-06-14 21:52 UTC (permalink / raw)
  To: Mark Wielaard via Overseers

Hi,

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
> https://fosstodon.org/@sourceware 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.

Cheers,

Mark

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-06-14 21:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-05 14:33 GCC email not getting through 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 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).