- 25 Mar, 2016 2 commits
-
-
Rémy Coutable authored
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
-
David Padilla authored
-
- 19 Jan, 2016 1 commit
-
-
Anton Baklanov authored
Fixes #2098
-
- 09 Jan, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 15 Dec, 2015 1 commit
-
-
Gabriel Mazetto authored
-
- 10 Dec, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 08 Dec, 2015 1 commit
-
-
Grzegorz Bizon authored
-
- 01 Oct, 2015 1 commit
-
-
Stan Hu authored
Closes #2867
-
- 21 Sep, 2015 1 commit
-
-
Douwe Maan authored
-
- 09 Sep, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 26 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 19 Aug, 2015 6 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 18 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 06 May, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
-
Jakub Jirutka authored
-
- 25 Apr, 2015 1 commit
-
-
Robert Speicher authored
Closes internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2269
-
- 14 Apr, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Apr, 2015 1 commit
-
-
Stan Hu authored
Closes #1305
-
- 02 Apr, 2015 1 commit
-
-
Douwe Maan authored
-
- 25 Mar, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 11 Mar, 2015 1 commit
-
-
Vyacheslav Slinko authored
-
- 25 Feb, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
See #1809.
-
- 07 Feb, 2015 2 commits
-
-
Douwe Maan authored
Closes #1932.
-
Aleks Bunin authored
Fixes #8748.
-
- 18 Jan, 2015 1 commit
-
-
Steven Burgart authored
signe-in -> signed-in go_to_gihub_for_permissions -> go_to_github_for_permissions descendand -> descendant behavour -> behaviour recepient_email -> recipient_email generate_fingerpint -> generate_fingerprint dependes -> depends Cant't -> Can't wisit -> visit notifcation -> notification sufficent_scope -> sufficient_scope? levet -> level
-
- 04 Dec, 2014 1 commit
-
-
Marin Jankovski authored
-
- 11 Nov, 2014 1 commit
-
-
Marin Jankovski authored
-
- 03 Jul, 2014 1 commit
-
-
Pierre de La Morinerie authored
* send a 'In-Reply-To' header along the 'References' header * subject of answers to an existing thread begins with 'Re: '
-
- 18 Jun, 2014 1 commit
-
-
Jacob Vosmaer authored
This reverts commit 97fd990e, reversing changes made to f451a697. Conflicts: app/mailers/emails/notes.rb app/mailers/emails/projects.rb
-
- 10 Jun, 2014 2 commits
-
-
Pierre de La Morinerie authored
* send a ‘In-Reply-To’ header along the ‘References’ header * subject of answers to an existing thread begins with ‘Re: ’ This fixes threading with at least Mail.app and Airmail.
-
Pierre de La Morinerie authored
This fixes email threading in Mail.app, that doesn't like when a thread doesn't have stable recipients. For instance, here is a possible sender-recipient combinations before: From: A To: Me New issue From: B To: Me Reply on new issue From: A To: Me Another reply Mail.app doesn't see B as a participant to the original email thread, and decides to break the thread: it will group all messages from A together, and separately all messages from B. This commit makes the thread look like this: From: A To: gitlab/project Cc: Me New issue From: B To: gitlab/project Cc: Me Reply on new issue From: A To: gitlab/project Cc: Me Another reply Mail.app sees a common recipient, and group the thread correctly.
-
- 05 May, 2014 1 commit
-
-
Philip Blatter authored
Added email threading for update emails on issues and merge requests (if the mail client support the References: mail header)
-
- 19 Feb, 2014 2 commits
-
-
Pierre de La Morinerie authored
This changes the email "From" field from "gitlab@example.com" to either: * "John Doe <gitlab@example.com>" if the author of the action is known, * "GitLab <gitlab@example.com>" otherwise. Rationale: this allow mails to appear as if they were sent by the author. It appears in the mailbox more like a real discussion between the sender and the receiver ("John sent: we should refactor this") and less like a robot notifying about something.
-
Pierre de La Morinerie authored
For instance, the email "Subject" field changes from: Mattt / Ground Control | Saving issue doesn't work sometimes (#1234) to: Ground Control | Saving issue doesn't work sometimes (#1234) Rationale: * Most people are receiving email notifications about a single fork: the project activity, issues and merge requests are happening either in a root repository or in a fork, but less often in several forks. * It removes noise from the email subject. The namespace of the project can still be read in the email body. * For Entreprise users that have a single namespace "MyEntreprise", having this repeated in every email subject is very noisy.
-