summaryrefslogtreecommitdiff
path: root/config/mail_room.yml
Commit message (Collapse)AuthorAgeFilesLines
* Support multiple Redis instances based on queue typePaul Charlton2017-07-111-2/+2
|
* Use newer mail_room to get `require_relative` supportGabriel Mazetto2017-02-201-4/+1
|
* Make mail_room idle_timeout option configurable.Marin Jankovski2016-11-161-1/+1
|
* Updated mail_room and added sentinel support to Reply by Email21645-mail_room_sentinelGabriel Mazetto2016-10-261-1/+16
|
* Fix reply-by-email not working due to queue name mismatchsh-fix-mailroom-configStan Hu2016-10-231-1/+1
| | | | | | | | | | mail_room was configured to deliver mail to the `incoming_email` queue while `EmailReceiveWorker` was reading the `email_receiver` queue. Adds a migration that repeats the work of a previous migration to ensure all mails that wound up in the old queue get processed. Closes #23689
* Synced mail_room.yml with the one in omnibusGabriel Mazetto2016-08-041-0/+4
| | | | | Added a comment to remember developers to open merge request to omnibus in future changes of the file.
* Fixed specs for Gitlab::Redis and code for Redis Sentinel supportGabriel Mazetto2016-08-041-1/+1
|
* Deduplicated resque.yml loading from several placesGabriel Mazetto2016-08-041-32/+17
| | | | We will trust redis configuration params loading to Gitlab::RedisConfig.
* Don't require Gitlab::Redis in mail_room.yml if it's already definedRémy Coutable2016-06-101-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Add Gitlab::Redis connection poolJacob Vosmaer2016-04-041-2/+2
|
* Improve and finish the fallback to the In-Reply-To and References header for ↵2364-fallback-to-in-reply-to-headerRémy Coutable2016-03-251-1/+1
| | | | | | | | | | | | | | | | 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
* Parse config/resque.yml in one place onlyJacob Vosmaer2016-03-091-7/+2
|
* Don't load all of GitLab in mail_roomDouwe Maan2016-02-261-36/+49
| | | | Fixes #12731
* Make Reply by email easier to configureDouwe Maan2015-10-131-0/+39