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 "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/05/05 03:43:00 UTC
[jira] [Closed] (JAMES-3689) JMSCacheableMailQueue remove is buggy
[ https://issues.apache.org/jira/browse/JAMES-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3689.
---------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
> JMSCacheableMailQueue remove is buggy
> -------------------------------------
>
> Key: JAMES-3689
> URL: https://issues.apache.org/jira/browse/JAMES-3689
> Project: James Server
> Issue Type: Bug
> Reporter: Jean Helou
> Priority: Major
> Fix For: 3.8.0
>
>
> While implementing the pulsar mailqueue we accidentally discovered this bug in theĀ JMSCacheableMailQueue:
> The test of the manageable mailqueue contract named
> {color:#172b4d}removeByRecipientShouldRemoveSpecificEmailWhenMultipleRecipients{color}
> {color:#172b4d}can be made to fail by {color}
> * {color:#172b4d}swapping the order of the recipients in the mail fixture. We tried with a few combinations and the remove never works for the first recipient.{color}
> * {color:#172b4d}adding a recipient which is similar enough to the targeted recipient (for instance removing [bob@example.co|mailto:bob@example.co] and having a mail with recipient bob@example.com){color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org