Hi Eric & Norman,
I did do the copy/restore using jpa -> maildir and back again.
After the restore, I also created a brand new account and was able to reproduce
the issue using it as well, so that appears to rule out any issues with the
mailboxcopier. I haven't narrowed this down to the smallest number of steps,
but I was able to recreate the issue by:
1) Sending 4 messages, one after the other.
2) Receive a new message.
As soon as the new message was received, Outlook 2010 started complaining. I
deleted the account from Outlook and redefined and the issue appeared
immediately, so Microsoft's suggested workaround didn't work. None of
Thunderbird, Roundcube, or Mac Mail have a problem, only Outlook.
Unfortunately Outlook is the primary client for the majority of our customers.
Thanks,
Pat
On 2011-06-29, at 2:31 AM, Eric Charles wrote:
> Hi Patrick,
> From previous thread, you were planning to copy/restore your mailbox.
> If you did that, then client uid/uidvalidity are no more in line.
>
> In thunderbird, it simply resynch the whole folder.
> Could it be oulook throws that message when uid/uidvalidy are no more in
> line? (that's what occurs when you copy/restore).
>
> Tks
>
> On 29/06/11 08:10, Norman Maurer wrote:
>> Hi Pat,
>>
>> did you saw this?:
>>
>> http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/4f2a9f05-365b-48a4-8557-63a8248fd108
>>
>>
>> Bye,
>> Norman
>>
>> Am 28.06.2011 18:04, schrieb Patrick Pyette:
>>> Hi,
>>>
>>> We've just upgraded one of our servers to the Beta 1 version of James
>>> and are seeing the following error when connecting with MS Outlook via
>>> IMAP. This account is also accessed without issue via IMAP using Mac
>>> Mail.
>>>
>>>
>>>
>>>
>>> If the image doesn't come through, it says "Your server has reported a
>>> UID which does not comply with the IMAP standard....." MsgSeqNum 7,
>>> New UID 1, Prev UID: 7, Next UID: 0.
>>> *
>>>
>>> Has this issue been identified as such and fixed? If not, it looks
>>> like a James issue, based on the message content, but perhaps is an MS
>>> implementation problem? Should I create a JIRA issue for it?
>>>
>>>
>>> Thanks,
>>> Pat
>>> *
>>>
>>>
>>>
>>>
>>
>>
>
> --
> Eric
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
