[ 
https://issues.apache.org/jira/browse/MAILBOX-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519100#comment-14519100
 ] 

Tellier Benoit commented on MAILBOX-11:
---------------------------------------

We want to solve this issue.

We identified the problem : it comes from StoreMailboxManager :: search method :

It relies on the MailboxMapper :: findMailboxWithPathLike. The behaviour of 
this metod is not standardized and differ in each and every implementation.

Then the StoreMailboxMapper selects only mailboxes satisfying the provided 
expression. We can add a check for name and namespace there.

It might be clever to standardize the MailboxMapper :: findMailboxWithPathLike 
method. This means provide standard test, test it in each implementation, and 
finally make the tests pass for each implementations.

> MailboxQuery ignore namespace
> -----------------------------
>
>                 Key: MAILBOX-11
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-11
>             Project: James Mailbox
>          Issue Type: Bug
>         Environment: Linux, JDK 1.6
>            Reporter: François-Denis Gonthier
>            Assignee: Norman Maurer
>             Fix For: 0.6
>
>
> MailboxQuery doesn't pay any attention to namespace of the mailbox it is 
> based on. For example, Mozilla Thunderbird might to mailbox search with 
> expressions like #private.%. That expression is passed directly to the 
> isExpressionMatch method of the MailboxQuery class. This has obviously 
> incorrect results.
> Arguments to the isExpressionMatch method should be parsed to separate the 
> namespace from the mailbox name or isExpressionMatch should do the parsing 
> itself. In that case the argument name should be renamed to something like 
> 'searchExpression' instead of 'name' which doesn't convey the right meaning.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to