<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto">Hi Benny, it seems these "signingEnabledPattern & signingDisabledPattern entries in my Security.plist file no longer work.</p>
<p dir="auto">Like other recent issues I've been reporting, I can't tell you precisely when things stopped working.</p>
<p dir="auto">Thanks.</p>
<p dir="auto">-Eric</p>
<p dir="auto">On 10 May 2019, at 9:53, Eric Sharakan wrote:</p>
</div>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div id="CB4465A9-28B9-420A-AA02-5207BD659DDF">
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 1 May 2019, at 5:22, Benny Kjær Nielsen wrote:</p>
</div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">On 12 Apr 2019, at 23:29, Eric Sharakan wrote:<br>
</p>
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><p dir="auto">On 16 Jan 2019, at 3:59, Benny Kjær Nielsen wrote:<br>
</p>
<blockquote style="border-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB"><blockquote style="border-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB"><p dir="auto">Perhaps another approach would be to make the sign settings be per account (or have an option under "Sign by default" of "Based on account"? I work in a company of over 100,000 employees, and I want mail I send on my work account to any of them to be signed. Conversely, I have no signing cert for my gmail account, so I never want MM to try to sign those messages.</p>
</blockquote><p dir="auto">Yes, that kind of flexibility would be nice.</p>
</blockquote><p dir="auto">I'm replying now because I just got bit by this inconsistency again. This to me is a bug, so I'm asking if you can please consider some kind of fix sooner rather than later?</p>
</blockquote><p dir="auto">I'll note to see if I can add some kind of stopgap solution, but I'm not promising anything.<br>
<br>
-- <br>
Benny<br>
<a href="https://freron.com/become_a_mailmate_patron/" style="color:#777">https://freron.com/become_a_mailmate_patron/</a><br>
_______________________________________________<br>
mailmate mailing list<br>
mailmate@lists.freron.com<br>
<a href="https://lists.freron.com/listinfo/mailmate" style="color:#777">https://lists.freron.com/listinfo/mailmate</a></p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">Hi Benny, I see you added something to address this in r5632, but I have a question about this documented syntax for the Security.plist file:<br>
<code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7"><br>
{<br>
signingEnabledPattern = "{always_sign1@example.com,never_sign1@example.com}";<br>
signingDisabledPattern = "never_sign@example.com";<br>
encryptionEnabledPattern = "*@example.org"; // Encrypt whenever sending to someone with an example.org address.<br>
encryptionDisabledPattern = "{exception1@example.org,exception2@example.org}"; // Do no encrypt for these addresses<br>
}<br>
</code><br>
In that first line, should "<a href="mailto:never_sign1@example.com" style="color:#3983C4">never_sign1@example.com</a>" actually be "<a href="mailto:always_sign2@example.com" style="color:#3983C4">always_sign2@example.com</a>"? :-)</p>
<p dir="auto">Thanks.</p>
<p dir="auto">-Eric</p>
</div>
</div></div></blockquote>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote></div>
</div>
</body>
</html>