From: Jens Remus <jremus@linux.ibm.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: Fwd: Patches sent to Binutils list appear to be delayed and some missing
Date: Thu, 27 Jun 2024 10:52:56 +0200 [thread overview]
Message-ID: <84962a3f-750e-43e9-86a0-5e4f23dd890c@linux.ibm.com> (raw)
In-Reply-To: <Znx9NDIYDPYCvv9l@elastic.org>
Hello Frank!
Am 26.06.2024 um 22:42 schrieb Frank Ch. Eigler:
>> Jens Remus has been having some problems with emails sent to the binutils list:
>
>>> lately my patches sent to the GNU Binutils mailing list
>>> (binutils@sourceware.org) seem to take a long time to appear on the
>>> list. That is they show up the next day. For my latest patch series some
>>> patches even appear to be missing.
>>> [...]
>
> From the mailman logs, it appears that the messages are ARRIVING at
> sourceware hours apart. This part is from the mailman listmanager
> logs:
>
> post:Jun 24 15:54:56 2024 (3136) post to binutils from jremus@linux.ibm.com, size=15548, message-id=<20240624142334.3283823-5-jremus@linux.ibm.com>, success
> post:Jun 24 16:57:37 2024 (3135) post to binutils from jremus@linux.ibm.com, size=9009, message-id=<20240624142334.3283823-11-jremus@linux.ibm.com>, success
> post:Jun 24 17:56:26 2024 (3136) post to binutils from jremus@linux.ibm.com, size=9214, message-id=<20240624142334.3283823-14-jremus@linux.ibm.com>, success
> post:Jun 24 18:58:03 2024 (3138) post to binutils from jremus@linux.ibm.com, size=6928, message-id=<20240624142334.3283823-13-jremus@linux.ibm.com>, success
> post:Jun 24 19:01:36 2024 (3137) post to binutils from jremus@linux.ibm.com, size=8824, message-id=<20240624142334.3283823-8-jremus@linux.ibm.com>, success
> post:Jun 24 22:01:46 2024 (3135) post to binutils from jremus@linux.ibm.com, size=10444, message-id=<20240624142334.3283823-6-jremus@linux.ibm.com>, success
> post:Jun 24 22:02:31 2024 (3139) post to binutils from jremus@linux.ibm.com, size=12316, message-id=<20240624142334.3283823-3-jremus@linux.ibm.com>, success
> post:Jun 24 22:02:41 2024 (3138) post to binutils from jremus@linux.ibm.com, size=17897, message-id=<20240624142334.3283823-4-jremus@linux.ibm.com>, success
> post:Jun 24 22:05:51 2024 (3135) post to binutils from jremus@linux.ibm.com, size=11452, message-id=<20240624142334.3283823-1-jremus@linux.ibm.com>, success
> post:Jun 25 02:09:47 2024 (3137) post to binutils from jremus@linux.ibm.com, size=8589, message-id=<20240624142334.3283823-12-jremus@linux.ibm.com>, success
> post:Jun 25 03:10:28 2024 (3139) post to binutils from jremus@linux.ibm.com, size=8599, message-id=<20240624142334.3283823-9-jremus@linux.ibm.com>, success
> post:Jun 25 03:12:32 2024 (3136) post to binutils from jremus@linux.ibm.com, size=7517, message-id=<20240624142334.3283823-15-jremus@linux.ibm.com>, success
> post:Jun 25 05:16:01 2024 (3135) post to binutils from jremus@linux.ibm.com, size=7693, message-id=<20240624142334.3283823-16-jremus@linux.ibm.com>, success
> post:Jun 25 08:32:37 2024 (3135) post to binutils from jremus@linux.ibm.com, size=7091, message-id=<20240624142334.3283823-2-jremus@linux.ibm.com>, success
> post:Jun 25 10:10:32 2024 (3136) post to binutils from jremus@linux.ibm.com, size=17355, message-id=<20240624142334.3283823-10-jremus@linux.ibm.com>, success
> post:Jun 25 10:52:09 2024 (3138) post to binutils from jremus@linux.ibm.com, size=9716, message-id=<20240624142334.3283823-7-jremus@linux.ibm.com>, success
> post:Jun 26 15:22:08 2024 (3137) post to binutils from jremus@linux.ibm.com, size=11318, message-id=<20240626152033.2567309-3-jremus@linux.ibm.com>, success
> post:Jun 26 15:22:10 2024 (3138) post to binutils from jremus@linux.ibm.com, size=8977, message-id=<20240626152033.2567309-2-jremus@linux.ibm.com>, success
> post:Jun 26 15:22:13 2024 (3139) post to binutils from jremus@linux.ibm.com, size=7249, message-id=<20240626152033.2567309-1-jremus@linux.ibm.com>, success
>
> .... and similar time gaps show up in the spam filter.
Thank you very much for for the diagnosis! Looks like this was an issue
with IBM's e-mail infrastructure then. I will try to get this
investigated at our end. Above details should be very helpful!
One of the recipients on Cc of patch 1/15, which was initially missing
on the binutils mailing list, received it in-time, as he replied
promptly after I had sent it. Therefore I wrongly assumed the issue to
be within Sourceware's infrastructure.
>> [...]
>> Your message has been rejected, probably because you are not
>> subscribed to the mailing list and the list's policy is to prohibit
>> non-members from posting to it. If you think that your messages are
>> being rejected in error, contact the mailing list owner at
>> mailman-owner@server2.sourceware.org.
>> [...]
>
> This sounds like the primary thing to sort out first (or concurrently).
I am/was subscribed to the binutils list. This was for my attempt to
reach out to mailman@sourceware.org for assistance, which got rejected
with the message above.
I tried to reach out to mailman@sourceware.org because of the following
statement on https://sourceware.org/mailman/listinfo, which does not
indicate that one must first subscribe to a particular list (mailman is
actually not listed as a list either):
| If you are having trouble using the lists, please contact
mailman@sourceware.org.
Only later, after I had already asked Nick to assist, I found the
helpful contact information at:
https://sourceware.org/mission.html#organization
Maybe replace the suggestion to contact mailman@sourceware.org with a
link to above web page?
> But fwiw I see no sourceware infrastructure-caused abnormality in the
> logs at all.
Thanks again!
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303) and z/VSE Support
+49-7031-16-1128 Office
jremus@de.ibm.com
IBM
IBM Deutschland Research & Development GmbH; Vorsitzender des
Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der
Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/
next prev parent reply other threads:[~2024-06-27 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a5ca060e-4c0a-49ee-8fd4-745f5a859bf2@linux.ibm.com>
2024-06-25 10:55 ` Nick Clifton
2024-06-26 20:42 ` Frank Ch. Eigler
2024-06-27 8:52 ` Jens Remus [this message]
2024-06-27 14:10 ` Frank Ch. Eigler
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=84962a3f-750e-43e9-86a0-5e4f23dd890c@linux.ibm.com \
--to=jremus@linux.ibm.com \
--cc=fche@elastic.org \
--cc=nickc@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).