Debugging A5 BAD Unexpected extra arguments to Search ?

[ellie timoney]

Hi Kristian,

The "A5" and "A7" are just the "tags" associated with the client's search commands, they have no semantic value.  The client prefixes each command with some tag, and then the server uses the same tag in the response (so that you can identify which response applies to which command).  In these two cases, your client has chosen "A5" and "A7" as tags.  Tags are described in detail here: https://tools.ietf.org/html/rfc3501#section-2.2.1

Your Java/Java Mail application hopefully has a feature to log the commands it's sending.  If you turn this on, you'll be able to see which bad search commands were resulting in the error (by matching response tags and command tags), and then compare the command syntax to the expected syntax from the relevant RFCs.

Cheers,

ellie

On Tue, Oct 23, 2018, at 8:58 PM, Kristian Rink wrote:
> Hi all;
> 
> we're running a Java (and Java Mail) based application interacting with 
> our cyrus imapd server. Trying to use complex search terms (searching 
> for multiple criterias, such as message-id and message date), we 
> regularly (all the time?) end up with messages such as
> 
> A5 BAD Unexpected extra arguments to Search    or
> A7 BAD Unexpected extra arguments to Search
> 
> Questions here: What's the difference between A5 and A7? Any way to 
> debug what exactly is wrong about our search terms here?
> 
> TIA and all the best,
> Kristian