On Sat, Jun 22, 2013 at 02:20:18PM -0400, [email protected] wrote: > Looking at the .mbsyncstate files showed they were all filled with Nulls. > this is typically what a file system like xfs would do after a crash.
> I have been using the git version of mbsync for a couple weeks (since > June 13). > hmpf. the above should not happen then - see the FSync option. anyway, there is no plausible way how mbsync itself could write a state file of all zeros (it's a text file written line wise). you should check your kernel log for anything unusual. > Is there any way to recover the .mbsyncstate files, short of > downloading everything from all the IMAP servers again? > nope. some nitpicks re your config: > CertificateFile ... > CertificateFile ... > CertificateFile ... > only the last instance is effective. > Inbox ~/path/to/Acct1/mail/Inbox > you don't actually need that, as you don't refer to INBOX (yes, all uppercase) anywhere: > Master :Acct1-imap:Inbox > the server will likely treat that as the INBOX ... > Slave :Acct1-local:Inbox > ... but mbsync won't. none of this actually matters, you just could streamline a bit. regards ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
