[JAMES-2541] In order to support distributed deployment, we should write a MailQueue implementation using RabbitMQ

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 3.2.0
• Component/s: Queue
• Assignee: Unassigned
• Reporter: Matthieu Baechler
• Created: 05/Sep/18 08:56
• Updated: 19/Jun/20 00:57
• Resolved: 17/Jun/20 13:47

Description

Default MailQueue for Cassandra/Elasticsearch James product is embedded ActiveMQ.
After a review of available distributed MQ, we decided that we should support RabbitMQ to replace ActiveMQ in distributed scenario.
And as we don't want to rely on filesystem for mail content neither, we decided that only meta-data would go into the MQ and that the raw email would be stored in a blob-store.
This ticket is supposed to track progress at implementing basic MailQueueFactoryContract and MailQueueContract on top of RabbitMQ and blob-store.