Email notification from forum says I can reply to email, but it doesn't work

At the bottom of an email notofication from this forum it is said I can either visit the site, or reply to the email. See here.

On Wed, 7 Jan 2026 at 03:30, nima_asgari via Google Developer forums no-reply@discuss.google.dev wrote:

| | nima_asgari
January 7 |
|----|----|

Looking at the support document though, it seems like this isn’t just a new UX for email delegation.

  • The support document notes that the creation flow for shared inboxes is separate from the standard user creation flow, which is what is used for email delegation today.

  • The support document notes that “You can convert an any existing email account (including delegated accounts) [emphasis mine] in your organization to a shared inbox and assign delegates.” This makes it sound like these shared inboxes will be a new primitive separate from the user account type (used for delegated accounts today) and the google group type, one that I hope doesn’t consume any workspace licenses and doesn’t allow direct authentication.

I know that I’m reading deep between lines here, but I’m hopeful.


Visit Topic or reply to this email to respond.

But when replying, I get this error message.

On Wed, 7 Jan 2026 at 08:50, Google Developer forums no-reply@discuss.google.dev wrote:

We’re sorry, but your email message to [“no-reply@discuss.google.dev”] (titled Re: [Google Developer forums] [Review upcoming launches (Roadmap & Release Radar)/Questions & Discussion] Shared Inbox Rollout Date) didn’t work.

Here are some things to check:

  • Do you use more than one email address? Did you reply from a different email address than the one you originally used? Email replies require that you use the same email address when replying.

  • Did your email software properly use the Reply-To: email address when replying? Unfortunately, some email software incorrectly sends replies to the From: address, which won’t work.

  • Was the Message-ID header in the email modified? The Message-ID must be consistent and unchanged.

Need more help? Reach out to us via the Contact Us details at https://discuss.google.dev/about

I’d recommend removing that “reply to the email” reference in those notification emails.

2 Likes

@kim_nilsson - thank you for bringing this to our attention, we will look into it.

3 Likes

@kim_nilsson - I just PM’d you with some additional information. Please let me know if that resolves the issue.

1 Like

I can now see that the reply-to address is different from when I posted this problem.
I think this post will succeed.

2 Likes

I’m going to keep an eye out, but I see when I today click Reply to notifications after 7 Jan that they show the correct incoming… address, and not the “broken” no-reply-address.

So I changed nothing on my end. It just works now for new notifications.

2 Likes