From: Mark Wielaard <mark@klomp.org>
To: Florian Weimer via Overseers <overseers@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: Bounces of gcc-patches email
Date: Thu, 07 Dec 2023 13:16:49 +0100 [thread overview]
Message-ID: <4683dfc0c6049772da6e80e77a1753c977b116c7.camel@klomp.org> (raw)
In-Reply-To: <87jzpqi7os.fsf@oldenburg.str.redhat.com>
Hi Florian,
On Thu, 2023-12-07 at 12:16 +0100, Florian Weimer via Overseers wrote:
> I just received one of those bounce notifications from Mailman for the
> gcc-patches list (“Your membership in the mailing list Gcc-patches has
> been disabled due to excessive bounces The last bounce received from you
> was dated 07-Dec-2023.”) Would it be possible to get additional details
> from those bounces, e.g. the SMTP rejection message from from the
> redhat.com MX, or whether it was a delayed bounce from further down the
> infrastructure? I wonder if it's related to a recent maintenance, or
> something else.
I am seeing two bounces to your address, one yesterday:
Dec 6 02:11:19 server2 postfix/smtpd[3679572]: 98FE23858423: client=localhost[::1]
Dec 6 02:11:19 server2 postfix/cleanup[3687370]: 98FE23858423: message-id=<oredg0rshb.fsf_-_@lxoliva.fsfla.org>
Dec 6 02:11:19 server2 opendkim[2238591]: 98FE23858423: no signing table match for 'oliva@adacore.com'
Dec 6 02:11:19 server2 postfix/qmgr[2245777]: 98FE23858423: from=<gcc-patches-bounces+fweimer=redhat.com@gcc.gnu.org>, size=69680, nrcpt=1 (queue active)
Dec 6 02:11:20 server2 postfix/smtp[3681116]: 98FE23858423: to=<fweimer@redhat.com>, relay=us-smtp-inbound-2.mimecast.com[207.211.30.242]:25, delay=1.1, delays=0.06/0/0.36/0.64, dsn=5.0.0, status=bounced (host us-smtp-inbound-2.mimecast.com[207.211.30.242] said: 554 Email rejected due to security policies - https://community.mimecast.com/docs/DOC-1369#554 [SBw5CqkjODKeyiHpAZWcjw.us91] (in reply to end of DATA command))
Dec 6 02:11:20 server2 postfix/bounce[3687396]: 98FE23858423: sender non-delivery notification: B110B385C6ED
Dec 6 02:11:20 server2 postfix/qmgr[2245777]: 98FE23858423: removed
And one today:
Dec 7 11:04:28 server2 postfix/smtpd[3270907]: BFD96385C6FC: client=localhost[::1]
Dec 7 11:04:28 server2 postfix/cleanup[3338005]: BFD96385C6FC: message-id=<075720231203030AEA6BEB19$D38F4CF043@wkints.com>
Dec 7 11:04:28 server2 opendkim[2238591]: BFD96385C6FC: no signing table match for 'reply@wkints.com'
Dec 7 11:04:28 server2 postfix/qmgr[2245777]: BFD96385C6FC: from=<gcc-patches-bounces+fweimer=redhat.com@gcc.gnu.org>, size=8950, nrcpt=1 (queue active)
Dec 7 11:04:29 server2 postfix/smtp[3333652]: BFD96385C6FC: to=<fweimer@redhat.com>, relay=us-smtp-inbound-2.mimecast.com[207.211.30.141]:25, delay=0.75, delays=0.04/0/0.2/0.5, dsn=5.0.0, status=bounced (host us-smtp-inbound-2.mimecast.com[207.211.30.141] said: 554 Email rejected due to security policies - https://community.mimecast.com/docs/DOC-1369#554 [pKd7O2DJPumk_edbXF7kRQ.us673] (in reply to end of DATA command))
Dec 7 11:04:29 server2 postfix/bounce[3338123]: BFD96385C6FC: sender non-delivery notification: 83A4E385B537
Dec 7 11:04:29 server2 postfix/qmgr[2245777]: BFD96385C6FC: removed
Hope that helps,
Mark
next prev parent reply other threads:[~2023-12-07 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 11:16 Florian Weimer
2023-12-07 12:16 ` Mark Wielaard [this message]
2023-12-07 12:29 ` Florian Weimer
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=4683dfc0c6049772da6e80e77a1753c977b116c7.camel@klomp.org \
--to=mark@klomp.org \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.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 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).