From f012e07c4ffe21bf5f2661b5a7837261cbe1106c Mon Sep 17 00:00:00 2001 From: Douwe Maan Date: Fri, 2 Oct 2015 08:46:39 +0000 Subject: [PATCH] Document known issue with Reply by email and multiple application servers. --- doc/incoming_email/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/incoming_email/README.md b/doc/incoming_email/README.md index 01ab22321ed..dc5bfeb290d 100644 --- a/doc/incoming_email/README.md +++ b/doc/incoming_email/README.md @@ -2,6 +2,10 @@ GitLab can be set up to allow users to comment on issues and merge requests by replying to notification emails. +**Warning**: Do not enable Reply by email if you have **multiple GitLab application servers**. +Due to an issue with the way incoming emails are read from the mail server, every incoming reply-by-email email will result in as many comments being created as you have application servers. +A fix is being worked on. + ## Get a mailbox 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. @@ -204,4 +208,4 @@ In this example, we'll use the Gmail address `gitlab-incoming@gmail.com`. bundle exec rake gitlab:incoming_email:check RAILS_ENV=development ``` -8. Reply by email should now be working. +8. Reply by email should now be working. \ No newline at end of file