Commit 6b211f9e authored by Marcin Sedlak-Jakubowski's avatar Marcin Sedlak-Jakubowski

Merge branch 'jh-add-received-email-header-docs' into 'master'

Add documentation on new email header

See merge request gitlab-org/gitlab!81806
parents 70b73351 2830ba88
...@@ -68,11 +68,16 @@ this method only supports replies, and not the other features of [incoming email ...@@ -68,11 +68,16 @@ this method only supports replies, and not the other features of [incoming email
## Accepted headers ## Accepted headers
Email is processed correctly when a configured email address is present in one of the following headers: > Accepting `Received` headers [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81489) in GitLab 14.9 [with a flag](feature_flags.md) named `use_received_header_for_incoming_emails`. Enabled by default.
Email is processed correctly when a configured email address is present in one of the following headers
(sorted in the order they are checked):
- `To` - `To`
- `References`
- `Delivered-To` - `Delivered-To`
- `Envelope-To` or `X-Envelope-To` - `Envelope-To` or `X-Envelope-To`
- `Received`
In GitLab 14.6 and later, [Service Desk](../user/project/service_desk.md) In GitLab 14.6 and later, [Service Desk](../user/project/service_desk.md)
also checks accepted headers. also checks accepted headers.
...@@ -84,6 +89,9 @@ However, it might not include the configured GitLab email address if: ...@@ -84,6 +89,9 @@ However, it might not include the configured GitLab email address if:
- The address was included when using "Reply all". - The address was included when using "Reply all".
- The email was forwarded. - The email was forwarded.
The `Received` header can contain multiple email addresses. These are checked in the order that they appear.
The first match is used.
## Rejected headers ## Rejected headers
To prevent unwanted issue creation from automatic email systems, GitLab ignores all incoming email To prevent unwanted issue creation from automatic email systems, GitLab ignores all incoming email
......
...@@ -47,6 +47,8 @@ following headers, in this order: ...@@ -47,6 +47,8 @@ following headers, in this order:
1. `References` header 1. `References` header
1. `Delivered-To` header 1. `Delivered-To` header
1. `Envelope-To` header 1. `Envelope-To` header
1. `X-Envelope-To` header
1. `Received` header
If it finds a reply key, it leaves your reply as a comment on If it finds a reply key, it leaves your reply as a comment on
the entity the notification was about (issue, merge request, commit...). the entity the notification was about (issue, merge request, commit...).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment