# Notification reasons in the email?
**URL:** https://meta.discourse.org/t/notification-reasons-in-the-email/132009
**Category:** Feature
**Created:** [October 27, 2019, 9:42pm UTC](https://meta.discourse.org/t/notification-reasons-in-the-email/132009 "2019-10-27T21:42:50Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@nedbat](https://meta.discourse.org/u/nedbat)
#### Post date: [October 27, 2019, 9:42pm UTC](https://meta.discourse.org/t/notification-reasons-in-the-email/132009/1 "2019-10-27T21:42:50Z")
My users are asking if there is a way to write gmail filters to treat notifications differently based on the reason for the notification. I couldn’t find a way, but I’m reminded of how GitHub deals with this: [https://help.github.com/en/github/receiving-notifications-about-activity-on-github/about-email-notifications](https://help.github.com/en/github/receiving-notifications-about-activity-on-github/about-email-notifications). They add a cc pseudo-address that encodes the reason for the notification, which makes it easily available to filters.
Is there something like this I’m missing, or could it be added?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [October 28, 2019, 3:34am UTC](https://meta.discourse.org/t/notification-reasons-in-the-email/132009/2 "2019-10-28T03:34:11Z")
I don’t understand the purpose of this request? Can you explain why this would be useful / necessary with some real world examples?
---
### Author:  [@nedbat](https://meta.discourse.org/u/nedbat)
#### Post date: [October 28, 2019, 12:39pm UTC](https://meta.discourse.org/t/notification-reasons-in-the-email/132009/3 "2019-10-28T12:39:38Z")
In my [user’s own words](https://discuss.openedx.org/t/gmail-filters-for-direct-mentions/770?u=nedbat):
> Has anyone figured out how to create a gmail filter to flag/label/otherwise distinguish messages from [discuss.openedx.org](http://discuss.openedx.org/) which directly mention you? I’ve tried filters like this, but they just match everything, since the email “to” field always matches my name:
>
> ```plaintext
> list:(development.discuss.openedx.org) "@jill"
> list:(development.discuss.openedx.org) +"@jill"
>
> ```
>
> I’m afraid my only options are to a) remember to check the [/notifications/mentions](https://discuss.openedx.org/u/jill/notifications/mentions) page often, or b) change my Discourse notification settings so that I don’t get every post sent to my Forums inbox, just the direct mentions or followed posts… which would be ok, but I do like having a very searchable record in my inbox.
---
### Author:  [@jill](https://meta.discourse.org/u/jill)
#### Post date: [October 28, 2019, 12:46pm UTC](https://meta.discourse.org/t/notification-reasons-in-the-email/132009/4 "2019-10-28T12:46:12Z")
Hi @codinghorror 🙂
I’m a member of the [discuss.openedx.org](http://discuss.openedx.org) community, and would like to:
1. get all new posts to that forum in my Gmail Forums list, so I can scan them easily, and visit them when I need more info.
2. make any posts which mention me personally be starred or otherwise flagged in my Gmail Inbox, so I know I need to respond to them ASAP.
Currently, I’ve got #1, which is great. But because all the Discourse notification emails are sent to my `jill@email.com`, and because [gmail doesn’t have an email `body:` filter](https://support.google.com/mail/answer/7190) or recognise the special `@` character in search text, there’s no way for me to specifically filter messages which have `@jill` in them.
Granted, these are flaws in Gmail’s filtering, not Discourse’s problem 🙂 But if there was a separate field somewhere with these notifications that provided the info I needed, I could work around these flaws.
---
### Author:  [@eLRuLL](https://meta.discourse.org/u/eLRuLL)
#### Post date: [August 26, 2020, 11:22pm UTC](https://meta.discourse.org/t/notification-reasons-in-the-email/132009/5 "2020-08-26T23:22:16Z")
maybe something like Github, where they include the `mention@noreply.github.com` email in the recipients, this would be super handy really.