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 in the per-recipient rules list maybe? Maybe only read-only as not to interfere with it, but it would materialize the cause of the behavior.
Thanks anyway for your insights, everybody! Rémi Le 11/05/2019 à 19:00, Patrick Brunschwig a écrit : > 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 overwrite the sender's preference, you'll need to create > a per-recipient rule for that email address. > > -Patrick > > > On 11.05.2019 18:55, Rémi Saurel wrote: >> 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 autocrypt:// one. This particular recipient must have enabled it. >> I went exploring the per-recipient rules before, but it was (and still >> is) empty. Thus i was clueless… >> >> I am not familiar with Autocrypt at all, I've read that it only starts >> encrypting after some sort of agreement/handshake between the 2 parties. >> I do not know how to complete the process with Enigmail :) >> >> One solution that would fit me well would be to know where these >> autocrypt:// rules are stored, and delete them. The party I try to >> communicate with is a pal of mine, and will be plenty satisfied by >> receiving encrypted/signed mail, and I do not like HIS settings >> impacting on mine. >> But perhaps I don't grasp the benefit of this Autocrypt thing? >> >> Thanks again, >> >> Rémi >> >> >> Le 11/05/2019 à 18:12, Sebastian a écrit : >>> 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. >>> Did you check the per recipient rules? >>> >> >> Le 11/05/2019 à 18:15, Olav Seyfarth a écrit : >>> Hi Rémi, >>> >>> you may want to provide a debug log - otherwise we can't see anything. :-) >>> >>> Make sure to close TB, restart it, compose the message in question, >>> enter the problematic address, check status is wrong, then save debug. >>> >>> Since that file does contain sensitive info, make sure to redact it first, >>> or send it to Patrick and me only. >>> >>> Olav >>> >> >> _______________________________________________ >> enigmail-users mailing list >> [email protected] >> To unsubscribe or make changes to your subscription click here: >> https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net >> > > > _______________________________________________ > enigmail-users mailing list > [email protected] > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
