gitlab-org--gitlab-foss/doc/reply_by_email/README.md

185 lines
5.7 KiB
Markdown
Raw Normal View History

2015-08-19 20:58:14 +00:00
# Reply by email
GitLab can be set up to allow users to comment on issues and merge requests by replying to notification emails.
2015-08-24 21:46:45 +00:00
## Get a mailbox
2015-08-19 20:58:14 +00:00
2015-08-24 21:46:45 +00:00
Reply by email requires an IMAP-enabled email account, with a provider or server that supports [email sub-addressing](https://en.wikipedia.org/wiki/Email_address#Sub-addressing). Sub-addressing is a feature where any email to `user+some_arbitrary_tag@example.com` will end up in the mailbox for `user@example.com`, and is supported by providers such as Gmail, Yahoo! Mail, Outlook.com and iCloud, as well as the Postfix mail server which you can run on-premises.
2015-08-24 18:23:24 +00:00
2015-08-24 21:46:45 +00:00
If you want to use Gmail with Reply by email, make sure you have [IMAP access enabled](https://support.google.com/mail/troubleshooter/1668960?hl=en#ts=1665018) and [allow less secure apps to access the account](https://support.google.com/accounts/answer/6010255).
To set up a basic Postfix mail server with IMAP access on Ubuntu, follow [these instructions](./postfix.md).
2015-08-24 18:23:24 +00:00
2015-08-19 20:58:14 +00:00
## Set it up
2015-08-24 18:23:24 +00:00
In this example, we'll use the Gmail address `gitlab-replies@gmail.com`.
2015-08-19 20:58:14 +00:00
### Installations from source
2015-08-20 00:43:36 +00:00
1. Go to the GitLab installation directory:
```sh
cd /home/git/gitlab
```
2015-08-19 20:58:14 +00:00
1. Find the `reply_by_email` section in `config/gitlab.yml`, enable the feature and enter the email address including a placeholder for the `reply_key`:
2015-08-20 00:43:36 +00:00
```sh
sudo editor config/gitlab.yml
```
2015-08-19 20:58:14 +00:00
```yaml
reply_by_email:
enabled: true
address: "gitlab-replies+%{reply_key}@gmail.com"
```
As mentioned, the part after `+` is ignored, and this will end up in the mailbox for `gitlab-replies@gmail.com`.
2015-08-25 17:23:55 +00:00
2. Copy `config/mail_room.yml.example` to `config/mail_room.yml`:
2015-08-19 20:58:14 +00:00
```sh
2015-08-20 00:43:36 +00:00
sudo cp config/mail_room.yml.example config/mail_room.yml
2015-08-19 20:58:14 +00:00
```
3. Uncomment the configuration options in `config/mail_room.yml` and fill in the details for your specific IMAP server and email account:
2015-08-20 00:43:36 +00:00
```sh
sudo editor config/mail_room.yml
```
2015-08-19 20:58:14 +00:00
```yaml
:mailboxes:
-
# IMAP server host
:host: "imap.gmail.com"
# IMAP server port
:port: 993
# Whether the IMAP server uses SSL
:ssl: true
# Email account username. Usually the full email address.
:email: "gitlab-replies@gmail.com"
# Email account password
:password: "[REDACTED]"
# The name of the mailbox where incoming mail will end up. Usually "inbox".
:name: "inbox"
# Always "sidekiq".
:delivery_method: sidekiq
:delivery_options:
# The URL to the Redis server used by Sidekiq. Should match the URL in config/resque.yml.
:redis_url: redis://localhost:6379
# Always "resque:gitlab".
:namespace: resque:gitlab
# Always "incoming_email".
:queue: incoming_email
# Always "EmailReceiverWorker"
:worker: EmailReceiverWorker
```
2015-08-25 17:23:55 +00:00
4. Copy `lib/support/init.d/gitlab.default.example` to `/etc/default/gitlab`, if that does not already exist:
2015-08-19 20:58:14 +00:00
```sh
2015-08-25 17:23:55 +00:00
[ -f /etc/default/gitlab ] || sudo cp lib/support/init.d/gitlab.default.example /etc/default/gitlab
2015-08-19 20:58:14 +00:00
```
5. Edit `/etc/default/gitlab` to enable `mail_room`:
2015-08-20 00:43:36 +00:00
```sh
sudo editor /etc/default/gitlab
```
2015-08-25 17:23:55 +00:00
Either change `mail_room_enabled=false` to the below, or add it at the bottom of the file:
2015-08-19 20:58:14 +00:00
```sh
mail_room_enabled=true
```
2015-08-21 22:03:16 +00:00
6. Restart GitLab:
2015-08-19 20:58:14 +00:00
```sh
sudo service gitlab restart
```
2015-08-21 22:03:16 +00:00
7. Check if everything is configured correctly:
```sh
sudo bundle exec rake gitlab:reply_by_email:check RAILS_ENV=production
```
2015-08-19 20:58:14 +00:00
8. Reply by email should now be working.
### Omnibus package installations
TODO
### Development
1. Go to the GitLab installation directory.
1. Find the `reply_by_email` section in `config/gitlab.yml`, enable the feature and enter the email address including a placeholder for the `reply_key`:
```yaml
reply_by_email:
enabled: true
address: "gitlab-replies+%{reply_key}@gmail.com"
```
As mentioned, the part after `+` is ignored, and this will end up in the mailbox for `gitlab-replies@gmail.com`.
2015-08-25 17:23:55 +00:00
2. Copy `config/mail_room.yml.example` to `config/mail_room.yml`:
```sh
sudo cp config/mail_room.yml.example config/mail_room.yml
```
3. Uncomment the configuration options in `config/mail_room.yml` and fill in the details for your specific IMAP server and email account:
```yaml
:mailboxes:
-
# IMAP server host
:host: "imap.gmail.com"
# IMAP server port
:port: 993
# Whether the IMAP server uses SSL
:ssl: true
# Email account username. Usually the full email address.
:email: "gitlab-replies@gmail.com"
# Email account password
:password: "[REDACTED]"
# The name of the mailbox where incoming mail will end up. Usually "inbox".
:name: "inbox"
# Always "sidekiq".
:delivery_method: sidekiq
:delivery_options:
# The URL to the Redis server used by Sidekiq. Should match the URL in config/resque.yml.
:redis_url: redis://localhost:6379
# Always "resque:gitlab".
:namespace: resque:gitlab
# Always "incoming_email".
:queue: incoming_email
# Always "EmailReceiverWorker"
:worker: EmailReceiverWorker
```
4. Uncomment the `mail_room` line in your `Procfile`:
```yaml
mail_room: bundle exec mail_room -q -c config/mail_room.yml
```
6. Restart GitLab:
```sh
bundle exec foreman start
```
7. Check if everything is configured correctly:
```sh
bundle exec rake gitlab:reply_by_email:check RAILS_ENV=development
```
8. Reply by email should now be working.