Dear Faisal, You should actually go and check that message in the maildir and maybe manually fix th UID. I think this might be a problem of the script you used to convert mboc to maildir. I am assuming you used mb2md.pl. I also did the same and had some slight problems, and ended up writing some 30 scripts before having a completely automated conversion. Good Luck! --- Alan Faisal Shaikh wrote:> Hi, > > I run a Postfix/Dovecot server with Outlook 2002, Thunderbird clients as > well as a Squirrelmail setup. All use IMAP to query the server. > > I recently converted our mail spool from mbox to maildir. After the > conversion, one of the users is receiving two types of error messages > which appear in a popup window. > > 1. The first popup says the following > > The UI D of a message changed unexpectedly. This typically indicates a > server bug. Your program may not function properly after this. > It then gives details of the MsgSeqNum, old UID and the new UID. > > 2. The second popup says > > Your server has reported a UID which does not comply with the IMAP > standard. This typically indicates a server bug. Your program may not > function properly after this. > > > Ive searched for this on google and it has been reported before, but > there are no reports of a solution or workaround. > > I would really appreciate any pointers or suggestions. > > Many Thanks, > Faisal Shaikh >
Hi, I run a Postfix/Dovecot server with Outlook 2002, Thunderbird clients as well as a Squirrelmail setup. All use IMAP to query the server. I recently converted our mail spool from mbox to maildir. After the conversion, one of the users is receiving two types of error messages which appear in a popup window. 1. The first popup says the following The UI D of a message changed unexpectedly. This typically indicates a server bug. Your program may not function properly after this. It then gives details of the MsgSeqNum, old UID and the new UID. 2. The second popup says Your server has reported a UID which does not comply with the IMAP standard. This typically indicates a server bug. Your program may not function properly after this. Ive searched for this on google and it has been reported before, but there are no reports of a solution or workaround. I would really appreciate any pointers or suggestions. Many Thanks, Faisal Shaikh
On Monday 14 Aug 2006 14:47, Faisal Shaikh wrote:> > Ive searched for this on google and it has been reported before, but > there are no reports of a solution or workaround. > > I would really appreciate any pointers or suggestions.One previous report was fixed by removing the index files on the server for that account, and clearing the cache in Outlook.
Thanks for the quick reply. Does clearing the cache on Outlook mean deleting the PST files ? Faisal
Sorry everyone, I was reading my original post and realised that I wasnt clear on the problem. The user that is getting the error pop-ups uses Outlook 2002. Faisal
Thanks! Clearing the index files on the server worked. Faisal Simon Waters wrote:>On Monday 14 Aug 2006 14:47, Faisal Shaikh wrote: > > >>Ive searched for this on google and it has been reported before, but >>there are no reports of a solution or workaround. >> >>I would really appreciate any pointers or suggestions. >> >> > >One previous report was fixed by removing the index files on the server for >that account, and clearing the cache in Outlook. > > >