james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-2259) IMAP search for MODSEQ is broken
Date Fri, 15 Dec 2017 04:04:00 GMT

    [ https://issues.apache.org/jira/browse/JAMES-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292009#comment-16292009

ASF GitHub Bot commented on JAMES-2259:

Github user chibenwa commented on the issue:

    I created this ticket https://issues.apache.org/jira/browse/JAMES-2259 for your issue.

> IMAP search for MODSEQ is broken
> --------------------------------
>                 Key: JAMES-2259
>                 URL: https://issues.apache.org/jira/browse/JAMES-2259
>             Project: James Server
>          Issue Type: Bug
>          Components: IMAPServer
>    Affects Versions: master
>            Reporter: Tellier Benoit
>              Labels: community, easy-fix
>             Fix For: master
> As reported by https://github.com/pedrohm in https://github.com/apache/james-project/pull/86
, the IMAP parsing layer interprets the ModSeq criterion as a flag criterion, leading to invalid
> We also missed some integration tests. They are impossible to write with MPT without
assumptions concerning the modseq.
> We can at the minimum ensure no modseq is returns for a very high modseq value.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message