Re: [MlMt] Sign by default based on history not working
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 > error is not new). I don't have reports on this (I think), but I'll try to reproduce it by sending you a couple of messages off list. My own usage of signing/encryption is mostly explicit or related to debugging issues. -- Benny ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
[MlMt] Sign by default based on history not working
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 that same contact. 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 error is not new). Thank you Stephan ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 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"? 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.
Yes, that kind of flexibility would be nice.
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?
I'll note to see if I can add some kind of stopgap solution, but I'm
not promising anything.
--
Benny
https://freron.com/become_a_mailmate_patron/
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
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:
```
{
signingEnabledPattern =
"{always_si...@example.com,never_si...@example.com}";
signingDisabledPattern = "never_s...@example.com";
encryptionEnabledPattern = "*@example.org"; // Encrypt whenever
sending to someone with an example.org address.
encryptionDisabledPattern =
"{excepti...@example.org,excepti...@example.org}"; // Do no encrypt
for these addresses
}
```
In that first line, should "never_si...@example.com" actually be
"always_si...@example.com"? :-)
Thanks.
-Eric
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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"? 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. Yes, that kind of flexibility would be nice. 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? I'll note to see if I can add some kind of stopgap solution, but I'm not promising anything. -- Benny https://freron.com/become_a_mailmate_patron/ Benny, I just wanted to followup and thank you for the support you added to address this in r5632; it's working perfectly. -Eric ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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"? 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.
Yes, that kind of flexibility would be nice.
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?
I'll note to see if I can add some kind of stopgap solution, but I'm
not promising anything.
--
Benny
https://freron.com/become_a_mailmate_patron/
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
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:
```
{
signingEnabledPattern =
"{always_si...@example.com,never_si...@example.com}";
signingDisabledPattern = "never_s...@example.com";
encryptionEnabledPattern = "*@example.org"; // Encrypt whenever
sending to someone with an example.org address.
encryptionDisabledPattern =
"{excepti...@example.org,excepti...@example.org}"; // Do no encrypt for
these addresses
}
```
In that first line, should "never_si...@example.com" actually be
"always_si...@example.com"? :-)
Thanks.
-Eric
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 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. Yes, that kind of flexibility would be nice. 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? I'll note to see if I can add some kind of stopgap solution, but I'm not promising anything. -- Benny https://freron.com/become_a_mailmate_patron/ ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 for this. Hmm, basing the heuristic on a specific recipient seems more useful for the 'encrypt' setting (where I need to have their public key) than for the 'sign' setting. Why wouldn't I want to sign all my messages for an account where I have a signing cert? Which is what the “sign always” setting gives you in the Security preferences pane. Yes, but that's a global setting, which causes me all kinds of grief if I set it as I don't have email signing certs for all my accounts. But I'm not saying it couldn't be more flexible. 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. Yes, that kind of flexibility would be nice. 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? Thanks! -Eric ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 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 recipient seems more useful > for the 'encrypt' setting (where I need to have their public key) than > for the 'sign' setting. Why wouldn't I want to sign all my messages > for an account where I have a signing cert? Which is what the “sign always” setting gives you in the Security preferences pane. But I'm not saying it couldn't be more flexible. > 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. Yes, that kind of flexibility would be nice. -- Benny ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 recipient seems more useful for the 'encrypt' setting (where I need to have their public key) than for the 'sign' setting. Why wouldn't I want to sign all my messages for an account where I have a signing cert? Which is what the “sign always” setting gives you in the Security preferences pane. But I'm not saying it couldn't be more flexible. 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. Yes, that kind of flexibility would be nice. -- Benny ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 Sign by default to "Based on history", mails I compose on the two accounts with email signing certs would be signed and mail from others accounts would not. 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 recipient seems more useful for the 'encrypt' setting (where I need to have their public key) than for the 'sign' setting. Why wouldn't I want to sign all my messages for an account where I have a signing cert? Well, maybe the bug is that this is no longer updated when changing the recipient (after re-implementing the composer status bar). I'll note to check that. Now it seems to simply remember whether I signed the last message or not and repeat that, so as I switch accounts it's often making the wrong decision. And if I set it to "Always", it throws an error when I try to send from an account with no cert. I guess what I want is a "Based on existence of valid cert" setting. :-) Something like that could be implemented, but I would have to be careful. If there is some problem with a previously used certificate (or it disappeared) then MailMate shouldn't suddenly stop signing/encrypting. The same goes for any similar feature based on the existence of a certificate for the recipient. This doesn't mean that I don't think it should be more flexible. It's just not a quick fix to do it right. Welcome back. 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. Thanks. -Eric ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Sign by default Based on history not working?
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 compose on the two accounts with email signing certs would be signed and mail from others accounts would not. 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. Well, maybe the bug is that this is no longer updated when changing the recipient (after re-implementing the composer status bar). I'll note to check that. Now it seems to simply remember whether I signed the last message or not and repeat that, so as I switch accounts it's often making the wrong decision. And if I set it to "Always", it throws an error when I try to send from an account with no cert. I guess what I want is a "Based on existence of valid cert" setting. :-) Something like that could be implemented, but I would have to be careful. If there is some problem with a previously used certificate (or it disappeared) then MailMate shouldn't suddenly stop signing/encrypting. The same goes for any similar feature based on the existence of a certificate for the recipient. This doesn't mean that I don't think it should be more flexible. It's just not a quick fix to do it right. -- Benny https://freron.com/become_a_mailmate_patron/ ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
[MlMt] Sign by default Based on history not working?
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 certs would be signed and mail from others accounts would not. Now it seems to simply remember whether I signed the last message or not and repeat that, so as I switch accounts it's often making the wrong decision. And if I set it to "Always", it throws an error when I try to send from an account with no cert. I guess what I want is a "Based on existence of valid cert" setting. :-) -Eric ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
