Re: [Enigmail] Thunderbird auto-encryption issues

Patrick Brunschwig <[email protected]>
Newsgroups gmane.comp.mozilla.enigmail.general
Message-ID <[email protected]>
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 (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEET5+J9VBawdGiYGMc2xGHud1faTsFAlzW/5kACgkQ2xGHud1f
aTtgThAAokMJQDc2nUO3rknXoDwPkLC5yVN+TDx4Ssbn3TOyxxg8sLck3cUXTd4L
5VOemJ5pBcPhukOyssezOl1UHCw0nZVuR0JLElLiAOeKqKsYGxHwL0VvbGTXnpmC
3Xq9Av6E/mzPrXV2fRwwB/r+Xw/lls1goqOCgYmwf74n7RJ5Tv3v9qVpMn6WYX6R
017klvlnh6MtWZC800ZS81FE2012fn1xT0Tbgnj8vCu83lIlEf+wlgG+OQp5qMYW
qjSP8n6mMVzpR8N6sIWW+yZhHxAPeWaOSc4SByfzVnudDekNboconmhj8uKrJfUn
Qrkg6BG3ZD5D8Q7NEHhxwklWa1rnDS2f9Pa59OxVx1hdUZfH3Bc1n5c4XKqpm1TV
OX1y06+gJBe6ZGUtjmD+v82c12al0AsB9BbKeJDddyDKVtk2fxTVja6GADxWEDWS
tYisI9qvrdhpgz6KWOVABGZzC0fVL9c9bmH9Zo4sEzzHVydkMfn50N15QK3krGov
fHILNsU1xeRJpx7GyFglZojLaeVtlY0i4xUE9vzyx7uQ44ZnXlSXnJBGsVNH+QB5
l6ONnMXU6ALhzr5OF8XbFeoqkZAFeMKxjBdkMqoToZ3uJExSqdLqs0e3I48Y/J9J
7pj4iM2R65gSktGb/bo23fCWXIfc3/6q6K8he8xKVYTf2PNTBb4=
=UBMC
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.