I was not aware of that before, indeed.
I was confused, because either I missed it or there is no way to guess
Autocrypt is the cause of this "inconsistency". I respect that there is
a standard for that, and it is useful and nice that Enigmail supports it.
Would it be possible to show this rules
Autocrypt is a standard that allows to send your public key with every
message, along with a preference for how to deal with encryption. I.e.
the sender chooses how he/she prefers to get emails. In that particular
case the sender has specified to prefer unencrypted emails.
If you want to
Thanks Olav, Sebastian,
You two gave me a hint on the problem.
First, I did not realise that the debug log did not update itself in
live: I had to close the window and reopen it to get something meaningful.
Then, parsing the relevant log, it seems that there is a per-recipient
rule: an
On 2019-05-11 17:05, Rémi Saurel wrote:
> But there is this one address, which as soon as I add it to the
> recipient list, causes the following to happen:
> * Disabling auo signing of the my message
> * Do not enable encryption despite the corresponding public key being
> present in my keychain.
Hi,
I'm using Enigmail 2.0.10 with Thunderbird 60.6.1 on Linux, and I'm
having a weird issue.
I want all of my outgoing messages to be signed automatically, and when
I have the recipient(s) key(s) in my keychain, encrypted automatically
as well.
So far so good, this works with multiple email
