2020-10-24 23:57:45 +05:30
---
stage: Plan
group: Certify
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
2016-11-03 12:29:30 +05:30
# Reply by email
2020-10-24 23:57:45 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/1173) in GitLab 8.0.
2016-11-03 12:29:30 +05:30
GitLab can be set up to allow users to comment on issues and merge requests by
replying to notification emails.
## Requirement
2018-12-05 23:21:45 +05:30
Make sure [incoming email ](incoming_email.md ) is set up.
2016-11-03 12:29:30 +05:30
## How it works?
### 1. GitLab sends a notification email
When GitLab sends a notification and Reply by email is enabled, the `Reply-To`
header is set to the address defined in your GitLab configuration, with the
`%{key}` placeholder (if present) replaced by a specific "reply key". In
addition, this "reply key" is also added to the `References` header.
### 2. You reply to the notification email
When you reply to the notification email, your email client will:
- send the email to the `Reply-To` address it got from the notification email
- set the `In-Reply-To` header to the value of the `Message-ID` header from the
notification email
- set the `References` header to the value of the `Message-ID` plus the value of
the notification email's `References` header.
### 3. GitLab receives your reply to the notification email
When GitLab receives your reply, it will look for the "reply key" in the
following headers, in this order:
1. the `To` header
1. the `References` header
If it finds a reply key, it will be able to leave your reply as a comment on
the entity the notification was about (issue, merge request, commit...).
For more details about the `Message-ID` , `In-Reply-To` , and `References headers` ,
2021-01-29 00:20:46 +05:30
see [RFC 5322 ](https://tools.ietf.org/html/rfc5322#section-3.6.4 ).
