Bug 31393 - Subscription email for libc-alpha not arriving.
Summary: Subscription email for libc-alpha not arriving.
Status: RESOLVED FIXED
Alias: None
Product: sourceware
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: unspecified
: P2 critical
Target Milestone: ---
Assignee: overseers mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-16 17:58 UTC by Carlos O'Donell
Modified: 2024-02-16 21:05 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos O'Donell 2024-02-16 17:58:14 UTC
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.
Comment 1 Mark Wielaard 2024-02-16 19:06:35 UTC
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
Comment 2 Carlos O'Donell 2024-02-16 19:40:02 UTC
(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.
Comment 3 Mark Wielaard 2024-02-16 20:33:30 UTC
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.
Comment 4 Carlos O'Donell 2024-02-16 20:46:53 UTC
(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).
Comment 5 Mark Wielaard 2024-02-16 21:05:50 UTC
(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.