[
https://issues.apache.org/jira/browse/JAMES-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469801#comment-17469801
]
Benoit Tellier commented on JAMES-3689:
---------------------------------------
Answer of Jean on the ML
{code:java}
Hello Benoit
Yes the PR github.com/apache/james-project/pull/824 fixes this bug
and the errors we encounter on the pulsar mailqueue PR
Jean
{code}
I just merged https://github.com/apache/james-project/pull/824 - should we
close this JIRA ticket as well?
> 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
>
> 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 [[email protected]|mailto:[email protected]] and
> having a mail with recipient [email protected]){color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
