This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git
commit f1453c0fc43402f85876b5b1455c175c0dedacae Author: Benoit Tellier <[email protected]> AuthorDate: Sun Jul 28 16:51:18 2019 +0200 JAMES-2850 Upgrade instructions for RabbitMQ MailQueue bugs --- upgrade-instructions.md | 34 ++++++++++++++++++++++++++++++++-- 1 file changed, 32 insertions(+), 2 deletions(-) diff --git a/upgrade-instructions.md b/upgrade-instructions.md index 6229179..426fe4a 100644 --- a/upgrade-instructions.md +++ b/upgrade-instructions.md @@ -16,8 +16,38 @@ Changes to apply between 3.3.x and 3.4.x will be reported here. Change list: - - [Upgrade to ElasticSearch 6.3](#upgrade-to-elasticsearch-6.3) - + - [Upgrade to ElasticSearch 6.3](#upgrade-to-elasticsearch-63) + - [Enqueuing several times a mail with the same name](#enqueuing-several-times-a-mail-with-the-same-name) + - [RabbitMQ Mail Queue with multiple specific headers for a single recipient](#rabbitmq-mail-queue-with-multiple-specific-headers-for-a-single-recipient) + +#### RabbitMQ Mail Queue with multiple specific headers for a single recipient + +Date: 31/07/2019 + +SHA-1: f19642aef4a67cd6675f66278792ba4aa85d6d6e + +JIRA: https://issues.apache.org/jira/browse/JAMES-2850 + +Concerned products: (experimental) RabbitMQ MailQueue + +RabbitMQ MailQueue projection in Cassandra relies on a map allowing a single specific header per recipient header. This +limitation causes rejection of emails with multiple per-recipient headers (which happens when forwarding to a remote server +a mail checked against SpamAssassin). + +In order to fix this issue, the structure of the underlying table was updated. A new table is created upon the first startup +following the upgrade, and the old one is ignored. + +Impact: the mails enqueued before the update can not be browsed nor removed from the queue after the update. + +Recommendation: Conduct this update with an empty mail queue. + +To do so: + + - Given a distributed Guice James server + - Stop incoming traffic + - Monitor the mailQueues and wait them to be empty (spool & outgoing) + - Once empty, upgrade James server and re-enable incoming traffic. + #### Enqueuing several times a mail with the same name Date: XX/06/2019 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
