Hi, I've used OfflineIMAP for some months, but I now intend to switch to mbsync¹ (the later let me avoid syncing email deleting from master to slave).
I would like to avoid downloading again GB of emails still in the remote repository. The most obvious way seem to convert the OfflineIMAP repository to a mbsync repository. And the first step is state files. ========= OfflineIMAP keeps them is a directory named after the "account". Then one file per directory, whose header is > OFFLINEIMAP LocalStatus CACHE DATA - DO NOT MODIFY - FORMAT 1 Sample: > 8203:FS > 8216:RS > 8125:S mostly: <increment>:<flags> Indexes are stored in a directory named like <source>/FolderValidity/<folder> which contains a long integer (folder UIDVALIDITY) Email files follow the pattern <timestamp>_<counter>.<PID>.<hostname>,U=<increment>,FMD5=<hash>:2,<flags> ========= mbsync keeps many files in .mbsync/ named as: <remote account>:<remote!folder>:<local account>:<local!folder> The first line contain somehow indexes/timestamp: > 631491624:7575 1368096631:0:0 followed by 3-columns lines, sample: > 72 10 RS > 81 14 S > 85 15 RS > 87 16 S > 169 31 S > 865 140 F mostly: <increment>:<unknown>:<flags> The .uidvalidity file stores the latest timestamp and id (even before the state file is full created) Email files follow the pattern: <timestamp>.<PID>_<counter>.<hostname>,U=<increment>:2,<flags> I guess email file naming isn't that important unrelated since none of the tools checks file existence before (re)downloading an email, but that's a guess. ========= what can be done Switching from OfflineIMAP .offlineimap/<local-repository>/FolderValidity/<folder> .offlineimap/<local-repository>/FolderValidity/<folder> to the two values inside mbsync's .uidvalidity file is trivial ========= what must probably be done What are the 2+3 values, in the header of mbsync's folder state file? And how OfflineIMAP's <repostory>/FolderValidity/<folder> could be converted/expanded to these 5 values? ========= other questions: - My goal being to continue, with mbsync, a synchronisation started for backup-purposes with OfflineIMAP, what part of the state could be omitted that mbsync could intelligently deduce? - What the 2nd column of the mbsync state file is useful for? - Why mbsync .uidvalidity file does not contain the value that OfflineIMAP calls folder UIDVALIDITY? - Any efforts to document (standardize?) these internal data/state files? thank you! ¹ explanation: offlineimap does not let me have an append/change-only local repository (email deleted remotely are forcefully deleted locally) ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
