-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06.01.15 15:23, Philip Jackson wrote: > On 06/01/15 13:07, Ian Mann wrote: >> I am going to stick with ver 1.8 because of the graphics in write mode. >> >> >> The fact that you can see the large padlock alerted me to the issue I was >> experiencing. >> > > I've been using "Running Enigmail version 1.8a1pre (20150102-0013)" since 2nd > Jan and my first reaction was to wonder where the sign and encrypt buttons had > gone to as I searched a vacant right hand side of the tool bar. > > Then I saw the new enigmail toolbar and I do think it's an improvement. > > I use "convenient encryption setting" and if I write 'TO' an address where I > have the public key of the person, the padlock is yellow and I see that the > message will be encrypted. > > As soon as I change the 'TO' to 'BCC' or 'Reply to' the padlock goes grey and > the message will not be encrypted. > > Changing to 'CC' gets yellow padlock and encrypted message status. > > Changing back to 'TO' or 'CC' gets encryption back - and this can be repeated > ad > infinitum. > > If it hadn't been for this thread, I'm not sure I would have noticed the > padlock > changing colour. > > Curiously, if I use two address lines, one for 'TO' or 'CC' and other for > 'BCC' > or 'Reply to' (both addresses for which I have public keys), the padlock stays > yellow. It doesn't matter in which order these two address lines are. > > There is another oddity : > > If I have one address line 'TO' with an address for which I have the key. the > padlock is yellow and the message will be encrypted. > > If I add a second line 'TO' or 'CC' with an address for which I do not have > the > public key, the padlock goes grey and the message will not be encrypted. > > But if I change the second 'TO' to 'BCC' or 'Reply to', the padlock goes > yellow > again and the text says the message will be encrypted. > > I didn't send any of the emails - I'm only commenting on visual behaviour > (display logic). It would look like the display logic needs re-examining.
Thanks for reporting! I can reproduce something similar. We will analyze it. Ludwig -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCgAGBQJUq/t5AAoJEA52XAUJWdLje2wIAK8PSXyYZ+jTLxGuFuUPIlvV cCUEsnuyc1CmnhkpbOaoZII0PRy+eFZ+BW9x5YxltOO/sbvQzQ/ZaWmFDB6wjnFW OCMN8PY3qo/CP8Ww7L7bqGt6I44Q/PqlEEwLrz5DdYLjQ5bl5nfnIl2UEn+bJMBu h8EOo92jOWyCynNQ62MCla4t5nLxHzIhdHESpTywoYcsANWqQIhR+ndoVofNzWV7 FybNWmtob+40fzNufpaNGFJuu9vKBg7zXFCCbUOmKQEEIyzJ3UUFVQIg5vPuuzQA inBVgUEbaMe38hP4JeFkoecafjXcIgeegVQXHD/3QCf9Wrajj91yZ4KtNigkBAM= =iS4o -----END PGP 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
