# Site title being used in subject, despite email prefix being used

**URL:** https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578
**Category:** Feature
**Created:** [3 Junho , 2015 01:10 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578 "2015-06-03T01:10:11Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [3 Junho , 2015 01:10 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/1 "2015-06-03T01:10:11Z")

</div>

Continuing the discussion from [Clarification on site\_domain\_name and site\_name](https://meta.discourse.org/t/clarification-on-site-domain-name-and-site-name/18136/8):

> [@watchmanmonitor](#):
>
> I just tested this on my hosted discourse, and the {%site\_name} in the plain english emails is replaced with the email prefix, which I would expect to only be used in subject lines.

This is still an issue on my hosted version. Is there some workaround until a fix can be had?

![](https://global.discourse-cdn.com/meta/original/3X/3/0/304691f78b78234c429d69db20ca6ff2468ce6f9.png)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3 Junho , 2015 01:31 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/2 "2015-06-03T01:31:13Z")

</div>

That does not apply to digests, but perhaps it should. @techapj can you normalize that code?

---

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [3 Junho , 2015 01:48 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/3 "2015-06-03T01:48:25Z")

</div>

I would love this as well. Our site title is way too long to be included in every email subject as a prefix. Thanks!

---

<div class="post-metadata">

### Author: ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [3 Junho , 2015 16:55 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/4 "2015-06-03T16:55:08Z")

</div>

Okay, done:

[https://github.com/discourse/discourse/pull/3527/](https://github.com/discourse/discourse/pull/3527/)

---

<div class="post-metadata">

### Author: ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)
#### Post date: [3 Junho , 2015 17:13 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/5 "2015-06-03T17:13:39Z")

</div>

I’m not sure this is a good idea. Notifications are received very often, perhaps every day. For those, a short slug works well.

The idea with a digest is it’s received only occasionally, and reminding people to come back to the site. Having the short slug version may not make it obvious from the subject line what the email is about or who/where it’s from. Especially now that the subject is shortened to just “Digest” with no date, the subject line shouldn’t be too long in most situations.

I for one want the full site title in the “come back” digest, just not the hundreds-per-day notifications.

---

<div class="post-metadata">

### Author: ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [3 Junho , 2015 17:29 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/6 "2015-06-03T17:29:34Z")

</div>

To me, it’s all about unified email subject lines.. for filtering and sanity.

---

<div class="post-metadata">

### Author: ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [5 Junho , 2015 13:45 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/7 "2015-06-05T13:45:24Z")

</div>

That said, I just got a weekly digest from [Commonmark](http://talk.commonmark.org/)

> [CMD] Digest

and to @downey’s point, just seeing `CMD` in the subject line didn’t help me much.

I suppose forum operators really need to make sure their “From” name is meaningful (their case `CommonMark Discussion digest` )

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5 Junho , 2015 23:08 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/8 "2015-06-05T23:08:50Z")

</div>

They wanted the short version, so that is the community’s desire in that case..

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [4 Dezembro , 2025 11:35 UTC](https://meta.discourse.org/t/site-title-being-used-in-subject-despite-email-prefix-being-used/29578/9 "2025-12-04T11:35:58Z")

</div>


