I'm changing the Chatter sender address in Setup > Chatter > Email Settings to a shared mailbox that I don't personally receive mail at. A client monitors the mailbox.
Saving the field sends a verification email to the new address. My client clicked the link and saw a confirmation that verification succeeded. She was then redirected to a Salesforce login screen, prepopulated with my username. She tried to login using her own credentials and was rejected. Her failed attempts don't appear in her Login History at all.
Setup continued to show "Requested new email address isn't valid until verified."
Here's what I have tried and ruled out so far:
- User error: I repeated this three times, including watching her click the link on a screen share
- The address is already a verified Organization-Wide Email Address, Purpose set to User Selection and Default No-Reply Address for all profiles.
- The sending domain is verified via a DKIM key.
- The address doesn't belong to a Salesforce User. However as far as I can tell the Chatter sender field doesn't require one.
- Org-level Allow Emails is enabled, and other Chatter notifications are sending normally from the current address.
What's blocking the verification?
#Chatter #Verification Email #Email Deliverbility
A Salesforce Case directed me to the solution:
Since Summer '26, these verification links are session-bound to the admin who initiated the change.
The EmailChangeVerification service requires the same logged-in session for sending the verification AND clicking the verification link in the resulting email. When a different user clicks the link, the token mismatch triggers Device Activation, which blocks the verification from completing. That also explains the missing Login History entries: Device Activation intercepts before the login is processed.
I sent a new verification email and asked the mailbox owner to forward the verification email back to me. I then logged in and clicked the link.
Salesforce confirmed this is Working As Designed, and no fix is planned.
This is documented in a KA (https://help.salesforce.com/s/articleView?id=005388172&type=1), but it's hard to find if you are working on Chatter verification, and it didn't come up in my AI-driven web searches.
The article is titled for Email-to-Case routing addresses and Organization-Wide Email Addresses, never mentions Chatter, and closes with "This behaviour is specific to routing address verification." Searching on the Chatter symptom won't surface it, and skimming it suggests Chatter isn't affected.
I'm cross-posting this in Salesforce Stack Exchange for visibility (and in the hopes that it will be more likely that future AI-driven troubleshooting sessions find this content):
https://salesforce.stackexchange.com/questions/439845/why-does-the-chatter-sender-address-stay-unverified-after-the-mailbox-owner-clic/439846#439846
