4 commits

Author	SHA1	Message	Date
Toon Claes	b1f236164e	Put fallback reply-key address first in the References header ... The References header is an ordered list of mails, and some clients only look at the last mail in the list to determine to which mail the mail is in reply to. Therefore, to be a less obtrusive as possible, put the fallback address first. Some info about the reply key lookup in the References header: https://docs.gitlab.com/ee/administration/reply_by_email.html#how-it-works	2018-07-27 15:12:52 +02:00
Rémy Coutable	9f218fc184	Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature ... A few things to note: - The IncomingEmail feature is now enabled even without a correctly-formatted sub-address - Message-ID for new thread mail are kept the same so that subsequent notifications to this thread are grouped in the thread by the email service that receives the notification (i.e. In-Reply-To of the answer == Message-ID of the first thread message) - To maximize our chance to be able to retrieve the reply key, we look for it in the In-Reply-To header and the References header - The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]" - Improve docs thanks to Axil	2016-03-25 13:05:15 +01:00
David Padilla	31e76baf61	Fix #2364. Fall back to In-Reply-To header when reply key not available	2016-03-25 13:05:15 +01:00
Douwe Maan	83081f1673	Start on tests.	2015-08-19 18:00:13 -07:00