You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (Jira)" <se...@james.apache.org> on 2020/06/17 13:42:00 UTC
[jira] [Commented] (JAMES-2541) In order to support distributed
deployment, we should write a MailQueue implementation using RabbitMQ
[ https://issues.apache.org/jira/browse/JAMES-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138443#comment-17138443 ]
Ioan Eugen Stan commented on JAMES-2541:
----------------------------------------
Is this still an issue? Can we close this?
> In order to support distributed deployment, we should write a MailQueue implementation using RabbitMQ
> -----------------------------------------------------------------------------------------------------
>
> Key: JAMES-2541
> URL: https://issues.apache.org/jira/browse/JAMES-2541
> Project: James Server
> Issue Type: Task
> Components: Queue
> Affects Versions: 3.1.0
> Reporter: Matthieu Baechler
> Priority: Major
> Fix For: 3.2.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org