From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30586] New: More data about Mailman bounce-based unsubscriptions
Date: Mon, 26 Jun 2023 06:32:12 +0000 [thread overview]
Message-ID: <bug-30586-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30586
Bug ID: 30586
Summary: More data about Mailman bounce-based unsubscriptions
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: fweimer at redhat dot com
Target Milestone: ---
I regularly receive notices such as this one:
“
From: gcc-cvs-request@gcc.gnu.org
Subject: confirm 21b5183595835e57a9f69d008b4b03889d4d8b91
To: fweimer@redhat.com
Date: Fri, 23 Jun 2023 20:14:53 +0000 (2 days, 10 hours, 15 minutes ago)
Message-ID: <mailman.370.1687551293.1980521.gcc-cvs@gcc.gnu.org>
Your membership in the mailing list Gcc-cvs has been disabled due to
excessive bounces The last bounce received from you was dated
23-Jun-2023. You will not get any more messages from this list until
you re-enable your membership. You will receive 3 more reminders like
this before your membership in the list is deleted.
To re-enable your membership, you can simply respond to this message
(leaving the Subject: line intact), or visit the confirmation page at
[…]
”
Could you provide copies of some of the bounce messages, so that I have
something report to Red Hat's IT team? Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-06-26 6:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 6:32 fweimer at redhat dot com [this message]
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
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@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).