On 21/08/2020 15:36, Jack wrote: > On 8/21/20 8:28 AM, Victor Ivanov wrote: > I seem to be slow on the pickup with parts of this thread, but I'm not > sure exactly what you are looking for here. I assume you did find how > Balsa handles encryption for sending and receiving mail. If you are > talking about encrypting the local storage of all or selected messages, > I agree it is not a current option.
Apologies, I kind of didn't want to fully hijack the thread. You're almost correct except that I'd like to encrypt the remote storage, not the local. Since IMAP works in both directions and allows for a full message, including headers, to be pushed to a given folder (handy for provider migration) one can use this feature to: (1) download a message in full (2) PGP encrypt the message according to RFC and a key of choice (3) push the encrypted message to the server (4) delete/expunge the previous, unencrypted message Both TB/Enigmail and KMail can use this technique to permanently decrypt a PGP encrypted message. The reverse, however, is a bit more clunky. KMail, has a working PGP encrypt filter but its message pushing is not always RFC compliant when it issues the IMAP "APPEND" command to push the message. It uses the current date/time instead of the one in the message's "Date" header which should take precedence according to RFC. This only appears to happen with multi-part messages, is easily reproducible even without PGP, and I have filed a bug report which has never been looked into. Plain-text messages are APPENDed correctly. The net result here is that as some providers, such as GMail, use the timestamp provided in the APPEND command to overwrite the message's Date header this leads to incorrect date/time indexing in folders/labels. So an old message now becomes recent when uploaded. KMail also fails to expunge the old message properly leaving the unencrypted message in addition to the newly pushed encrypted. TB/Enigmail too offers an "Encrypt to key" filter which ought to do the job but is completely broken and does not work at all. On the other hand pushing a message via IMAP works correctly for both plain-text and multi-part messages. The other mail clients that I have mentioned all have a correct APPEND implementation but do not seem to have an option (or filter choices) to perform the PGP procedure above. I'm hopeful that TB 78.2 will have this feature in one form or another. - V
signature.asc
Description: OpenPGP digital signature
