"Post intent to blink-dev" button updated feature status but failed to send/post the email

[yoshisatoyanagisawa]

Thank you for letting us know that something needs to be fixed. This page is for recording bugs on Chrome Status (https://www.chromestatus.com). If you need to report a problem with Chrome or Chromium, please use crbug (http://crbug.com/new). Thank you.

Describe the bug
When using the "Post intent to blink-dev" feature from an "Intent to Extend Experiment" draft page, the feature status on chromestatus.com was successfully updated. However, the actual email was never sent to the blink-dev mailing list, nor does it appear in the Google Groups archives (https://groups.google.com/a/chromium.org/g/blink-dev).

To Reproduce
Steps to reproduce the behavior:

1. Fill in the required fields for the intent.
2. Go to a feature's "Intent to Extend Experiment" (or supposing any Intent) stage on chromestatus.com, and push "Draft Intent to Extend Experiment email" button.
3. Click the "Post intent to blink-dev" button in the opened page.
4. Observe that the feature status changes on the dashboard, but no email is received by the mailing list.

Expected behavior
Clicking "Post intent to blink-dev" should both update the feature status on the dashboard and successfully post the drafted message to the blink-dev@chromium.org mailing list.

Additional context

• I waited for over 24 hours to account for any potential delivery delays.
• I checked the official blink-dev Google Groups archives (https://groups.google.com/a/chromium.org/g/blink-dev), but the post is missing.
• This resulted in a discrepancy where the dashboard shows the intent has been "Trial Extension Pending" but the community has not been notified.
• https://chromestatus.com/feature/6265472244514816 is the feature I tried to extend experiment.

[jrobbins]

From the logs

POST /tasks/email-intent-to-blink-dev
INFO 2026-01-08T03:40:35.594103Z Submitting email task: To: blink-dev@chromium.org CC: ... Subject: Intent to Extend Experiment: SharedWorker on Android
INFO 2026-01-08T03:40:35.594617Z Processing 1 email tasks
INFO 2026-01-08T03:40:35.623455Z Skipping email task with no non-bounced To: addrs

The problem was the blink-dev was marked as a bouncing email address. We don't sent emails to addresses that bounced previously, but that rule is apparently too strict. I am tracking that general problem in #5853. But, I will keep this issue open until I specifically track down why (or at least when) blink-dev@chromium.org was marked as bouncing.

[jrobbins]

#5864 adds debugging so that we can track down the root cause. It will be a while before that is deployed to prod and then we wait for an example bounce to show up in the logs.