#17 Invalid Fetch command

closed-fixed
Ethan Sommer
None
5
2001-10-19
2001-09-23
Carl Gherardi
No

Had to kill althea after clicking my inbox. The
progress meter for gathering my mail comes up and
doesn't move because the server has responded BAD

./althea -V

Verbose:2
Server loaded
S: * OK Microsoft Exchange IMAP4rev1 server version
5.5.2653.23 (MSexchangeserver.etc) ready
C: a001 login "myusername" "mypassword"

S: a001 OK LOGIN completed.
C: a002 list "" "INBOX"

S: * LIST (\Marked) "/" INBOX
S: a002 OK LIST completed.
C: a002 list "" "~/mail/*"

S: a002 OK LIST completed.
You selected server MSexchangeserver.etc
C: a011 noop

S: a011 OK NOOP completed.
You selected folder INBOX
C: a003 SELECT "INBOX"

S: * 24 EXISTS
S: * 0 RECENT
S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft)
S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged
\Deleted \Draft)]
S: * OK [UNSEEN 19] Is the first unseen message
S: * OK [UIDVALIDITY 5385] UIDVALIDITY value.
S: a003 OK [READ-WRITE] SELECT completed.
0

C: aHEADER uid FETCH 1:4294967296 (BODY.PEEK[header]
FLAGS BODYSTRUCTURE)

getting headers for 1
S: aHEADER BAD Protocol Error: "Invalid message set in
FETCH command"
getting flags and bodystructure for 1
Killed

Discussion

  • Ethan Sommer
    Ethan Sommer
    2001-10-11

    • assigned_to: nobody --> sommere
     
  • Ethan Sommer
    Ethan Sommer
    2001-10-16

    Logged In: YES
    user_id=28252

    it should have been 1:4294967295, please download the
    current CVS tree and give it a try...

     
  • Ethan Sommer
    Ethan Sommer
    2001-10-19

    • status: open --> closed-fixed