public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
Date: Fri, 16 Feb 2024 20:46:53 +0000	[thread overview]
Message-ID: <bug-31393-14326-Y3hp7VnCEP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31393-14326@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31393

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Mark Wielaard from comment #3)
> Got an address to which the confirmation email didn't arrive. I looked it up
> in the postfix logs and it looks like it did actually arrive now (just now
> confirmed by the recipient) The Message-ID is
> mailman.0.1708112005.768143.libc-alpha@sourceware.org (postfix ID
> A07883857B86). This might have been a resent or forced subscription. But the
> user is now subscribed.

Thanks. Could just have been a transient issue.

For my own testing it seems like the confirmation email *did* arrive on time,
but interestingly the confirmation email is filtered by list
libc-alpha@sourceware.org ML filtering so I missed the confirmation!

The root cause here could be that if you setup ML filtering, then go to
subscribe to the list, you won't see the subscription request in your inbox,
but may instead have it land in the ML filtered folder (something I'd not
considered).

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2024-02-16 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 17:58 [Bug Infrastructure/31393] New: " carlos at redhat dot com
2024-02-16 19:06 ` [Bug Infrastructure/31393] " mark at klomp dot org
2024-02-16 19:40 ` carlos at redhat dot com
2024-02-16 20:33 ` mark at klomp dot org
2024-02-16 20:46 ` carlos at redhat dot com [this message]
2024-02-16 21:05 ` mark at klomp dot org

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-31393-14326-Y3hp7VnCEP@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).