From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31393] New: Subscription email for libc-alpha not arriving.
Date: Fri, 16 Feb 2024 17:58:14 +0000 [thread overview]
Message-ID: <bug-31393-14326@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2024-02-16 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 17:58 carlos at redhat dot com [this message]
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
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@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).