Command error. 10 - When fetching Exchange mailbox about node-imap

[mscdex]

Set the 'debug' property of the settings object to console.error when you create an instance of ImapConnection like so:

    var imap = new ImapConnection({
      username: '[email protected]',
      password: 'mygmailpassword',
      host: 'imap.gmail.com',
      port: 993,
      secure: true,
      debug: console.error
    });

That will display debug info needed to pin down the actual cause. Be sure to strip out credentials and the like when posting this debug output to a gist.

Thanks.

[stromgren]

This is the last debug rows before the error appears:

<<RECEIVED>>: 'A7 OK SEARCH completed.\r\n'

<<SENT>>: A8 UID FETCH 1,2,3,4,5,6,7……9631 (FLAGS INTERNALDATE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (FROM TO SUBJECT DATE)])

<<RECEIVED>>: 'A8 BAD Command Error. 10\r\n* BYE Connection closed.'

Note that i have removed many UID:s. There area thousands of mails in the folder.

The login debug looks like this:

Connected to host.
<<RECEIVED>>: '* OK The Microsoft Exchange IMAP4 service is ready.\r\n'
<<SENT>>: A1 CAPABILITY
<<RECEIVED>>: '* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN STARTTLS IDLE NAMESPACE LITERAL+\r\nA1 OK CAPABILITY completed.\r\n'
<<RECEIVED>>: 'A1 OK CAPABILITY completed.\r\n'
<<SENT>>: A2 LOGIN "username" "password"
<<RECEIVED>>: 'A2 OK LOGIN completed.\r\n'
<<SENT>>: A3 CAPABILITY
<<RECEIVED>>: '* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN STARTTLS IDLE NAMESPACE LITERAL+\r\nA3 OK CAPABILITY completed.\r\n'
<<RECEIVED>>: 'A3 OK CAPABILITY completed.\r\n'
<<SENT>>: A4 NAMESPACE
<<RECEIVED>>: '* NAMESPACE (("" "/")) NIL NIL\r\nA4 OK NAMESPACE completed.\r\n'
<<RECEIVED>>: 'A4 OK NAMESPACE completed.\r\n'
<<SENT>>: A5 LIST "" ""
<<RECEIVED>>: '* LIST (\\Noselect \\HasChildren) "/" ""\r\nA5 OK LIST completed.\r\n'
<<RECEIVED>>: 'A5 OK LIST completed.\r\n'

[mscdex]

Hrmm. I'm curious, if you fetch a fewer number of messages at once (say as little as 10) do you still get the same error?

Also, do other IMAP clients (e.g. PHP/Ruby/Python/Perl's IMAP client, Thunderbird, etc) not encounter this error when performing the same actions?

[stromgren]

If I fetch SEEN SINCE yesterday, it seems to work.

[mscdex]

There's not much on the internet about this error, however the one result I did find where this error was occurring was with a different IMAP client where they were trying to work with 8000 or so messages. That's what leads me to believe it may be some kind of server-side buffering issue or setting where it can't respond with that many messages for one request.

I'm marking this as closed now as it seems to be an issue with the server's IMAP implementation that I cannot do anything about.