On Sat, Jul 28, 2018 at 08:44:25AM +0000, J. Tull wrote: > you still have not answered my question. Would my request require > porting offlineimap to python3, as you talked about it?
No. > If not would my > request require a lot of efforts? I can't say. I'm not sure what you have in mind. The best I can think of is the X-Offlineimap header trick that sounds the nearest to your purpose. You might like to start by studying this mechanism. This allows tracking the emails when UIDPLUS is not available (likely rare these days BTW). offlineimap is designed to rely on UID because that's what IMAP provides to work on the emails remotely. Working on any other parameter would require to request the remote servers with additional requests. I'm pretty sure there would be no other choice and this will strongly slow down the sync process. There's no object of "email" in the code. Basically, int values for the UIDs are passed everywhere (sometimes in tuples alongside other values like flags). This could be the most serious obstacle to get the things done because there might be a lot of code to update. Finally, syncing is not easy. This looks like easy but it's not. Even when working with UIDs. At some point in time we might realize the purpose is broken by design. This already happened in the past for a feature not relying on UIDS _1. Hope this helps. _1: http://www.offlineimap.org/devel/2015/04/14/why-we-changed-maxage.html -- Nicolas Sebrecht _______________________________________________ OfflineIMAP-project mailing list: OfflineIMAP-project@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/offlineimap-project OfflineIMAP homepages: - https://github.com/OfflineIMAP - http://offlineimap.org
