Obviously I’m testing with several accounts I created just for this purpose (using virtual machines and other browsers and too much time testing 
).
I think I resolved the issue on my end. It had nothing to do with Discourse.
There’s a bit of code in my site’s footer that checks – for users whose email has been verified – if they are logged in to Discourse already and, if they aren’t, logs them in. This informs Discourse of users’ info, even if they don’t visit the forum itself.
Alas, this chunk was being accidentally cached so, of course, it wasn’t firing because it had been cached when no user had logged in. My bad! 
「いいね！」 3
This is probably the best place still to mention that there are cases when Discourse drives me absolutely nuts.
I happen to have several “users” that are not real. Whether they are read-only accounts for a specific hidden category, anonymous beyond the capabilities of Discourse or whatever should not matter. Some of these are automatic and created on the fly as needed (and reused in a queue).
Problem is, they have been added using a “noreply” email. That email does not exist anymore so Discourse is spamming out admin mails saying this email bounced, all the time, for each of these users and the moderators are now starting to go nuts.
Now, if I go in and change that email to an existing no-forward, no-store email, Discourse refuses to do it without sending a mail to said email asking for confirmation… so no changes are made. Anyone see the problem here? 
So I have two options I can think of:
Log in as each user using SSO to force an email change (which hopefully does not require confirmation, haven’t actually tried, would be too tedious).
Go to the preferences of each such user and change email notifications and summary digests to never, ever. And every time a new temporary user gets created, I need to remember to do the same.
Maaaaan. If I as an admin change an email for a user, there is no need to ask the user to confirm the email. Any user will hopefully contact me if I actually messed up which is very unlikely. Besides, these days I just let the users change their emails at will, less trouble for a poor admin. And I understand there is a risk that the user will never be able to login or notify anyone again but obviously they can mail the site help as such.
「いいね！」 1
Why not use the sync_sso endpoint to fix all the emails via api?
「いいね！」 2
Not sure what you mean by this. Are you talking about the setting “sso overrides email”?
That would only take effect when/if the user actually logs in. So emails would still bounce while the email is wrong.
If you are possibly talking about “POST admin endpoint /admin/users/sync_sso to synchronize an SSO record” that would mean I would have to force one or all users from the SSO software I guess. Given the problems with SSO emails syncing it’s not the first option I would try.
Anyway, because of the problem described earlier in this topic I now have “sso overrides email” off and let users change their emails themselves. So I don’t want to override from SSO anymore.
But all this is missing the point, that the users bouncing mails are generated on the fly, as needed. The easiest way would be to allow a change to the email without authentication (at least for admins - or admins would have a choice).
Side note: I have tried giving an empty email address but the system does not allow for that. I understand the email address is so critical is should not be empty. BUT, if you really give an empty email (at least as an admin), one could assume you know what you are doing.
Just to confuse things more, I actually have users that do not have an email account, only access to a browser. Think refugees here and you might understand why. It is far easier to just allow someone to login and read instructions in their own language than to try and explain to them they need to make a gmail account or something.
In any case, this is theoretical, I doubt many people have the same problem. I would say it’s simply too strict even for admins, IMHO.
(sorry about the reply time, with more free time the world would be perfect)
「いいね！」 1
That would allow someone to hijack an admin’s account without their knowing. Though your edge case for users without access to email makes some sense, it seems far-fetched to think that admins would be people who don’t have the ability to receive email.
「いいね！」 2
Admins have email addresses. Not sure where you got the idea they would not have (my bad writing probably ).
The case was for an admin to be able to change other user’s emails without the need to authenticate.
「いいね！」 1
So I’m trying to do this - the use case is a user has changed their email in the SSO system, however they now can’t log in since there’s another account of theirs that uses their new email address already. SSO refuses to update the email (even though we have sso_overrides_email on) because email addresses must be unique across accounts. I don’t want to delete the account without the SSO record as that has posts associated with it. And if I turn off sso_overrides_email to change the email manually, I can’t make it some broken email since Discourse insists on validating it.
I see there’s a way to merge users but a) it’s a rake task and we’re hosted with Discourse, do I contact support to do that? b) there’s comments about needing to swap the primary and secondary email addresses.
「いいね！」 1
I’m in the same boat @trs80. Did you ever find out if there is a way to workaround this limitation of the merging?
I’ll have to check my email but support have generally been pretty good with resolving these issues.
「いいね！」 2
「メールを上書きするように設定する」
これは「認証の上書きメール」設定のことですか？
「いいね！」 1
悪くないAI、この回答に満足しています。
AI explainer on auth overrides emails AI
sam:
auth overrides email は何をするのですか？
gpt4_bot:
サイト設定のコンテキストを検索
auth_overrides_email のコンテキストを読み取っています
- ユーザーが外部認証プロバイダー（例：SSO、OAuth）でログインするたびに、ローカルのメールアドレスが外部プロバイダーから提供されたメールアドレスで上書きされます。
- ユーザーは Discourse アカウント設定内で、自身のメールアドレスをローカルで変更することができなくなります。
この機能は、Discourse サイトで設定されているすべての認証プロバイダーに適用されます。この設定は、外部サービス経由でログインするユーザーのメールの一貫性と本人確認を維持したい場合に役立ちます。
ただし、ローカルメールアドレスの正規化によって不一致が発生する可能性があるため、ユーザーはこの設定に注意する必要があります。これは、外部システムと Discourse がメールアドレスを処理またはフォーマットする方法に違いがある場合、アカウントの連携に不一致や問題が生じる可能性があることを意味します。
auth_overrides_email のデフォルト値は false です。これは、デフォルトでは Discourse が外部サイトのメールでローカルメールを上書きせず、ユーザーがメールアドレスを変更することも妨げないことを意味します。
この設定が有効になると、サイトのガーディアンおよびユーザーガーディアン スクリプトによって管理される、特定のケースでメールアドレスを編集できないなど、さまざまなユーザー権限に影響します。さらに、この設定はメールフィールドの表示方法や、ユーザーインターフェイス内でメールアドレスの変更に関する指示がユーザーに提供されるかどうかにも影響します。
「いいね！」 1
ここでも問題が発生しています。DiscourseはWordPressサイトからSSO情報を取得しており、auth_overrides_emailが有効になっています。
しかし、WordPressでユーザーのメールアドレスを更新しても、Discourseに変更は反映されません。
auth_overrides_emailを無効にしてみましたが、認証プロバイダーによって管理されているというコメントは削除されたものの、管理者である私自身や、上記で提案されたログイン/ログアウトのシミュレーションのために何度か試したユーザーになりすました場合でも、メールアドレスの横に鉛筆アイコンが表示されることはありませんでした。表示できるのはアドレスのみでした。
auth_overrides_emailを再度有効にし、WordPressでアドレスをさらに2回変更しましたが（別のものに変更してから元に戻しました）、変更はありませんでした。
何か提案はありますか？
同じ問題を抱えています。Discourseデータベースのユーザーのメールを変更する方法はありますか？コマンドラインから行うにはどうすればよいですか？
「いいね！」 1
通常、emails_editableを有効にしてからauth_overrides_emailを無効にし、その後メールを変更する必要があります。
「いいね！」 1
強制的にログアウトさせて再度ログインさせる場合、新しいメールアドレスはDiscourseに渡されますか？
「いいね！」 1