Continuing the discussion from Mail does not go out after recent update … I experienced this issue yesterday before the fixes were released. I was coincidentally migrating my notification email to a new domain and setting it up while the emails were broken. It led to a very confusing couple of hours! On that note, I’ve spotted recently that emails no longer go out with the sender name that includes the site name. Where it used to say User Via [Site] it now just says User as the email sender name. Noticed this across more than one Discourse instance. Having done some reading it appears there was previously a site setting named from_email which allowed for specifying this, but it appears to have been removed. Is there any chance this is another bug related to these same changes perhaps? Or was there a new method for doing things / intentional design change I might have missed?

[imagen] Saen: Old From: Saen via Collectives New From: Saen The relevant change is: https://github.com/discourse/discourse/commit/826d3463945f2917ee6f6635adf5df2919962f25

[imagen] Saen: Where it used to say User Via [Site] it now just says User as the email sender name. The via is likely added by the MUA to show the Sender. Can you dig out and show the From, Reply-To, Subject, and Sender headers from old and new emails? [imagen] Saen: there was previously a site setting named from_email which allowed for specifying this There was not. There’s: notification_email # env var: DISCOURSE_NOTIFICATION_EMAIL reply_by_email_address # env var: DISCOURSE_REPLY_BY_EMAIL_ADDRESS

There seems to be no difference in these headers between the old and new emails, except for the fact that the old From headers include the via statement. (For context my site name is Collectives, my old domain was minecraftengineering.org and the new domain is saen.dev). Everything was switched over except the notification email, which I didn’t change until a few days ago (I still own the old domain). Old From: Saen via Collectives New From: Saen (Didn’t Change) Reply-To: Collectives Subject: [My Topic Title] X-Discourse-Sender: Saen Maybe it’s related to the fact that I previously had different domains in use for the notification and reply emails, and now I have the same domain across both. Perhaps this triggers something in the clients that the “via” is no longer necessary?

[imagen] supermathie: UX: improve sender name in emails (#36974) · discourse/discourse@826d346 · GitHub I don’t particularly care about this myself, but how is including less information about why you’re getting email an improvement? Another topic about this change (or this family of changes) complained that now it says something like “you got this because they replied to to a topic you were watching” (which has MORE information than the old way).

[imagen] pfaffman: I don’t particularly care about this myself, but how is including less information about why you’re getting email an improvement? I can’t answer authoritatively, but I suspect it’s due to the site’s name already being present in the Subject line.

[imagen] supermathie: but I suspect it’s due to the site’s name already being present in the Subject line. Ah. That would make sense. So the Basic Principle is reducing redundancy here.

Encabezados de correo electrónico de: perdieron el texto "via SITENAME"

Soporte del producto

supermathie (Michael Brown) 19 Enero, 2026 17:55 4

El cambio relevante es:

Tema		Respuestas	Vistas
Change Send As in Email Notifications Feature	23	5970	4 Enero 2019
Avoiding the forum name in the email sender? Product Support	5	924	5 Febrero 2019
Forum topic creator name is used instead of notifier in sent emails with the Notify feature Bug	3	791	25 Mayo 2021
How do I change the email "FROM" address? Product Support	8	1033	5 Septiembre 2020
Poster's name in From email instead of admin/orignal topic starter Product Support	4	725	6 Julio 2021

Encabezados de correo electrónico de: perdieron el texto "via SITENAME"

Temas relacionados