On 2 Sep 2022, at 9:25, Stephan Kleiber via mailmate wrote:
> This does not work for me. I have the option activated, yet I always have to
> enable signing manually in the Composer window. Is there something I might be
> doing wrong or can anyone reproduce the issue? I’m on build 5914 (but the
Hi everyone,
in MailMate’s Preferences, there’s Security > Composer: OpenPGP > Sign by
default > Based on history. As I understand it, the setting should work in a
way that when I sign a message for a contact, MailMate should automatically
enable signing the next time I compose a message to
Hi Benny, it seems these "signingEnabledPattern & signingDisabledPattern
entries in my Security.plist file no longer work.
Like other recent issues I've been reporting, I can't tell you precisely
when things stopped working.
Thanks.
-Eric
On 10 May 2019, at 9:53, Eric Sharakan wrote:
On
On 1 May 2019, at 5:22, Benny Kjær Nielsen wrote:
On 12 Apr 2019, at 23:29, Eric Sharakan wrote:
On 16 Jan 2019, at 3:59, Benny Kjær Nielsen wrote:
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"?
On 10 May 2019, at 15:53, Eric Sharakan wrote:
In that first line, should "never_si...@example.com" actually be
"always_si...@example.com"? :-)
Yes, thanks for letting me know.
--
Benny
https://freron.com/become_a_mailmate_patron/
___
mailmate
On 1 May 2019, at 5:22, Benny Kjær Nielsen wrote:
On 12 Apr 2019, at 23:29, Eric Sharakan wrote:
On 16 Jan 2019, at 3:59, Benny Kjær Nielsen wrote:
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"?
On 12 Apr 2019, at 23:29, Eric Sharakan wrote:
On 16 Jan 2019, at 3:59, Benny Kjær Nielsen wrote:
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
On 16 Jan 2019, at 3:59, Benny Kjær Nielsen wrote:
On 11 Jan 2019, at 16:34, Eric Sharakan wrote:
On 11 Jan 2019, at 9:19, Benny Kjær Nielsen wrote:
I don't think I've changed anything. “Based on History” looks at
the latest email sent to the same recipient. There's currently no
fallback
One simple thing that would help in my situation is have the "sign always"
setting not throw an error if there's no signing cert for the account I'm
currently sending from.
Thanks.
-Eric
On Jan 16, 2019 at 03:59:23 EST, Benny Kjær Nielsen
wrote:
On 11 Jan 2019, at 16:34, Eric Sharakan
On 11 Jan 2019, at 16:34, Eric Sharakan wrote:
On 11 Jan 2019, at 9:19, Benny Kjær Nielsen wrote:
I don't think I've changed anything. “Based on History” looks at
the latest email sent to the same recipient. There's currently no
fallback for this.
Hmm, basing the heuristic on a specific
On 11 Jan 2019, at 9:19, Benny Kjær Nielsen wrote:
On 19 Dec 2018, at 6:17, Eric Sharakan wrote:
Running r5579, I'm finding MM is not making correct decisions on
whether to sign my emails or not. I have 5 accounts, two with S/MIME
signing certs and three without. It used to be that setting
On 19 Dec 2018, at 6:17, Eric Sharakan wrote:
Running r5579, I'm finding MM is not making correct decisions on
whether to sign my emails or not. I have 5 accounts, two with S/MIME
signing certs and three without. It used to be that setting Sign by
default to "Based on history", mails I
Running r5579, I'm finding MM is not making correct decisions on whether
to sign my emails or not. I have 5 accounts, two with S/MIME signing
certs and three without. It used to be that setting Sign by default to
"Based on history", mails I compose on the two accounts with email
signing
13 matches
Mail list logo
