Re: [Enigmail] BCC issues 1.7.2
Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian On 06/01/15 20:05, Ludwig Hügelschäfer wrote: Hi Ian, I'm afraid that there's a misunderstanding: On 06.01.15 08:52, Ian Mann wrote: I experienced BCC issues with 1.7.2 and searched the web and found this UK Register article. http://www.theregister.co.uk/2014/09/09/enigmail_encryption_error_prompts_plaintext_panic/ The article says: ! The dangerous hole in the Mozilla Thunderbird extension affected ! email that was sent only to blind carbon copy recipients on all ! versions below 1.7.2 released last month. ^^^ The BCC issue is solved with the 1.7.2 release. Subsequently I visited your web site and got the nightly 1.8a1 pre. You're invited to download and test our nightlies. However, there may always be bugs in the implementation of new features. I really like what you have done with the write message layout, its neat. I am also glad the BCC issue is corrected too, but the new layout was a pleasant surprise, thank you for all the work you do. You do a great job. You're welcome! Some of the graphic changes are the result of a usability study, so your thank goes to the authors of it! Ludwig ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. signature.asc Description: OpenPGP digital signature ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
On 06.01.2015 08:52, Ian Mann wrote: I experienced BCC issues with 1.7.2 and searched the web and found this UK Register article. http://www.theregister.co.uk/2014/09/09/enigmail_encryption_error_prompts_plaintext_panic/ Subsequently I visited your web site and got the nightly 1.8a1 pre. I thought the BCC problems were only in versions 1.7.2 ?! signature.asc Description: OpenPGP digital signature ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06.01.15 09:47, Alexander Buchner wrote: On 06.01.2015 08:52, Ian Mann wrote: I experienced BCC issues with 1.7.2 and searched the web and found this UK Register article. http://www.theregister.co.uk/2014/09/09/enigmail_encryption_error_prompts_plaintext_panic/ Subsequently I visited your web site and got the nightly 1.8a1 pre. I thought the BCC problems were only in versions 1.7.2 ?! Yes, that's right, and so I understand the article. Ludwig -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJUq6JfAAoJEA52XAUJWdLjYFEH/jQVMDfsISo2U91P7UtphbZF G0UiURbQeWfih2VVBfAGhXBjV/cF+a0msLIcNtfo1iv0dJwf9sZ1QEVy40097jsp mUae2A9lHBjKXyIDu4mGxY2BRIR0AY0Vh2bt9GTeuFf3rUW3mmPLQC3JcEXPu2k4 DOp3KsscTNaQBGY24R3TCCmMjMuEvH4fcJL6IvgWmTbL7hRfdzqPvAgI7XYwl6WE FrL7Q0xfQJDH/uNw5LH4BeNmadVvli3QGNVVswt6HbA9STmyM6g+ymrW7v0eZOSx yS2KTXNGxYuWo9P9PfmkJXrDWvYHitZeejEVQRPsnM6RMvE3MYRKaCoxz5Hak2A= =l8nz -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Ian, I'm afraid that there's a misunderstanding: On 06.01.15 08:52, Ian Mann wrote: I experienced BCC issues with 1.7.2 and searched the web and found this UK Register article. http://www.theregister.co.uk/2014/09/09/enigmail_encryption_error_prompts_plaintext_panic/ The article says: ! The dangerous hole in the Mozilla Thunderbird extension affected ! email that was sent only to blind carbon copy recipients on all ! versions below 1.7.2 released last month. ^^^ The BCC issue is solved with the 1.7.2 release. Subsequently I visited your web site and got the nightly 1.8a1 pre. You're invited to download and test our nightlies. However, there may always be bugs in the implementation of new features. I really like what you have done with the write message layout, its neat. I am also glad the BCC issue is corrected too, but the new layout was a pleasant surprise, thank you for all the work you do. You do a great job. You're welcome! Some of the graphic changes are the result of a usability study, so your thank goes to the authors of it! Ludwig -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJUq6VfAAoJEA52XAUJWdLjwf4H/3ewLUo/hLRWBLGTiUg01mE6 giYrA2brc3x6GHfVpORQw8VsMZEs1Ex+oXRB9HKY2+UwOa/hzb4Wnwdh4fJ2SdGs rANtM8y3kJL0b600rC0MW5M31/lgh+9mEOK/KH+yIlwsvFW2r+fGsfych79wKtIe et/d+bTnWBvIhinp2NLpyGtdyERUroi7ITcmQLbnK6K9WhCD6iy7x/DYoox0KiTo 9lhf9kgdUXYR/00PgEiVNKz/sPGi02JrPHS3NltaUNRKNnXTuwBhecJc+dWtTlLq hb2Dycha2eLgzqk/Brp5Uryum6t2gnRzzafQmgLrYQKyOFU0KTGEAYtwyNfTJd8= =bUFC -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
OK, rolled back to 1.7.2 TO: addressed back to my sending email BCC one of my other accounts BCC one of my other accounts Pressed SEND, got pop up warning on BCC, DID PRESS HIDE BCC Pressed NORMAL encryption, all went fine and received fine all encrypted. I have no idea now what I did incorrectly when I encountered the unencrypted BCC issue. Sorry to have posted ,misleading information. Ian On 06/01/15 21:35, Alexander Buchner wrote: On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
OK, rolled back to 1.7.2 TO: addressed back to my sending email BCC one of my other accounts BCC one of my other accounts Pressed SEND, got pop up warning on BCC, DID PRESS HIDE BCC Pressed NORMAL encryption, all went fine and received fine all encrypted. I have no idea now what I did incorrectly when I encountered the unencrypted BCC issue. Sorry to have posted ,misleading information. Ian On 06/01/15 21:35, Alexander Buchner wrote: On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
According to the article Enigmail only sent unencrypted when the message was sent *only* to BCC addresses, so to test properly you have to remove the TO to your own address. On Tue, Jan 6, 2015 at 11:53 AM, Ian Mann an...@neomailbox.ch wrote: OK, rolled back to 1.7.2 TO: addressed back to my sending email BCC one of my other accounts BCC one of my other accounts Pressed SEND, got pop up warning on BCC, DID PRESS HIDE BCC Pressed NORMAL encryption, all went fine and received fine all encrypted. I have no idea now what I did incorrectly when I encountered the unencrypted BCC issue. Sorry to have posted ,misleading information. Ian On 06/01/15 21:35, Alexander Buchner wrote: On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. ___ enigmail-users mailing listenigmail-us...@enigmail.net To unsubscribe or make changes to your subscription click here:https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
Correction OK, rolled back to 1.7.2 TO: addressed back to my sending email BCC one of my other accounts BCC one of my other accounts Pressed SEND, got pop up warning on BCC, _DID NOT PRESS HIDE BC_C ***Note: added NOT Pressed NORMAL encryption, all went fine and received fine all encrypted. I have no idea now what I did incorrectly when I encountered the unencrypted BCC issue. Sorry to have posted ,misleading information. Ian On 06/01/15 21:35, Alexander Buchner wrote: On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
Further, installed the nightly 1.8, no TO: Account used. BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, On 06/01/15 21:55, Onno Ekker wrote: According to the article Enigmail only sent unencrypted when the message was sent *only* to BCC addresses, so to test properly you have to remove the TO to your own address. On Tue, Jan 6, 2015 at 11:53 AM, Ian Mann an...@neomailbox.ch mailto:an...@neomailbox.ch wrote: OK, rolled back to 1.7.2 TO: addressed back to my sending email BCC one of my other accounts BCC one of my other accounts Pressed SEND, got pop up warning on BCC, DID PRESS HIDE BCC Pressed NORMAL encryption, all went fine and received fine all encrypted. I have no idea now what I did incorrectly when I encountered the unencrypted BCC issue. Sorry to have posted ,misleading information. Ian On 06/01/15 21:35, Alexander Buchner wrote: On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. ___ enigmail-users mailing list enigmail-users@enigmail.net mailto:enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net mailto:enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Ian, On 06.01.15 12:13, Ian Mann wrote: Further, installed the nightly 1.8, no TO: Account used. BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, I cannot reproduce this here using the nightly. Also, I get the BCC warning. This means that there is something wrong with - at least - your setup. Maybe there is still a bug. Let's explore this phenomenon. What are your settings? Is Convenient encryption enabled? Are there Per-Recipient rules for the BCC recipients? Would you please perform the test another time (after a restart of Thunderbird) and send us (ludwig at enigmail dot net and patrick at enigmail dot net) the debug log? Using the latest nightly, you don't need to set up logging, you always get a debug log (Enigmail - Debugging - View log, then press the save button). Thanks for helping! Ludwig -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJUq8ZMAAoJEA52XAUJWdLjoh8H/2cU5LJXAMzQVfRF2hXLBxN8 k/PKdJVBovYyoFGx01rQJlM81zQ/bXSUJi1TL8zJDoMm9SYktI/0qEltlboL2HWw Jz8Raq55Pk9joYBwz4arM/8X09XprRpSHjrS6SW8y7torn8R91gWLH2+YfHd/l/6 prFovP2U+JVhOkKsrVfSI/UuLJwd7yAsX5dPjAUJh5oFi8RPJK8XdqzipLR+Cv3c t7lkz2YdtghPWdHF95d99FALaKNdp0fBM4WHSG2qBUniHjskSL2WmQ6LEGgVWxfg hCewdmioP3H93XOIchidQFEpxAWv7Yd89fa9OAFoCOpkWOzQlG9i8k81VTSRieA= =aEjJ -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
Have tested 1.7.2 and 1.8 version the same way, they way you pointed out. Further, installed the nightly 1.8, no TO: Account used. and tested 1.7.2 the same method BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, If this really is a bug someone else should be able to get the same result. If I use a TO: filed, it all works fine and the BCC prompt happens. I have no idea how to lodge a bug report. Ian On 06/01/15 21:55, Onno Ekker wrote: According to the article Enigmail only sent unencrypted when the message was sent *only* to BCC addresses, so to test properly you have to remove the TO to your own address. On Tue, Jan 6, 2015 at 11:53 AM, Ian Mann an...@neomailbox.ch mailto:an...@neomailbox.ch wrote: OK, rolled back to 1.7.2 TO: addressed back to my sending email BCC one of my other accounts BCC one of my other accounts Pressed SEND, got pop up warning on BCC, DID PRESS HIDE BCC Pressed NORMAL encryption, all went fine and received fine all encrypted. I have no idea now what I did incorrectly when I encountered the unencrypted BCC issue. Sorry to have posted ,misleading information. Ian On 06/01/15 21:35, Alexander Buchner wrote: On 06.01.2015 10:29, Ian Mann wrote: Hmm, re reading I see your point, and should be less than version, 1.7.2 Hmm, I BCC'd and it seemed to encrypt but when I checked it was not encrypted, that is why I went looking on the web for an answer. I was sending to one of my other accounts as a test. I am kinda happy I have the nightly anyway with the improved Graphics. Thanks for pointing out my misunderstanding - Ian If there is still a bug with BCCs in 1.7.2 then I think the developers don't know about it yet. So please file a bug report! This kind of bug would qualify for a new release then I think. ___ enigmail-users mailing list enigmail-users@enigmail.net mailto:enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net mailto:enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
Probably so, it works if I use one TO: Filed, If all are BCC: I get that odd result where none are encrypted. Give me a minute to check the answers to the questions on set up you ask. Ian On 06/01/15 22:26, Ludwig Hügelschäfer wrote: Hi Ian, On 06.01.15 12:13, Ian Mann wrote: Further, installed the nightly 1.8, no TO: Account used. BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, I cannot reproduce this here using the nightly. Also, I get the BCC warning. This means that there is something wrong with - at least - your setup. Maybe there is still a bug. Let's explore this phenomenon. What are your settings? Is Convenient encryption enabled? Are there Per-Recipient rules for the BCC recipients? Would you please perform the test another time (after a restart of Thunderbird) and send us (ludwig at enigmail dot net and patrick at enigmail dot net) the debug log? Using the latest nightly, you don't need to set up logging, you always get a debug log (Enigmail - Debugging - View log, then press the save button). Thanks for helping! Ludwig ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
Manual encryption No BCC rules On 06/01/15 22:26, Ludwig Hügelschäfer wrote: Hi Ian, On 06.01.15 12:13, Ian Mann wrote: Further, installed the nightly 1.8, no TO: Account used. BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, I cannot reproduce this here using the nightly. Also, I get the BCC warning. This means that there is something wrong with - at least - your setup. Maybe there is still a bug. Let's explore this phenomenon. What are your settings? Is Convenient encryption enabled? Are there Per-Recipient rules for the BCC recipients? Would you please perform the test another time (after a restart of Thunderbird) and send us (ludwig at enigmail dot net and patrick at enigmail dot net) the debug log? Using the latest nightly, you don't need to set up logging, you always get a debug log (Enigmail - Debugging - View log, then press the save button). Thanks for helping! Ludwig ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
I can add something furtherfor version 1.8 I watched as I entered the accounts into the boxes, when I made them BCC the padlock dropped out. Encryption OFF. I went and re clicked the padlock and and it showed locked, or encrypted. This time when I pressed send I got a warning and all arrived encrypted. On 06/01/15 22:26, Ludwig Hügelschäfer wrote: Hi Ian, On 06.01.15 12:13, Ian Mann wrote: Further, installed the nightly 1.8, no TO: Account used. BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, I cannot reproduce this here using the nightly. Also, I get the BCC warning. This means that there is something wrong with - at least - your setup. Maybe there is still a bug. Let's explore this phenomenon. What are your settings? Is Convenient encryption enabled? Are there Per-Recipient rules for the BCC recipients? Would you please perform the test another time (after a restart of Thunderbird) and send us (ludwig at enigmail dot net and patrick at enigmail dot net) the debug log? Using the latest nightly, you don't need to set up logging, you always get a debug log (Enigmail - Debugging - View log, then press the save button). Thanks for helping! Ludwig ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
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. Ian On 06/01/15 22:26, Ludwig Hügelschäfer wrote: Hi Ian, On 06.01.15 12:13, Ian Mann wrote: Further, installed the nightly 1.8, no TO: Account used. BCC account 1 BCC account 2 BCC account 3 Pressed SEND, got no BCC warning, encrypted, all arrived unencrypted, I cannot reproduce this here using the nightly. Also, I get the BCC warning. This means that there is something wrong with - at least - your setup. Maybe there is still a bug. Let's explore this phenomenon. What are your settings? Is Convenient encryption enabled? Are there Per-Recipient rules for the BCC recipients? Would you please perform the test another time (after a restart of Thunderbird) and send us (ludwig at enigmail dot net and patrick at enigmail dot net) the debug log? Using the latest nightly, you don't need to set up logging, you always get a debug log (Enigmail - Debugging - View log, then press the save button). Thanks for helping! Ludwig ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
If I am understanding this issue correctly, a plausible real world scenario for bcc'ing encrypted recipients is one I ran into last week: I am working on a project that requires interaction with 3 different stakeholder teams. All use encrypted email, but do not interact with one another directly, and that is by design. It was a simple enough task to copy/paste the original message into new messages for the other teams. But it would have been convenient to be able to BCC the whole group at one time. I use myself as the To recipient. My personal preference is to see the same encryption behavior everywhere - where there are recipients w/o a key combined w/recipients that do have a key, warn that the message will be unencrypted. A prompt before send may be better than a status icon imho. On 1/6/2015 11:24 AM, Phil Stracchino wrote: On 01/06/15 11:23, Patrick Brunschwig wrote: If you think this should be changed, then you're invited to discuss this here. I never use BCC recipients in conjunction with encryption, so I can't really estimate how to proceed here. I tend to agree; I have a little difficulty imagining a plausible real-world scenario in which you would want to send Alice an encrypted message and bcc: Bob on it. ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06.01.15 19:23, Daniel Kahn Gillmor wrote: (...) I think the right thing to do is to treat Bcc: recipients the same as the To: or Cc: recipients, whether that's with convenient settings or per-address rules. I believe this is a closer match to most users' expectations of what should happen. ACK. And keeping it like the present implementation will produce user errors, user questions and documentation needs. This can be easily avoided. Ludwig -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJUrDQpAAoJEA52XAUJWdLjLhAIALoHiOOxF9jdxykovozT5Lz2 rVqPeTw9d2hGX8cfNzJdO66ZBmfQOO5QtXQNI5ifd2JMxyS/c07+1KIYxpRPDYKw ILkeOdM+I3QCxUPzBVi9rQcZgcVPioiOw7OgaV9H6m4+XsjN+vz/vbx0JohD/iot 8fN9psbX6K0U2UDhvkadcXY5KxRdZXj3PJddWHSmk/SwjboSbXG2SYp055I86jxL 4Th8mP+CfDazV1N3WGRhOQBw+Ff/NtJIET9im/d4lXBj5nwZDhDC3UniJZ4/1aQ3 INa06My12qZXIgl5Lg/kxUDs9DgYwsngjtA1F67i5R8H2TfS4qXNHeOraAkVwLI= =O4LY -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
On 06/01/15 20:14, Ludwig Hügelschäfer wrote: On 06.01.15 19:23, Daniel Kahn Gillmor wrote: (...) I think the right thing to do is to treat Bcc: recipients the same as the To: or Cc: recipients, whether that's with convenient settings or per-address rules. I believe this is a closer match to most users' expectations of what should happen. ACK. And keeping it like the present implementation will produce user errors, user questions and documentation needs. This can be easily avoided. I'd agree with this approach. I never have need of BCC's but there are lots of scenarios in business / politics where a user might wish to keep recipients unaware of each other's existence. At present, a user's 'careless' click when writing an email could cause him some embarrassment. Philip signature.asc Description: OpenPGP digital signature ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
I am going to make a point of not using BCC now. Some may have valid reasons for needing it. I just happened to key BCC by mistake initially and noticed the result. That is my two cents worth. Ian On 07/01/15 03:23, Patrick Brunschwig wrote: 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 agree. We're still working on improving the icons, but it's certainly a lot better now than before. 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. The point here is (I know, it's not well enough documented) that I decided to ignore per-recipient rules for BCC recipient; and we also decided to exclude BCC recipients from some of the logic for enabling/disabling encryption. Unfortunately I don't recall the reasons. If you think this should be changed, then you're invited to discuss this here. I never use BCC recipients in conjunction with encryption, so I can't really estimate how to proceed here. -Patrick ___ enigmail-users mailing list enigmail-users@enigmail.net 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 agree. We're still working on improving the icons, but it's certainly a lot better now than before. 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. The point here is (I know, it's not well enough documented) that I decided to ignore per-recipient rules for BCC recipient; and we also decided to exclude BCC recipients from some of the logic for enabling/disabling encryption. Unfortunately I don't recall the reasons. If you think this should be changed, then you're invited to discuss this here. I never use BCC recipients in conjunction with encryption, so I can't really estimate how to proceed here. - -Patrick -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJUrAv5AAoJEMk25cDiHiw+aDgH/ikR5s8Tihe5rBHBTH2zJCR8 6MHOGb575Sv26eKyTegSknali1fdfwR9aD/KAgccPc6mrQ+A/WJ6Eue8UUaggioK KMnYFzCCVvfK7HP74K8R0vb/dJkv4gco5ZK3B0UKah0++I6G15einzA/K2D323+c yoVwSef67bIgeEDGMddAfYbd6oBL48ZcTOBLyUBND1sNSPFyyMKbvNyanh2dM1Ng Oc1V1VN+0Rn2wrLvtRDBTip2afgdTViLrrR2Xx63/HOVVYCF9znzvR8VmBNYajzi d5Q1kGOGScZDYR3nFThQHI/m4MwdG/t9trJ6H8hPbhbuJLediD5wfEj+rf/sOts= =1jSt -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] BCC issues 1.7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/06/15 11:23, Patrick Brunschwig wrote: If you think this should be changed, then you're invited to discuss this here. I never use BCC recipients in conjunction with encryption, so I can't really estimate how to proceed here. I tend to agree; I have a little difficulty imagining a plausible real-world scenario in which you would want to send Alice an encrypted message and bcc: Bob on it. - -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: 603.293.8485 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEAREIAAYFAlSsGj4ACgkQ0DfOju+hMkk9aACg+D6ST0bqywP7KyJ15B5zeZhx eisAoPQrmt7+e7dCyIrNKVNP/XjXgLoi =+IzN -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
[Enigmail] BCC issues 1.7.2
I experienced BCC issues with 1.7.2 and searched the web and found this UK Register article. http://www.theregister.co.uk/2014/09/09/enigmail_encryption_error_prompts_plaintext_panic/ Subsequently I visited your web site and got the nightly 1.8a1 pre. I really like what you have done with the write message layout, its neat. I am also glad the BCC issue is corrected too, but the new layout was a pleasant surprise, thank you for all the work you do. You do a great job. Signed by Ian Mann *OpenPGP EMAIL ENCRYPTION* Request my Public Key if you encrypt email or retrieve it from the *MIT PGP Public Key Server* http://pgp.mit.edu/ *PGP is P*retty *G*ood *P*rivacy Windows Ubuntu https://whyencryptemail.net/ iPhone iPad https://ipgmail.com/ For Mac https://gpgtools.org/ signature.asc Description: OpenPGP digital signature ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
