J.J.

How about having the behavior you prefer as the default but adding an option so users can enable full extraction of tar.ext archives? I can appreciate that not extracting the tar is beneficial from a performance perspective; however, most people are ultimately after what's inside the tar archive. This is why I suggest having current behavior as default while providing an option for the alternative. Thanks

Wow. I'm a bit less adventurous than that, so I'm currently exploring gmvault for the interim. My object-oriented skills are pretty much non-existent, so I wouldn't be much help beyond possibly pseudocode. Thanks

Ability to log runtime errors and final result to file or syslog

OK. Thank you for considering a hashing solution. I will make do with what I can till then.

Just tried with a smaller mailbox and it looks like "SyncState *" is not appropriate for my use case. I'm syncing from Gmail to a local IMAP server. Based on the error message, "Error: store 'local-mychannel' does not support in-box sync state," I'm assuming that "SyncState *" is only meaningful if you're syncing to the filesystem.

No. I'll give it a try later on and see what happens. That user's mailbox is over 20 GB, so I'll give it a day or two so Google doesn't flip out.

Journal naming scheme leads to "File name too long" errors

Better yet, if the Explorer shell extension code hasn't changed, don't update it....