public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving.
@ 2024-02-16 17:58 carlos at redhat dot com
  2024-02-16 19:06 ` [Bug Infrastructure/31393] " mark at klomp dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: carlos at redhat dot com @ 2024-02-16 17:58 UTC (permalink / raw)
  To: overseers

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

            Bug ID: 31393
           Summary: Subscription email for libc-alpha not arriving.
           Product: sourceware
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Infrastructure
          Assignee: overseers at sourceware dot org
          Reporter: carlos at redhat dot com
  Target Milestone: ---

I have had a report to libc-alpha-owner of subscription confirmation emails not
arriving at the destination email.

I can confirm that when I use a person email I am also not seeing a
subscription confirmation email.

The person in question was a Google employee subscribing with a @google.com
email, and my own personal subscription was a test of an address that is backed
by Google Workspace.

I set severity to critical because this isn't something we're setup to self
serve and users might not understand what's wrong.

In this case I got the email directly via libc-alpha-owner.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
  2024-02-16 17:58 [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving carlos at redhat dot com
@ 2024-02-16 19:06 ` mark at klomp dot org
  2024-02-16 19:40 ` carlos at redhat dot com
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: mark at klomp dot org @ 2024-02-16 19:06 UTC (permalink / raw)
  To: overseers

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Could you provide a bit more details so that we can track what is happening?

What exactly was in the libc-alpha-owner email (any bounce or error message?)
Which address did you try to subscribe?
How did you try to subscribe this address (email or webform)?

As a workaround you can also subscribe people by hand at
https://sourceware.org/mailman/admin/libc-alpha/members/add

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
  2024-02-16 17:58 [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving 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
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: carlos at redhat dot com @ 2024-02-16 19:40 UTC (permalink / raw)
  To: overseers

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

--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Mark Wielaard from comment #1)
> Could you provide a bit more details so that we can track what is happening?
> 
> What exactly was in the libc-alpha-owner email (any bounce or error message?)
> Which address did you try to subscribe?

I subscribed to libc-alpha using the standard mailman web form here:
https://sourceware.org/mailman/listinfo/libc-alpha

> How did you try to subscribe this address (email or webform)?

Normal mailman 2.x webform from the listinfo.

> As a workaround you can also subscribe people by hand at
> https://sourceware.org/mailman/admin/libc-alpha/members/add

Correct, and since I'm the list owner I can help them subscribe, but I filed
this for the broader issue that the confirmation email hasn't arrived at my
address yet either.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
  2024-02-16 17:58 [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving 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
  2024-02-16 21:05 ` mark at klomp dot org
  4 siblings, 0 replies; 6+ messages in thread
From: mark at klomp dot org @ 2024-02-16 20:33 UTC (permalink / raw)
  To: overseers

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

--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
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.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
  2024-02-16 17:58 [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving carlos at redhat dot com
                   ` (2 preceding siblings ...)
  2024-02-16 20:33 ` mark at klomp dot org
@ 2024-02-16 20:46 ` carlos at redhat dot com
  2024-02-16 21:05 ` mark at klomp dot org
  4 siblings, 0 replies; 6+ messages in thread
From: carlos at redhat dot com @ 2024-02-16 20:46 UTC (permalink / raw)
  To: overseers

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
  2024-02-16 17:58 [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving carlos at redhat dot com
                   ` (3 preceding siblings ...)
  2024-02-16 20:46 ` carlos at redhat dot com
@ 2024-02-16 21:05 ` mark at klomp dot org
  4 siblings, 0 replies; 6+ messages in thread
From: mark at klomp dot org @ 2024-02-16 21:05 UTC (permalink / raw)
  To: overseers

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Carlos O'Donell from comment #4)
> (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).

Yes, that could very well be. In my own testing my list filtering did indeed
put the confirmation email into the libc-alpha list folder. The confirmation
email does have the List-Id: Libc-alpha mailing list
<libc-alpha.sourceware.org> header set.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2024-02-16 21:05 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-16 17:58 [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving 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
2024-02-16 21:05 ` mark at klomp dot org

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).