<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">>On Sun, Jun 26, 2011 at 11:32 PM, chris coleman wrote:<br><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;">>> Brandon, Thanks for the clarification.<br>>><br>>> So this issue will be resolved once imaplib2 properly digests the untagged<br>>> 2nd CAPABILITIES response after login to Gmail.<br>>><br>>> There is still this issue: you seem to be saying that Gmail sometimes (or<br>>> always) doesn't announce UIDPLUS in the 1st CAPABILITIES response. This<br>>> implies SOME users are on Gmail servers that don't support UIDPLUS, so all<br>>> Gmail servers are obliged to include defer announcing UIDPLUS support until<br>>> the 2nd CAPABILITIES
response. So the same crash will happen if the user is<br>>> on one of those servers that do not support UIDPLUS.<br>><br>>Ah, I see the confusion.<br>><br>>UIDPLUS was rolled out incrementally, but its now on for all users,<br>>and has been for at least a year. We could graduate it to being<br>>always on and being announced pre-login, we just haven't done it yet.<br><br>My opinion: graduating UIDPLUS to be always on and announced pre-login would definitely be appropriate.<br><br>@Sebastian: What's your thoughts on fixing imaplib2 or offlineimap, so they respond properly when an untagged CAPABILITIES response arrives at any time. Just in case, one day a user gets an IMAP server that changes the capabilities. Imagine a cluster scenario, the 1st IMAP server goes down, the load balancer switches over to the 2nd IMAP server, which announces different capabilities.<br><br>>And I just logged in and checked our
code, my guess at the possible<br>>failure scenario is wrong, I do believe that we should handle that<br>>search backup correctly. I'll have to write a test or two to see if<br>>there's some other bug there.<br>><br>>Brandon<br><br>Very cool. It's great to have your input Brandon.<br>Chris<br><br></div></div></div></body></html>