Benny, Thanks for the interesting explanation and details as regards encryption/signing of messages affecting Drafts in this way. Never considered that as a possibility in terms of sharing the contents of the Drafts folder. Other apps (notably Mail) don’t make that accommodation (nor make the extensive support for PGP or S/MIME signing and encryption that MM does). I would call their support minimal, possibly concerning as security content processing.
Respectfully, Henry Seiden - - Techworks Pro Co. E: info<at>techworkspro<dot>com W: http://techworkspro.com On 2 Apr 2025, at 9:14, Benny Kjær Nielsen wrote: > On 2 Apr 2025, at 13:50, Henry Seiden wrote: > >> So, I’m looking for confirmation that this is indeed occurring for all users >> and for your opinion (assuming you can replicate it) that you consider this >> either a bug or some undocumented feature. > > It's likely undocumented, but I think I wrote to you in an earlier email that > this is expected behavior when signing/encrypting is enabled in the composer > window. You can call it a bug if you like, but this is done to ensure that > sending a signed or encrypted email from A to B does not involve uploading > intermediate unfinished versions of the email. It might be a bit theoretical, > but one could imagine different scenarios for which this would be undesirable. > > I introduced this restriction when I realized that if encryption failed > (e.g., a missing certificate or something like that) then the email would be > uploaded unencrypted in its draft-state which was obviously bad. It was not > sufficient that MailMate would refuse to send it. In other cases, MailMate > could/should allow drafts to be uploaded (at least optionally). > > -- > Benny > _______________________________________________ > mailmate mailing list > Unsubscribe: https://lists.freron.com/listinfo/mailmate
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mailmate mailing list Unsubscribe: https://lists.freron.com/listinfo/mailmate
