On Wed, Mar 21, 2018 at 10:13:58AM +, Seb Frank wrote:
> I again suddenly got this error:
> *Error: channel xxx, master yyy: UIDVALIDITY genuinely changed (at UID zzz).*
>
as it happens, i ran into this myself and pushed a fix. you can check
whether your problem had the same root cause (see co
I managed to solve this in the end by moving the message reported as
offending (with "Order received" in Thunderbird corresponding to the UID)
out of the way. After doing the same for two more UIDs which were
subsequently reported as having UIDvalidity changed, synchronization went
ahead, including
On Wed, Mar 21, 2018 at 10:13:58AM +, Seb Frank wrote:
>Hi,
>
>I again suddenly got this error:
>Error: channel xxx, master yyy: UIDVALIDITY genuinely changed (at UID
>zzz).
>
>see previous thread:
>
> [1]https://sourceforge.net/p/isync/mailman/isync-devel/thread/CAMF4
Hi,
I again suddenly got this error:
*Error: channel xxx, master yyy: UIDVALIDITY genuinely changed (at UID
zzz).*
see previous thread:
https://sourceforge.net/p/isync/mailman/isync-devel/thread/CAMF4YiPg6QAVBtkmjSjwRMyX1tXTQn1Q81h%3DUS%2BEZdDf_BhL5Q%40mail.gmail.com/#msg36070604
I checked .mbsy
