<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">Benny,</p>
<p dir="auto">Was able to delete the encryption and signing in PGP, which seems to have restored operation of v6241 in Drafts Folder>Send. Don’t know if it will affect the crashing issues.</p>
<p dir="auto">As to Drafts, it is still flaky and not shared to others even when no new Network Framework is enabled. Sorry to say, that is a no-go for my ever using Drafts folder.</p>
<p dir="auto">Can you tell me if there is a version of MM that supports a shared Drafts folder and how to fall back to that as previously requested? That folder appears to be tightly integrated to composing messages and it doesn’t seems that I can back down from using it when composing a new message. Hence when moving to a different device I lose my work.</p>
</div><div id="1995A5DB-20CE-42F9-8B2F-3BA5BB180511">
<div style="font-family: times; font-size: 125%; word-wrap:break-word;-webkit-nbsp-mode:space;line-break:after-white-space;">
Respectfully, <br />
Henry Seiden <br />
<! -- Email address option -- >
E: <a href= "mailto:inf@techworkspro.com"> Techworks Pro E-mail</a> <br />
W: <a href= "https://techworkspro.com"> Techworks Pro Co. Home Page</a>
<br /> <hr /> <br />
</div>
<div class="container" style="width:100%;margin-top:0px;margin-bottom:0px;margin-right:0px;margin-left:0px;border-width:1px;border-style:solid;border-color:gray;line-height:150%;background-color:lightblue;" >
<div class="header" style="padding-top:0.5em;padding-bottom:0.5em;padding-right:0.5em;padding-left:0.5em;color:white;background-color:gray;clear:left;" >
<h1 class="header" style="padding-top:0;padding-bottom:0;padding-right:0;padding-left:0;margin-top:0;margin-bottom:0;margin-right:0;margin-left:0;" >Techworks Pro Co.
</h1>
</div>
<div class="left" style="float:left;width:210px;margin-top:0;margin-bottom:0;margin-right:0;margin-left:0;padding-top:1em;padding-bottom:1em;padding-right:1em;padding-left:1em;" >
<p>Founder, Henry Seiden info@techworkspro.com
</p>
</div>
<div class="content" style="margin-left:230px;border-left-width:1px;border-left-style:solid;border-left-color:gray;padding-top:1em;padding-bottom:1em;padding-right:1em;padding-left:1em;overflow:hidden;" >
<img src="https://techworkspro.com/_includes/techworkspro_v3_200x53.png" width="300" alt="" />
</div>
<div class="footer" style="padding-top:0.5em;padding-bottom:0.5em;padding-right:0.5em;padding-left:0.5em;color:white;background-color:gray;clear:left;" >© 2024 techworkspro.com
</div>
</div></div>
<div class="markdown" style="white-space: normal;"><p dir="auto"><br>
On 2 Apr 2025, at 9:29, Henry Seiden wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">Benny,</p>
<p dir="auto">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.</p>
<p dir="auto">Respectfully,</p>
<p dir="auto">Henry Seiden</p>
<ul>
<li>
<ul>
<li></li>
</ul>
</li>
</ul>
<p dir="auto">Techworks Pro Co.<br>
E: info<at>techworkspro<dot>com<br>
W: <a href="http://techworkspro.com" style="color: #777777;">http://techworkspro.com</a></p>
<p dir="auto">On 2 Apr 2025, at 9:14, Benny Kjær Nielsen wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;">
<p dir="auto">On 2 Apr 2025, at 13:50, Henry Seiden wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #BBBBBB; color: #BBBBBB;">
<p dir="auto">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.</p>
</blockquote>
<p dir="auto">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.</p>
<p dir="auto">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).</p>
<p dir="auto">--<br>
Benny</p>
<hr style="border: 0; height: 1px; background: #333; background-image: linear-gradient(to right, #ccc, #333, #ccc);">
<p dir="auto">mailmate mailing list<br>
Unsubscribe: <a href="https://lists.freron.com/listinfo/mailmate" style="color: #999999;">https://lists.freron.com/listinfo/mailmate</a></p>
</blockquote>
<hr style="border: 0; height: 1px; background: #333; background-image: linear-gradient(to right, #ccc, #333, #ccc);">
<p dir="auto">mailmate mailing list<br>
Unsubscribe: <a href="https://lists.freron.com/listinfo/mailmate" style="color: #777777;">https://lists.freron.com/listinfo/mailmate</a></p>
</blockquote>
</div>
</div>
</body>
</html>