UID does not comply with IMAP standard.

[James Ridge]

For a long time, I had been using another proxy by Bravura software to convert Yahoo
mail to IMAP, but I had to abandon it because of persistent error while checking mail since October 2012.   I
attempted to contact Bravura but they are not responded.  So I switched to this proxy just this year.  Alas, I have the same error. 

"The UID of the message changed unexpectedly.  This typically indicates a server bug. 
Your program may not function properly after this.\" 

MsgSeqNum  3376; Previous UID 144531, New UID:  133875
Protocol: IMAP
Server: localhost
Port: 9143
Error Code:  0x800CCCDB

I also get the error "your server reported a UID that does not comply with the IMAP standard.   This typically indicates a server bug.  Your program may not fuction properly after this."

MsgSeqNum  4598; Previous UID 161379, Prev UID:  161379, Next UID: 0
Protocol: IMAP
Server: localhost
Port: 9143
Error Code:  0x800CCCDB

I have been researching and found that Zimbra also has this issue:  https://bugzilla.zimbra.com/show_bug.cgi?id=62160
and they do not have solution. 

I am using Outlook 2007.  I archived all my Yahoo mail in a separate folder thinking it was an email causing the error.  I have re-created the account in Outlook.  I still have the error when it checks for email.

Any guidance, suggestions are most welcomed.

[James Ridge]

After more research and trial & error, I archived my entire Inbox and Sent messages.   The UID problem has disappeared.

[AdamS]

Thanks for the information and adding your solution.

The proxy has nothing to do with UID.  However anyone using the proxy might encounter this error, so it's valuable to have some information here.

I have done a few quick searches and used by background knowledge of IMAP to put together some theories.

- It appears that Yahoo doesn't strictly follow the rules for UID.  This is not too surprising because Yahoo is first and foremost a web-based email service, with IMAP as a secondary mechanism.
- Some reports elsewhere suggest that the problem may be triggered by modifying emails on the web interleaved with IMAP access.
- It appears that Outlook can be quite fussy about any non-strictness.  Potentially using another client would avoid the problem, although the OP suggests Zimbra is similar.  I never hit this problem using Thunderbird, but then I never use the web interface so that may be the reason.

The OP has identified a workaround, although one that is somewhat tedious to follow.  It seems possible that the problem would recur and workaround need to be repeated.

To recap, there's nothing the proxy can do to help.  Yahoo probably aren't rushing to fix the bug their end.  So you have to find a way around it in your client software.

[Anonymous]

The best answer I have found is here: http://www.windowsitpro.com/article/outlook/accessed-outlook-account-web-browser-outlook-error-message-uid-doesnt-comply-imap-standard-happened-fix-139684

Don't access a mailbox with web access while Outlook has an open connection to that mailbox using the IMAP client protocol and you won't encounter this problem. If you do leave Outlook with IMAP access to a mailbox and access that mailbox from an alternate client, you might have some UID errors to accept when you get back to Outlook. The best solution might be to close Outlook if you're using IMAP and expect to access your mailbox with other clients.