Fix the error mail.QUERY PARSE ERROR parserErr, STR, "Encountered "EOF"

1. Zimbra Tech Center
2. Certified
3. Fix the error mail.QUERY PARSE ERROR parserErr, STR, "Encountered "EOF"

Fix the error mail.QUERY PARSE ERROR parserErr, STR, "Encountered "<EOF>"

 - This article is a Work in Progress, and may be unfinished or missing sections.

Purpose

Fix an error when a user is login into the Web Client obtaining a popup error with the next message:

In the mailbox.log you will find the next information:

2015-05-07 09:28:25,937 INFO  [qtp509886383-3550:https://YOURIP:8443/ser
vice/soap/SearchRequest] [name=THEEMAILADDRESS@OFTHE.USER;mid=31;ip=CLIENTIP;u
a=ZimbraWebClient - GC42 (Mac)/8.6.0_GA_1153;] SoapEngine - handler exception
com.zimbra.cs.mailbox.MailServiceException: Couldn't parse query: in:
ExceptionId:qtp509886383-3550:https://208.71.113.120:8443/service/soap/SearchRequest:1430990905937:2d86683ef45c06b8
Code:mail.QUERY_PARSE_ERROR Arg:(curTok, STR, "in:") Arg:(colNo, NUM, "1") Arg:(parserErr, STR, "Encountered "<EOF>" at line 1, column 3.
Was expecting one of:
    "(" ...
    <TERM> ...
    <QUOTED_TERM> ...
    ")
...

Caused by: com.zimbra.cs.index.query.parser.ParseException: Encountered "<EOF>" at line 1, column 3.
Was expecting one of:
    "(" ...
    <TERM> ...
    <QUOTED_TERM> ...
    
        at com.zimbra.cs.index.query.parser.Parser.generateParseException(Parser.java:1213)
        at com.zimbra.cs.index.query.parser.Parser.jj_consume_token(Parser.java:1145)
        at com.zimbra.cs.index.query.parser.Parser.TextTerm(Parser.java:793)
        at com.zimbra.cs.index.query.parser.Parser.TextClause(Parser.java:364)
        at com.zimbra.cs.index.query.parser.Parser.Clause(Parser.java:279)
        at com.zimbra.cs.index.query.parser.Parser.Query(Parser.java:94)
        at com.zimbra.cs.index.query.parser.Parser.parse(Parser.java:30)
        at com.zimbra.cs.index.query.parser.QueryParser.parse(QueryParser.java:302)
        ... 56 more

Resolution

This is a common mistake that any user in the Web Client can have, if the users change the Search path for an invalid value, this wrong configuration will generate this bug, for example: Under Preferences > Mail > Displaying messages > Default Mail Search

You need to remove the value and restore it for in:inbox, or just keep it clear, and will take the COS value:

Additional Content

• For detailed explanations of and corrections for the mistakes listed above, please refer to the Tips & Tricks blog.