Hi Thanks, I guess I can handle the BAD response in my application via javamail by just catching the exception. I think in dovecot it sends back the "BAD", but also closes the connection ? Is that the expected behavior on a BAD fetch, to close the IMAP connection?
Exchange also sends back a NO , but I'll take that as a bug too :) Thanks Reinier On 9/30/07, Timo Sirainen <[EMAIL PROTECTED]> wrote: > > On Thu, 2007-09-27 at 10:18 -0400, Reinier Bezuidenhout wrote: > > AXXX FETCH 14 (UID) > > AXXX BAD Error in IMAP command FETCH: Invalid messageset > > This has been discussed in imap-protocol mailing list a few times, and > BAD is the correct reply here. For example UW-IMAP is the reference IMAP > server implementation and it gives: > > x fetch 100 uid > x BAD Bogus sequence in FETCH: Sequence out of range > > Looks like Cyrus replies with "NO" for some reason. I'd say it's a bug > in Cyrus instead. > > Actually it's been said that FETCH should never return NO, and it was a > mistake to add that to the spec in the first place. > > >