Oswald Buddenhagen <[email protected]> writes: > On Tue, Oct 21, 2014 at 04:07:15PM +0800, Eric Abrahamsen wrote: >> I set AuthMech to LOGIN, and mbsync connected, but then got a >> UIDVALIDITY error for each mailbox. >> > this is seriously weird. the UIDVALIDITY can only change due to some > server-side event. maybe it is somehow bound to the configuration, and > you changed something.
And I did. I changed the name of one of the local stores, forgetting that would invalidate the existing state files, and the new name somewhat miraculously coincided with the name of some old state files from a few years ago, and... anyway, it was a stupid mistake. >> I moved the ~/.mbsync directory to a different location and tried >> again, and it looks like it's going to resync each mailbox: >> > well, of course. > > in principle you can check whether the actual uids are still identical > (open the mailbox in thunderbird and enable the "arrival" column, match > these numbers against the state files in .mbsync/) and simply adjust the > state file if they match, but this is a somewhat risky business - if > (some) uids *did* change for some weird reason, you'll lose messages. Before I go pester someone else, my last question: For this example account, the AUTHENTICATE string should, as I understand it, be derivable like this: $ pas=$(echo -en "\[email protected]\0ThisIsMyPassword" | base64) If I telnet into my local dovecot server, and issue ", authenticate plain", together with the string from above, it logs in correctly. Does this explain anything, or explain nothing? Thanks, Eric ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
