Benny,
Could it be an idea to store these unfinished encrypted emails in a
subfolder of the drafts “Drafts-encryted”? Or in an “Other
Drafts” folder.
At least that would “remind” the user that there is more to that
mail than a draft
Just my 5 cts
Marc
On 2 Apr 2025, at 15: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
_______________________________________________
mailmate mailing list
Unsubscribe: https://lists.freron.com/listinfo/mailmate
