For more information about the differences between participating and watching notifications, see "About notifications."
After enabling email notifications, GitHub Enterprise Server will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on GitHub Enterprise Server. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. For more information about enabling email notifications, see "Choosing the delivery method for your notifications."
Note: You'll only receive email notifications if outbound email support is enabled on your GitHub Enterprise Server instance. For more information, contact your site administrator.
Tip: If you receive both web and email notifications, you can automatically sync the read or unread status of the notification so that web notifications are automatically marked as read once you've read the corresponding email notification. To enable this sync, your email client must be able to view images from the no-reply email address for your GitHub Enterprise Server instance, which your site administrator configures.
Filtering email notifications
Each email notification that GitHub Enterprise Server sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all GitHub Enterprise Server notifications, or certain types of GitHub Enterprise Server notifications.
Email notifications from GitHub Enterprise Server contain the following header information:
| Header | Information |
|---|---|
From address | This address will always be 'the no-reply email address configured by your site administrator'. |
To field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. |
Cc address | GitHub Enterprise Server will Cc you if you're subscribed to a conversation. The second Cc email address matches the notification reason. The suffix for these notification reasons is based on the no-reply email address configured by your site administrator. The possible notification reasons are:
|
mailing list field | This field identifies the name of the repository and its owner. The format of this address is always <repository name>.<repository owner>.[hostname]. |
X-GitHub-Severity field | Email notifications for security alerts that affect one or more repositories include the X-GitHub-Severity header field. You can use the value of the X-GitHub-Severity header field to filter email notifications for security alerts. The possible severity levels are:
|