From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30586] More data about Mailman bounce-based unsubscriptions
Date: Mon, 10 Jul 2023 07:24:26 +0000 [thread overview]
Message-ID: <bug-30586-14326-W3NYTbPNHD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30586-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30586
--- Comment #12 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Mark Wielaard from comment #11)
> It looks like no more "554 Email rejected due to security policies" bounces
> have been seen for more than 2 days now. Could you confirm emails seem to be
> flowing again to your address?
I just received:
“
Your membership in the mailing list Gcc-patches has been disabled due
to excessive bounces The last bounce received from you was dated
10-Jul-2023.
”
Any idea what bounces may have triggered this, and how far back they go?
Perhaps it's an actual spam rejection this time, which triggered Mailman into
action combined with the old bounces still stored in the system?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-07-10 7:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 6:32 [Bug Infrastructure/30586] New: " fweimer at redhat dot com
2023-06-26 8:59 ` [Bug Infrastructure/30586] " mark at klomp dot org
2023-06-26 9:19 ` fweimer at redhat dot com
2023-07-02 12:17 ` mark at klomp dot org
2023-07-02 12:49 ` mark at klomp dot org
2023-07-02 12:54 ` fweimer at redhat dot com
2023-07-02 18:22 ` mark at klomp dot org
2023-07-02 18:24 ` fche at redhat dot com
2023-07-03 10:00 ` fweimer at redhat dot com
2023-07-05 18:15 ` fweimer at redhat dot com
2023-07-05 20:07 ` mark at klomp dot org
2023-07-09 14:13 ` mark at klomp dot org
2023-07-10 7:24 ` fweimer at redhat dot com [this message]
2023-07-10 8:31 ` mark at klomp dot org
2023-07-14 11:34 ` mark at klomp dot org
2023-07-14 11:43 ` fweimer at redhat dot com
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=bug-30586-14326-W3NYTbPNHD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).