more on the wrong Group unread counts

[James Cloos <cloos@jhcloos.com>]

Here is an example of the data retrieved by nnimap for a group which
showed an incorrect unread count in Group:

write(5, "* 5 EXISTS\r\n", 12) = 12
write(5, "* 4 RECENT\r\n", 12) = 12
write(5, "* FLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)\r\n", 52) = 52
write(5, "* OK [PERMANENTFLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)]\r\n", 66) = 66
write(5, "* OK [UIDNEXT 612] Predicted next UID\r\n", 39) = 39
write(5, "* OK [UIDVALIDITY 47581] UID value\r\n", 36) = 36
write(5, "* OK [UNSEEN 2] first unseen message\r\n", 38) = 38
write(5, "133397 OK [READ-WRITE] SELECT completed\r\n", 41) = 41
write(5, "* 1 FETCH (FLAGS (\\Seen) UID 376)\r\n* 2 FETCH (FLAGS
          (\\Recent) UID 608)\r\n* 3 FETCH (FLAGS (\\Recent) UID
          609)\r\n* 4 FETCH (FLAGS (\\Recent) UID 610)\r\n* 5 FETCH
          (FLAGS (\\Recent) UID 611)\r\n", 183) = 183
write(5, "133398 OK UID FETCH completed\r\n", 31) = 31

As you can see, Group should show either 4 or 5 unread articles (5
exist, 4 are unread), but it instead claimed over 200, probably the
difference between the largest and smallest UID values returned by
the UID FETCH FLAGS call.

This is exactly the same symptom the old nnimap had, and which the
new nnimap previously avoided.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6