From dkg at fifthhorseman.net Thu Oct 1 06:20:56 2009 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Thu, 01 Oct 2009 09:20:56 -0400 Subject: [Enigmail] enigmail should never sign drafts In-Reply-To: <4AC4470A.8080203@mozilla-enigmail.org> References: <4AC15651.8040006@fifthhorseman.net> <0McPxo-1MbN2f4ALY-00HifE@mrelayeu.kundenserver.de> <4AC37659.6060701@mozilla-enigmail.org> <4AC38477.7080808@fifthhorseman.net> <4AC3A250.1010803@sixdemonbag.org> <4AC3A99A.8060104@fifthhorseman.net> <4AC3C751.9010607@sixdemonbag.org> <4AC3D9FE.80909@fifthhorseman.net> <4AC3E5D9.3030908@sixdemonbag.org> <4AC404A0.6080401@fifthhorseman.net> <4AC4470A.8080203@mozilla-enigmail.org> Message-ID: <4AC4ACB8.3070708@fifthhorseman.net> Thanks for the kind words, Olav. On 10/01/2009 02:07 AM, Olav Seyfarth wrote: > Apart from that I think that at least the part "using a product (or issuing > a signature) by itself doesn't make anything safe" must be pointed out from > time to time. Indeed. And to bring it back to Enigmail, this is exactly why i think it's great that Patrick is looking into getting Enigmail to stop signing drafts. Robert listed a number of good reasons why one might decide that a particular signature or class of signatures was effectively meaningless; among those, i might add: * signature issuer is known to use a tool which issues signatures on their behalf at unintended times. It would be unfortunate if use of Enigmail was considered to make other signatures by the same issuer suspect. To make it personal: it would be sad for me, because my OpenPGP signatures are relied upon by colleagues in a number of projects, and i make no secret of my use of Enigmail. --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 891 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Thu Oct 1 06:26:50 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Thu, 01 Oct 2009 09:26:50 -0400 Subject: [Enigmail] enigmail should never sign drafts In-Reply-To: <4AC4470A.8080203@mozilla-enigmail.org> References: <4AC15651.8040006@fifthhorseman.net> <0McPxo-1MbN2f4ALY-00HifE@mrelayeu.kundenserver.de> <4AC37659.6060701@mozilla-enigmail.org> <4AC38477.7080808@fifthhorseman.net> <4AC3A250.1010803@sixdemonbag.org> <4AC3A99A.8060104@fifthhorseman.net> <4AC3C751.9010607@sixdemonbag.org> <4AC3D9FE.80909@fifthhorseman.net> <4AC3E5D9.3030908@sixdemonbag.org> <4AC404A0.6080401@fifthhorseman.net> <4AC4470A.8080203@mozilla-enigmail.org> Message-ID: <4AC4AE1A.2050604@sixdemonbag.org> Olav Seyfarth wrote: > Never mind, I liked to sit back, relax and see both of you arguing. > But yes, Robert could have flagged it OT ;-) I personally thought it was on-topic. Too often we fool ourselves into thinking that we know how people need to use our software, when the real world often has use-cases we haven't considered. Likewise, we fool ourselves into thinking signatures are some kind of magic pixie dust. I think those two points are both relevant to Enigmail. With respect to the question, "should Enigmail allow you to sign drafts before saving them?", I'm ambivalent. So far the argument against is, "but I don't see any use for it!" I don't find this logic persuasive, for reasons already mentioned. The other argument is, "it's not needed and only makes things more complex." This is only a little bit better: none of us know whether it's needed or unneeded or how many users need it. We wouldn't find that out until we removed the option and started getting "why did you remove it?" questions. So the first part of the argument, "it's not needed," is really our prejudice: it's something we believe in the absence of facts. The other bit, how it makes the interface more complex ... okay, that I'll agree with: it adds a small bit of complexity. So, on the one hand, signing adds a small bit of complexity to the user interface. Fine. Let's add it to the list of low-hanging fruit. File an RFE for it on Bugzilla and we'll see about it. The idea might be worth implementing. From rjh at sixdemonbag.org Thu Oct 1 06:42:04 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Thu, 01 Oct 2009 09:42:04 -0400 Subject: [Enigmail] enigmail should never sign drafts In-Reply-To: <4AC4ACB8.3070708@fifthhorseman.net> References: <4AC15651.8040006@fifthhorseman.net> <0McPxo-1MbN2f4ALY-00HifE@mrelayeu.kundenserver.de> <4AC37659.6060701@mozilla-enigmail.org> <4AC38477.7080808@fifthhorseman.net> <4AC3A250.1010803@sixdemonbag.org> <4AC3A99A.8060104@fifthhorseman.net> <4AC3C751.9010607@sixdemonbag.org> <4AC3D9FE.80909@fifthhorseman.net> <4AC3E5D9.3030908@sixdemonbag.org> <4AC404A0.6080401@fifthhorseman.net> <4AC4470A.8080203@mozilla-enigmail.org> <4AC4ACB8.3070708@fifthhorseman.net> Message-ID: <4AC4B1AC.10900@sixdemonbag.org> Daniel Kahn Gillmor wrote: > Robert listed a number of good reasons why one might decide that a > particular signature or class of signatures was effectively meaningless; > among those, i might add: > > * signature issuer is known to use a tool which issues signatures on > their behalf at unintended times. By the same logic, once you configure PGP Corporation's email proxy to automatically sign all outgoing email, if you get botted and your desktop sends out spams, your spams will be PGP-signed. (Yes, this has been observed in-the-wild.) Does that mean PGP Corporation's email proxy is suspect? Of course not. So long as users are clearly told under what conditions signatures will be made, you can't claim the tool issues signatures at unintended times. This dog won't hunt. From shavital at mac.com Sat Oct 3 11:07:23 2009 From: shavital at mac.com (Charly Avital) Date: Sat, 03 Oct 2009 14:07:23 -0400 Subject: [Enigmail] Reporting: TB3+Enigmail In-Reply-To: <4ABA6608.5020505@hammernoch.net> References: <4ABA4D84.5040402@mac.com> <4ABA6608.5020505@hammernoch.net> Message-ID: <4AC792DB.6020201@mac.com> Hi, Running Enigmail version 0.97a (20091003-1243), MacOSX 1.6.1, MacGnuPG2 2.0.12, with gpg-agent. Decryption is instantaneous: click the Decrypt button, Pinentry-Mac pops-up, type passphrase/Enter, message is decrypted immediately. No need to reenter the passphrase as long as gpg-agent's cache in gpg-agent.conf is active. Verifying signed messages, either MIME or in-line, is "laborious", requiring two attempts, whether clicking the Decrypt button, or choosing from Menu OpenPGP>Decrypt/Verify. Signature is verified eventually, and when signer's key contains a photo file, photo is displayed twice. The above does not depend upon having to download the signers' public key, which I know have been in my public keyring for a long time. Tested also with previous nightly (September 29), same behavior. Not crucial, just annoying. TB 3.0b4 still buggy, but that's not Enigmail's purview. Thank you for your work with Enigmail. Charly From patrick at mozilla-enigmail.org Sun Oct 4 02:14:42 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Sun, 04 Oct 2009 11:14:42 +0200 Subject: [Enigmail] Reporting: TB3+Enigmail In-Reply-To: <4AC792DB.6020201@mac.com> References: <4ABA4D84.5040402@mac.com> <4ABA6608.5020505@hammernoch.net> <4AC792DB.6020201@mac.com> Message-ID: <4AC86782.2090505@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Charly Avital wrote: > Hi, > > Running Enigmail version 0.97a (20091003-1243), MacOSX 1.6.1, MacGnuPG2 > 2.0.12, with gpg-agent. > > Decryption is instantaneous: click the Decrypt button, Pinentry-Mac > pops-up, type passphrase/Enter, message is decrypted immediately. > No need to reenter the passphrase as long as gpg-agent's cache in > gpg-agent.conf is active. > > Verifying signed messages, either MIME or in-line, is "laborious", > requiring two attempts, whether clicking the Decrypt button, or choosing > from Menu OpenPGP>Decrypt/Verify. Signature is verified eventually, and > when signer's key contains a photo file, photo is displayed twice. > > The above does not depend upon having to download the signers' public > key, which I know have been in my public keyring for a long time. > > Tested also with previous nightly (September 29), same behavior. > > Not crucial, just annoying. This has nothing to do with the version of Thunderbird, but with the messages you are verifying. I added several heuristics that allow to verify most inline-PGP messages, but this means that depending on how a message is encoded (e.g. quoted-printable inline-PGP mail), Enigmail may need up to 4(!) attempts to verify a message. And this is exactly what you see. The only recommendation I have is to switch to PGP/MIME. Encrypted inline-PGP messages usually do not suffer from this problem because they are simple 7-bit ASCII messages. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSshngHcOpHodsOiwAQhUGQf/bSb2l6ZAreYle2qEEzFJT7qS7TTcSvKR ABH9dQxMFKKrk5w6/Xxq5nj0etn6judbfdOvTsKPPYmTH0IVOw2qmp4y3PQkHosk w8CQ4ctiZ479SaFmYfAQ/1Efy0nuEHfqpnJ9NBGu9NKOwOYClp+RVyb+7lI00V7m aJY3DZHpPp37PExGPexU0ZdrNgXwz+3taKMRk/tiBso/n1OFHCvm1/1laUjUCJlj vxUaG0phw3X8RY9pO27yY9pdeh2HFsjYD42NFispnfqwJ6wH8ryGk0OTv34/mjPL 0SmnS3hpekqfZw1SmWxoEjd5FxWrcXM0iT63mEyd8H7WesbixJNHmA== =iOtG -----END PGP SIGNATURE----- From adminsmstsp2001 at gmail.com Tue Oct 6 04:16:02 2009 From: adminsmstsp2001 at gmail.com (Admin System) Date: Tue, 06 Oct 2009 19:16:02 +0800 Subject: [Enigmail] question error sending signed message Message-ID: <4ACB26F2.8060809@gmail.com> I followed Chapter 3 Hello World's guide from http://enigmail.mozdev.org/documentation/quickstart-ch3.php page without missing any important detail , yes , sent to the robot adele-en at gnupp.de and then an IMAP gmail account , still receive the same set of errors: Thunderbird 2.0.0.23 -Alert pop-up box shows : " An error occured while sending mail. The mail server responded : 5.7.1 Authentication required : recipientname at gmail.com. Please check the message recipients and try again. " then it followed with :"Sending Message Error" titled pop-up box Sending of message failed. Please verify that your Mail & Newsgroups account settings are correct and try again. OpenPGP options selected : -Attach My Public Key -Sign Message email message options -plain text -gmail IMAP TLS/SSL Because of this I can never proceed to the step of "Encrypting message". Please help . Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xCC17C3B0.asc Type: application/pgp-keys Size: 1741 bytes Desc: not available URL: From olav at mozilla-enigmail.org Tue Oct 6 06:02:27 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Tue, 06 Oct 2009 15:02:27 +0200 Subject: [Enigmail] question error sending signed message In-Reply-To: <4ACB26F2.8060809@gmail.com> References: <4ACB26F2.8060809@gmail.com> Message-ID: <4ACB3FE3.5070106@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi anonymous enigmail user, > I sent to adele-en at gnupp.de so you could send to and got a response from the robot? > I send to an IMAP gmail account but always get mail server response > 5.7.1 Authentication required: recipientname at gmail.com. > Please check the message recipients and try again. This points to an SMTP settings error and has got nothing to do with Enigmail. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Diese Email ist digital signiert und/oder verschl?sselt Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkrLP+IACgkQL/NBt8fdKe2h5ACfZ0aEAPHLBFYMm166vGIjaAxI lhoAn1Xg/3ithwZv0JEpP/PCgsWKgNaE =ClHH -----END PGP SIGNATURE----- From jeandavid8 at verizon.net Tue Oct 6 06:13:43 2009 From: jeandavid8 at verizon.net (Jean-David Beyer) Date: Tue, 06 Oct 2009 09:13:43 -0400 Subject: [Enigmail] question error sending signed message In-Reply-To: <4ACB3FE3.5070106@mozilla-enigmail.org> References: <4ACB26F2.8060809@gmail.com> <4ACB3FE3.5070106@mozilla-enigmail.org> Message-ID: <4ACB4287.70409@verizon.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Olav Seyfarth wrote: | Hi anonymous enigmail user, | |> I sent to adele-en at gnupp.de | | so you could send to and got a response from the robot? | |> I send to an IMAP gmail account but always get mail server response |> 5.7.1 Authentication required: recipientname at gmail.com. |> Please check the message recipients and try again. | | This points to an SMTP settings error and has got nothing to do with | Enigmail. | It may not be your SMTP settings if your ISP is like mine (Verizon). They often have problems with their server and I cannot login to it. Sometimes waiting a day fixes the problem, but sometimes I must reset my password to what it already was. As if they just got an error in their database where passwords are kept. - -- ~ .~. Jean-David Beyer Registered Linux User 85642. ~ /V\ PGP-Key: 9A2FC99A Registered Machine 241939. ~ /( )\ Shrewsbury, New Jersey http://counter.li.org ~ ^^-^^ 09:10:01 up 5 days, 18:09, 3 users, load average: 4.29, 4.13, 4.18 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org/ iD8DBQFKy0KGPtu2XpovyZoRAg90AKDOJ8kUod0ECYipx03KEHOs9JkT1wCfbZLT Y/fbx4Kp0+mMrrANTEX/iVA= =Rcx4 -----END PGP SIGNATURE----- From jalockli at uwaterloo.ca Tue Oct 6 06:32:10 2009 From: jalockli at uwaterloo.ca (Jason Locklin) Date: Tue, 06 Oct 2009 09:32:10 -0400 Subject: [Enigmail] enigmail should never sign drafts In-Reply-To: <4AC38477.7080808@fifthhorseman.net> References: <4AC15651.8040006@fifthhorseman.net> <0McPxo-1MbN2f4ALY-00HifE@mrelayeu.kundenserver.de> <4AC37659.6060701@mozilla-enigmail.org> <4AC38477.7080808@fifthhorseman.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel Kahn Gillmor wrote: > On 09/30/2009 11:16 AM, Patrick Brunschwig wrote: >> Enigmail only automatically signs drafts if you once instructed Enigmail >> to do so. When auto-saving, there is a question asking if the draft >> should be encrypted with a checkbox "Do not ask again". If you clicked >> "yes" and activated that checkbox, then the obvious happens: Enigmail >> will encrypt any future drafts. > > but encryption is not signing. I *want* enigmail to encrypt my drafts. > I *do not want* enigmail to ever attempt to *sign* my drafts. > > I can't see why anyone would want to sign their drafts, for that matter. > I don't see a problem with signing drafts if they are only encrypted to self. Then there is no chance of people reading incomplete, but accidentally distributed emails. At the same time, the user can verify that the email hasn't been altered somehow. It just seems like good practice to always sign what's encrypted. >> To reset any warnings, go to OpenPGP > Preferences, click on "Display >> expert settings"; then switch to the "Advanced" tab and click on "Reset >> Warnings". > > Will this let me distinguish between signing and encryption of drafts? > > --dkg > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: 'http://artsweb.uwaterloo.ca/~jalockli' Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrLRtMACgkQb2BKgf4F4OjEuQCfaltSINcUFZgvgZSqB/cXVB96 B5YAnjZuQiaxeaKNToyQcBWh+F6Y2jI8 =f6ML -----END PGP SIGNATURE----- From dkg at fifthhorseman.net Tue Oct 6 11:43:26 2009 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Tue, 06 Oct 2009 14:43:26 -0400 Subject: [Enigmail] enigmail should never sign drafts In-Reply-To: References: <4AC15651.8040006@fifthhorseman.net> <0McPxo-1MbN2f4ALY-00HifE@mrelayeu.kundenserver.de> <4AC37659.6060701@mozilla-enigmail.org> <4AC38477.7080808@fifthhorseman.net> Message-ID: <4ACB8FCE.9050206@fifthhorseman.net> On 10/06/2009 09:32 AM, Jason Locklin wrote: > I don't see a problem with signing drafts if they are only encrypted to > self. Then there is no chance of people reading incomplete, but > accidentally distributed emails. At the same time, the user can verify > that the email hasn't been altered somehow. It just seems like good > practice to always sign what's encrypted. I agree with you that if the draft is always encrypted-only-to-self, then the risk of the extra signature itself isn't as great. (though there are cases where it might still be bad, such as when your "self-encrypt" target belongs to the company e-mail archiver). But signing does create a workflow hiccup (the user must enter their GPG passphrase) during draft save time. Since drafts are auto-saved, this interruption can be surprising and potentially annoying. For a user who explicitly wants this behavior, this might be an acceptable tradeoff. For users who don't want this behavior (e.g. folks who don't like their signature affixed to an incomplete document), it's counterproductive. Do you verify the signature of your draft before resuming editing? If so, what do you do when the signature isn't present or is malformed? --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 891 bytes Desc: OpenPGP digital signature URL: From sgd-enigmail at lugaru.com Wed Oct 7 15:24:27 2009 From: sgd-enigmail at lugaru.com (Steven Doerfler) Date: Wed, 07 Oct 2009 18:24:27 -0400 Subject: [Enigmail] Turn off masking of passphrase prompt Message-ID: <4ACD151B.4050904@lugaru.com> In my environment there's no one who can look over my shoulder, so the asterisks displayed when I type my passphrase aren't useful. And I frequently have to retype my passphrase, or type it very slowly, to get it right. For me, enigmail would be much easier to use if I could set it to display my passphrase as I type it. Is there any way to configure this? I tried editing userChrome.css and defining a new style for #password1Textbox, but nothing I tried had any effect. Thanks for any help. Steven From patrick at mozilla-enigmail.org Thu Oct 8 23:54:40 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 09 Oct 2009 08:54:40 +0200 Subject: [Enigmail] Turn off masking of passphrase prompt In-Reply-To: <4ACD151B.4050904@lugaru.com> References: <4ACD151B.4050904@lugaru.com> Message-ID: <4ACEDE30.6030703@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Steven Doerfler wrote: > In my environment there's no one who can look over my shoulder, so the > asterisks displayed when I type my passphrase aren't useful. And I > frequently have to retype my passphrase, or type it very slowly, to get > it right. > > For me, enigmail would be much easier to use if I could set it to > display my passphrase as I type it. Is there any way to configure > this? I tried editing userChrome.css and defining a new style for > #password1Textbox, but nothing I tried had any effect. > > Thanks for any help. Enigmail uses the normal promptPassword method provided by nsIPromptService (i.e. a standard Mozilla component that is also used in Thunderbird and Firefox). There are some add-ons that handle this; I'd recommend you search e.g. for "password" on addons.mozilla.org. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSs7eLncOpHodsOiwAQi7tgf/VRE2FIrNUQNPY6ZK0KgiidgR1zqbkl54 iACpcwYgIVo0miOGiOE0JdcC25tAmE/6T2+gQR34e5I55EIKmZJWItNXkA2XurQy MKDMGLvhLj3GCHJlOvDSgLs/1mwEEec0IRd6tc2hpLr1MKvdLWunsW+mbAMJ1CCH zi7wAehbveDQvjtwXXMWEYkwFb7BQIeMsf6V9TrGQV3+WZQnMJQiyiPSvgdKvM2P 56Fy5kpgVyGqJOYfPbwIu75maH5ZsVNverIZ6GUy/VgiGXeM+xK+7kGy2bJlmHD2 TJH8Y0OPz4/Es7z/yOMSQR0L4gGgKCvRLDn5k+XK6Mhs8KV5JMhEnA== =TXF3 -----END PGP SIGNATURE----- From atlanx at gmx.de Sun Oct 11 08:59:04 2009 From: atlanx at gmx.de (Markur) Date: Sun, 11 Oct 2009 17:59:04 +0200 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? Message-ID: Hello, will enigmail work on Seamonkey 2.0 Final? Thank you. From jmoore3rd at bellsouth.net Sun Oct 11 09:12:36 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Sun, 11 Oct 2009 12:12:36 -0400 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: <4AD203F4.9050701@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Markur wrote: > will enigmail work on Seamonkey 2.0 Final? The Nightly Build should. http://enigmail.mozdev.org/download/nightly.php JOHN ;) Timestamp: Sunday 11 Oct 2009, 12:12 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJK0gPzAAoJEBCGy9eAtCsPG9oH/0Gyl596xAPoC0HHqrvmy5RE 1n6s1fNMgiIJv4a0sTvbs0XRyE57hxCOKVXThDqU1TrlR6Wx35aA5UhmoPl79/EM 5Sq4mR7pl57ZAVa2b7HiQSMcrwrlv/DhlYxVBTfYV4IpnY+xZ9ZZFfBMRRllwH+k +3XIyx/UrtzuBBTylfZqtWV2Ahl7gCQ0Thgm3MxLaoGgOqfoWSVbSzDctCBqapa8 UaRshD7hquqW66AqqLupR0PgV+AoWeYXoGPuzAxW+jE2txOWpFJRj2d5GLwLq+jT 0HWBxRJu7VlENtWCEajlWp+WMy1FauhM+Z5g0G/w+7pjDtiSYUHvKGV7ioBM8v0= =Bby6 -----END PGP SIGNATURE----- From rjh at sixdemonbag.org Sun Oct 11 09:27:18 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sun, 11 Oct 2009 12:27:18 -0400 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: <4AD20766.1000900@sixdemonbag.org> Markur wrote: > will enigmail work on Seamonkey 2.0 Final? Yes. When Seamonkey 2.0 is officially released, Enigmail will support it. Maybe not immediately, but soon. The latest Enigmail nightly builds support the Seamonkey 2.0 release candidates; assuming Seamonkey doesn't change very much between now and release, Enigmail will work with it pretty much right out of the box. This message was composed in Seamonkey 2.0 RC1, using the latest Enigmail nightly. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 187 bytes Desc: OpenPGP digital signature URL: From patrick at mozilla-enigmail.org Sun Oct 11 10:24:19 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Sun, 11 Oct 2009 19:24:19 +0200 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: <4AD214C3.4050002@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Markur wrote: > Hello, > > will enigmail work on Seamonkey 2.0 Final? Yes, I will release Enigmail v0.97.0 around the time of the Seamonkey 2.0 release. This is _very_ likely before Thunderbird 3.0 will be out; I hope that the same release will also work on TB3 (but that's to be seen). - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBStIUwXcOpHodsOiwAQj3UQf+I2d+zkalVqjjNREDd0INLl3XFhL8/WQH TZsV6ti+zhc7TDE+kEsMOwg+0medmOZhlnpT8S5YWTMRWe5819qmpRtp/BTwNKey FWT4Wwl9BJUT5OLhyD4+2aZq/pD++mX1ZeotyIFGM6piWrn70m4o59dPDn12tR18 dR7MhfYgsInS9iMgg8a9IBIU6RCoFEaSzvTcY0770UbDdVItsqcU0zs/bnqRCbAx OJ1j6JWKG3+VcB2PMd3PDSTez9l8QBN774d5Yl/d4mM3vRGRuctcDRp4qg+FXOxN 7xHY7fxwbQcKNuNaBL/fPWa9vZQUk+T09vIAxSgW8Jp5uzNOM6ucHA== =KZNU -----END PGP SIGNATURE----- From 71oesav71 at estreet.com Sun Oct 11 19:21:27 2009 From: 71oesav71 at estreet.com (richard c savage) Date: Sun, 11 Oct 2009 20:21:27 -0600 Subject: [Enigmail] ???????????????????????? Message-ID: <4AD292A7.4050201@estreet.com> What IS this???? It just came up on my newly-installed SUSE screen. Why should I care???? From hrickards at oftle.com Mon Oct 12 11:45:37 2009 From: hrickards at oftle.com (Harry Rickards) Date: Mon, 12 Oct 2009 19:45:37 +0100 Subject: [Enigmail] ???????????????????????? In-Reply-To: <4AD292A7.4050201@estreet.com> References: <4AD292A7.4050201@estreet.com> Message-ID: <4AD37951.8080803@oftle.com> richard c savage wrote: > What IS this???? > > It just came up on my newly-installed SUSE screen. > > Why should I care???? Do you know (and understand) what GPG, PGP or any public-key crypto is? -- Harry Rickards - hrickards at oftle.com Debian Lenny server | Debian Sid desktop | UNR Karmic netbook A good programmer is someone who looks both ways before crossing a one-way street. - Doug Linder Binary is as easy as 01, 10, 11. From rjh at sixdemonbag.org Mon Oct 12 12:06:56 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Mon, 12 Oct 2009 15:06:56 -0400 Subject: [Enigmail] ???????????????????????? In-Reply-To: <4AD292A7.4050201@estreet.com> References: <4AD292A7.4050201@estreet.com> Message-ID: <4AD37E50.1000903@sixdemonbag.org> richard c savage wrote: > What IS this???? In five words or less, "Enigmail integrates GnuPG with Thunderbird." If you don't use Thunderbird for your email client, or don't use GnuPG to provide email security, then you have no need for Enigmail. > It just came up on my newly-installed SUSE screen. Enigmail was not included on the last OpenSuSE 11.1 installation I did. I can't explain how it got included on yours. From moznews...hb at calen.de Fri Oct 16 17:50:20 2009 From: moznews...hb at calen.de (moznews...hb at calen.de) Date: Sat, 17 Oct 2009 02:50:20 +0200 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: Patrick Brunschwig schrieb: > Yes, I will release Enigmail v0.97.0 around the time of the Seamonkey > 2.0 release. ... Has https://bugzilla.mozilla.org/show_bug.cgi?id=521199 come to your attention? From mlisten at hammernoch.net Sat Oct 17 03:42:09 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Sat, 17 Oct 2009 12:42:09 +0200 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: <4AD99F81.8090808@hammernoch.net> "moznews...hb"@calen.de wrote on 17.10.09 02:50: > Patrick Brunschwig schrieb: >> Yes, I will release Enigmail v0.97.0 around the time of the Seamonkey >> 2.0 release. ... > > Has https://bugzilla.mozilla.org/show_bug.cgi?id=521199 come to your attention? Seems to be no Enigmail issue. See my comment from today there. Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From moznews...hb at calen.de Sat Oct 17 15:29:12 2009 From: moznews...hb at calen.de (moznews...hb at calen.de) Date: Sun, 18 Oct 2009 00:29:12 +0200 Subject: [Enigmail] Attach public key, and attachments. Attach my public key In-Reply-To: References: Message-ID: Charly Avital schrieb: > 1. When OpenPGP/Attach My Public Key is selected, trying to send a > signed or an encrypted/signed message will display a warning: > ...Sign/Encrypt failed, send unsigned/unencrypted..? Can confirm this for (Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091017 SeaMonkey/2.0.1pre and Enigmail 0.97a (20091013-0600). Error message appears before asking the passphrase. > 2. When OpenPGP/Attach Public Key... is enabled, and a public key is > selected from Enigmail's public keys list, sending a signed or encrypted > and signed message is successful, but the received message shows that no > public key file was attached. Confirming for Seamonkey 2.0.1. > 3. When using TB's 'Attach' ... > - select a public key *file* (attachment file shows in the upper right > corner of the window message) > - choose OpenPGP/Sign > > Enigmail displays what seems to be an in-line signed message (PGP > headers and footers are visible), displays also the expected window > where one can choose the three options for the attachment (sign/encrypt > message only-not the attachment, sign/encrypt attachment, use PGP/MIME) > > I choose the first option, I do NOT select use PGP/MIME > > The received message is displayed by TB/EM with a blue header line reading > OpenPGP: Possibly PGP/MIME encrypted or signed message; click Decrypt > button to verify. > The displayed message seems to be an in-line signed message, with PGP > headers and footers, and the attachment is there. Can't confirm this. "Just encrypt/sign the message text, but not the attachments" works as expected. > 4. OpenPGP/Preferences, whether invoked from Menu or from > Tools/Add-ons/0.96a, shows, after 'GnuPG was found in' a string of > characters, instead of the field where the path to gpg (or gpg2) should > be displayed. Can't confirm, path to exe ist valid. From cai.0407 at gmail.com Sat Oct 17 22:46:18 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Sun, 18 Oct 2009 14:46:18 +0900 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4AB1EA19.5010902@gmail.com> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> Message-ID: <4ADAABAA.4040000@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear, On Thu Sep 17 2009 16:49:45 GMT+0900, Kosuke Kaizuka wrote: > In summary, with my patch and your work, Enigmail will set encoding for > PGP/MIME-signed message written in ISO-2022-JP as below, right? > > TB3 - ISO-2022-JP/quoted-printable > TB2 - User can choose ISO-2022-JP/7bit with --rfc2440 or > UTF-8/quoted-printable by prefs When will these solutions be applied? Release of TB3 seems to be in near future. - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAkraq6kACgkQa+goYNi1URLo0gD/cHhGoqaWjNx3NQGN9vOgz6TE /rEx5G0LK8ODd/FK4zkA/jP5nooWdR5hf3zDJXb4I7wLJR0eRNaH/VilHvznfW/1 =y+2i -----END PGP SIGNATURE----- From mlisten at hammernoch.net Sun Oct 18 07:02:54 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Sun, 18 Oct 2009 16:02:54 +0200 Subject: [Enigmail] Attach public key, and attachments. Attach my public key In-Reply-To: References: Message-ID: <4ADB200E.6090300@hammernoch.net> Hi, "moznews...hb"@calen.de wrote on 18.10.09 00:29: > Charly Avital schrieb: >> 1. When OpenPGP/Attach My Public Key is selected, trying to send a >> signed or an encrypted/signed message will display a warning: >> ...Sign/Encrypt failed, send unsigned/unencrypted..? > > Can confirm this for (Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091017 > SeaMonkey/2.0.1pre and Enigmail 0.97a (20091013-0600). Error message appears > before asking the passphrase. Using Seamonkey 2.01pre on Mac OS X from today I can confirm this error both for PGP/MIME and inline-PGP. Using Thunderbird 3.0pre from today, there is no error in both cases. >> 2. When OpenPGP/Attach Public Key... is enabled, and a public key is >> selected from Enigmail's public keys list, sending a signed or encrypted >> and signed message is successful, but the received message shows that no >> public key file was attached. > > Confirming for Seamonkey 2.0.1. Happens here, too. Again not happening on TB3.0pre. Speculation: Seamonkey 2 didn't apply all internal API changes happening to Thunderbird 3 in July this year. Ludwig BTW: Your news setup seems to strip all "References" Headers, so your reply ended up as a new thread. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From patrick at mozilla-enigmail.org Sun Oct 18 10:14:06 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Sun, 18 Oct 2009 19:14:06 +0200 Subject: [Enigmail] Attach public key, and attachments. Attach my public key In-Reply-To: <4ADB200E.6090300@hammernoch.net> References: <4ADB200E.6090300@hammernoch.net> Message-ID: <4ADB4CDE.40907@mozilla-enigmail.org> On 18.10.2009 16:02, Ludwig H?gelsch?fer wrote: > Hi, > > "moznews...hb"@calen.de wrote on 18.10.09 00:29: >> Charly Avital schrieb: >>> 1. When OpenPGP/Attach My Public Key is selected, trying to send a >>> signed or an encrypted/signed message will display a warning: >>> ...Sign/Encrypt failed, send unsigned/unencrypted..? >> >> Can confirm this for (Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091017 >> SeaMonkey/2.0.1pre and Enigmail 0.97a (20091013-0600). Error message appears >> before asking the passphrase. > > Using Seamonkey 2.01pre on Mac OS X from today I can confirm this error > both for PGP/MIME and inline-PGP. Using Thunderbird 3.0pre from today, > there is no error in both cases. > >>> 2. When OpenPGP/Attach Public Key... is enabled, and a public key is >>> selected from Enigmail's public keys list, sending a signed or encrypted >>> and signed message is successful, but the received message shows that no >>> public key file was attached. >> >> Confirming for Seamonkey 2.0.1. > > Happens here, too. Again not happening on TB3.0pre. Both fixed on trunk, will be in tomorrow's nightly builds. > Speculation: Seamonkey 2 didn't apply all internal API changes happening > to Thunderbird 3 in July this year. Wrong this time ;-) It's simply one of the occasions where TB and SeaMonkey user interface differ and I didn't do anything about it. The only one to blame is me for once :-) -Patrick -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 552 bytes Desc: OpenPGP digital signature URL: From patrick at mozilla-enigmail.org Sun Oct 18 10:15:06 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Sun, 18 Oct 2009 19:15:06 +0200 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: <4ADB4D1A.8000101@mozilla-enigmail.org> On 17.10.2009 02:50, "moznews...hb"@calen.de wrote: > Patrick Brunschwig schrieb: >> Yes, I will release Enigmail v0.97.0 around the time of the Seamonkey >> 2.0 release. ... > > Has https://bugzilla.mozilla.org/show_bug.cgi?id=521199 come to your attention? If you think that I should be pointed to a bug, then please put me on the Cc list of the bug. -Patrick -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 552 bytes Desc: OpenPGP digital signature URL: From patrick at mozilla-enigmail.org Sun Oct 18 10:19:44 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Sun, 18 Oct 2009 19:19:44 +0200 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4ADAABAA.4040000@gmail.com> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> <4ADAABAA.4040000@gmail.com> Message-ID: <4ADB4E30.8080304@mozilla-enigmail.org> On 18.10.2009 07:46, Kosuke Kaizuka wrote: > Dear, > > On Thu Sep 17 2009 16:49:45 GMT+0900, Kosuke Kaizuka wrote: >> In summary, with my patch and your work, Enigmail will set encoding for >> PGP/MIME-signed message written in ISO-2022-JP as below, right? > >> TB3 - ISO-2022-JP/quoted-printable >> TB2 - User can choose ISO-2022-JP/7bit with --rfc2440 or >> UTF-8/quoted-printable by prefs > > When will these solutions be applied? Committed today on trunk. > Release of TB3 seems to be in near future. The TB 3 release will still take quite a while. Release candidate 1 is foreseen for early November ... -Patrick -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 552 bytes Desc: OpenPGP digital signature URL: From cai.0407 at gmail.com Sun Oct 18 21:13:44 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Mon, 19 Oct 2009 13:13:44 +0900 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4ADB4E30.8080304@mozilla-enigmail.org> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> <4ADAABAA.4040000@gmail.com> <4ADB4E30.8080304@mozilla-enigmail.org> Message-ID: <4ADBE778.7040008@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear Patrick, On 2009/10/19 2:19, Patrick Brunschwig wrote: >>> In summary, with my patch and your work, Enigmail will set encoding for >>> PGP/MIME-signed message written in ISO-2022-JP as below, right? >> >>> TB3 - ISO-2022-JP/quoted-printable >>> TB2 - User can choose ISO-2022-JP/7bit with --rfc2440 or >>> UTF-8/quoted-printable by prefs >> >> When will these solutions be applied? > > Committed today on trunk. Thank you for your work. But, unfortunately, Content-Transfer-Encoding of clear-text signed ISO-2022-JP message is set to 8bit. It is wrong, 7bit is correct. In case of ISO-2022-JP, msgCompFields.forceMsgEncoding should be false. My previous patch contains this fix too, but you omitted. Here is additional patch for enigmailMsgComposeOverlay.js 1.190. - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAkrb53YACgkQa+goYNi1URJMagD/eEZkkgNPm9KcseOl56kX57ZG +HT7zZWOUB1KyHWgEekA/i29175sYEQOXesUhYVeEtEVS3mEYYZ1bpviz9dL74vL =X8Pk -----END PGP SIGNATURE----- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: enigmailMsgComposeOverlay.js.patch URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: enigmailMsgComposeOverlay.js.patch.sig URL: From patrick at mozilla-enigmail.org Mon Oct 19 01:30:14 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Mon, 19 Oct 2009 10:30:14 +0200 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4ADBE778.7040008@gmail.com> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> <4ADAABAA.4040000@gmail.com> <4ADB4E30.8080304@mozilla-enigmail.org> <4ADBE778.7040008@gmail.com> Message-ID: <4ADC2396.1050104@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Kosuke Kaizuka wrote: > Dear Patrick, > > On 2009/10/19 2:19, Patrick Brunschwig wrote: >>>> In summary, with my patch and your work, Enigmail will set encoding for >>>> PGP/MIME-signed message written in ISO-2022-JP as below, right? >>>> TB3 - ISO-2022-JP/quoted-printable >>>> TB2 - User can choose ISO-2022-JP/7bit with --rfc2440 or >>>> UTF-8/quoted-printable by prefs >>> When will these solutions be applied? >> Committed today on trunk. > > Thank you for your work. > But, unfortunately, Content-Transfer-Encoding of clear-text signed > ISO-2022-JP message is set to 8bit. It is wrong, 7bit is correct. > > In case of ISO-2022-JP, msgCompFields.forceMsgEncoding should be false. > My previous patch contains this fix too, but you omitted. > > Here is additional patch for enigmailMsgComposeOverlay.js 1.190. upps, sorry. Fixed now. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBStwjlHcOpHodsOiwAQhzEAgAi1UGSulHe2qSFeXlVrXEUR405VG09Dbb LmIkd7znjozhq4kTjkFuBkQdruMhfFLqLWH3X0YI0DE3CeOY4uqikNklfryjF5y+ eL+KMoK3BBJrXbNeqFw80NDyoN6JT1CO10KnTgCHIp0tMo1uZ0GaHAHM6yjNMgRq DFGGXDb2Uo6CJiAUvi+D8DsXq5oya0vpjRotq29ILzPKR9BakRtRRn873dwiKT+V ijyt+gpiJMFN4lH9mMyH6xLwT6j6wz9x6FV5GosLvDiGhivdiW8jsH4e3E/9k90j Ay1N+UKlOq++APGT3qlM51lVmbyR2NgLYHyrhRyTzPew/V+ZpoIn7Q== =Lcx8 -----END PGP SIGNATURE----- From moznews...hb at calen.de Mon Oct 19 01:10:58 2009 From: moznews...hb at calen.de (moznews...hb at calen.de) Date: Mon, 19 Oct 2009 10:10:58 +0200 Subject: [Enigmail] Will Enigmail work on Seamonkey 2.0 Final? In-Reply-To: References: Message-ID: Patrick Brunschwig schrieb: > If you think that I should be pointed to a bug, then please put me on > the Cc list of the bug. This one changed to WORKSFORME after a fix in Seamonkey. If appropriate I will be glad to CC you the next time. Hb From cai.0407 at gmail.com Mon Oct 19 01:49:20 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Mon, 19 Oct 2009 17:49:20 +0900 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4ADC2396.1050104@mozilla-enigmail.org> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> <4ADAABAA.4040000@gmail.com> <4ADB4E30.8080304@mozilla-enigmail.org> <4ADBE778.7040008@gmail.com> <4ADC2396.1050104@mozilla-enigmail.org> Message-ID: <4ADC2810.5040701@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2009/10/19 17:30, Patrick Brunschwig wrote: > Kosuke Kaizuka wrote: >> Dear Patrick, > >> On 2009/10/19 2:19, Patrick Brunschwig wrote: >>>>> In summary, with my patch and your work, Enigmail will set encoding for >>>>> PGP/MIME-signed message written in ISO-2022-JP as below, right? >>>>> TB3 - ISO-2022-JP/quoted-printable >>>>> TB2 - User can choose ISO-2022-JP/7bit with --rfc2440 or >>>>> UTF-8/quoted-printable by prefs >>>> When will these solutions be applied? >>> Committed today on trunk. > >> Thank you for your work. >> But, unfortunately, Content-Transfer-Encoding of clear-text signed >> ISO-2022-JP message is set to 8bit. It is wrong, 7bit is correct. > >> In case of ISO-2022-JP, msgCompFields.forceMsgEncoding should be false. >> My previous patch contains this fix too, but you omitted. > >> Here is additional patch for enigmailMsgComposeOverlay.js 1.190. > > upps, sorry. Fixed now. Thank you so much! I will check next nightly nightly build (2009-10-20) and report here. - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAkrcKA8ACgkQa+goYNi1URJoEgD/RGTbvAclTpA6Cp1gHbnf8sM6 RIR5UtRC4UvAIJLMgEQA/3xF9j8OB8hNMDeEA13iNuCtPqY4Pqtg1SxD3yfnWafO =9F3S -----END PGP SIGNATURE----- From moznews...hb at calen.de Tue Oct 20 01:35:15 2009 From: moznews...hb at calen.de (moznews...hb at calen.de) Date: Tue, 20 Oct 2009 10:35:15 +0200 Subject: [Enigmail] Attach public key, and attachments. Attach my public key In-Reply-To: References: <4ADB200E.6090300@hammernoch.net> Message-ID: Patrick Brunschwig schrieb: > Both fixed on trunk, will be in tomorrow's nightly builds. VERIFIED FIXED From moznews...hb at calen.de Tue Oct 20 02:28:10 2009 From: moznews...hb at calen.de (moznews...hb at calen.de) Date: Tue, 20 Oct 2009 11:28:10 +0200 Subject: [Enigmail] Automatically verified PGP/MIME prevents deleting attachments Message-ID: Hi Patrick, Seamonkey 2 allows to delete or detach attachments from existing messages. This works fine for Inline signed messages. Using PGP/MIME and having Automatically Decrypt/Verify Messages set seems to prevent this. Attachments can't be detached or deleted any more. The context menu items are disabled. Is this behaviour intentional? Hb From patrick at mozilla-enigmail.org Tue Oct 20 03:58:50 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 20 Oct 2009 12:58:50 +0200 Subject: [Enigmail] Automatically verified PGP/MIME prevents deleting attachments In-Reply-To: References: Message-ID: <4ADD97EA.6010909@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 "moznews...hb"@calen.de wrote: > Hi Patrick, > > Seamonkey 2 allows to delete or detach attachments from existing messages. This > works fine for Inline signed messages. > > Using PGP/MIME and having Automatically Decrypt/Verify Messages set seems to > prevent this. Attachments can't be detached or deleted any more. The context > menu items are disabled. Is this behaviour intentional? Yes, this is intentional because deleting or detaching attachments would break the signature and for PGP/MIME encrypted messages destroy the message entirely such that it could not be recovered. The same restriction is implemented for S/MIME messages. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSt2X6XcOpHodsOiwAQjWrAf/Wh+4C99+qGdeZAF/w06OsKgo7Ny/L20Q cZliw9tlwAGd9Wi8QnxfQ7QvwxrGNkBfSkhrtmyxPk210DxEyzYwUCSA7+VHSlVT iJhE1e/Qh4kI1u+Oo/oiTBNIznFCkyLDz+2J0pit9Whv+t0y7HK4qTscm5VGliav pg5NtPeTo+Z4eLePsQhu8uC5sVSAh0RrHVJLB2ZgRoM05qmnxyBIIZwtxyi20wRy Wt4DEsSUgl1/L6Cl/NOKHRG+NM4Xmsos9CP/9BLAXX66VwGqvpSKi84ZNNw5n89Z doJgYZiq8MMhDjj8iHYdBOrA9jA8kAyJ3+YBIKQ/TF9vmg8Rw+Nknw== =GWag -----END PGP SIGNATURE----- From cai.0407 at gmail.com Tue Oct 20 04:10:56 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Tue, 20 Oct 2009 20:10:56 +0900 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4ADC2810.5040701@gmail.com> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> <4ADAABAA.4040000@gmail.com> <4ADB4E30.8080304@mozilla-enigmail.org> <4ADBE778.7040008@gmail.com> <4ADC2396.1050104@mozilla-enigmail.org> <4ADC2810.5040701@gmail.com> Message-ID: <4ADD9AC0.1030201@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon Oct 19 2009 17:49:20 GMT+0900, Kosuke Kaizuka wrote: > I will check next nightly nightly build (2009-10-20) and report here. I installed 2009-10-20 nightly and it works well! Thanks a lot! - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAkrdmr8ACgkQa+goYNi1URLV+QD/f8KtOQuVxoteefGzjVkd7NcQ d31tfC629060dKCnVvIA/jGraKDX3mILmns30vkj/AasUwH8L0D3OojmHAxkWioB =Kthv -----END PGP SIGNATURE----- From jarif at iki.fi Tue Oct 20 07:53:03 2009 From: jarif at iki.fi (Jari Fredriksson) Date: Tue, 20 Oct 2009 17:53:03 +0300 Subject: [Enigmail] Hello (test-ignore) Message-ID: <4ADDCECF.3060700@iki.fi> Just installed Enigmail for my TB3B4. Testing how it signs. -- http://www.iki.fi/jarif/ Save energy: be apathetic. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From jarif at iki.fi Tue Oct 20 09:11:54 2009 From: jarif at iki.fi (Jari Fredriksson) Date: Tue, 20 Oct 2009 19:11:54 +0300 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG Message-ID: <4ADDE14A.3010203@iki.fi> I have a PGP keyring file from a PGP installation that I do not have any more. Is it possible to import to GnuPG somehow? This may be offtopic for this list, but I think someone here might know the answer anyway. -- http://www.iki.fi/jarif/ Extreme fear can neither fight nor fly. -- William Shakespeare, "The Rape of Lucrece" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From olav at mozilla-enigmail.org Tue Oct 20 09:29:45 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Tue, 20 Oct 2009 18:29:45 +0200 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG In-Reply-To: <4ADDE14A.3010203@iki.fi> References: <4ADDE14A.3010203@iki.fi> Message-ID: <4ADDE579.8080805@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Jari, > I have a PGP keyring file from a PGP installation that I do not have any > more. > > Is it possible to import to GnuPG somehow? This may be offtopic for this > list, but I think someone here might know the answer anyway. I haven't tried the last couple of years but once PGP and GnuPG keyrings were even binary compatible, I shared the same files between PGP 7 and GnuPG 1.x once. You should not have any problem just importing the files using GnuPG CLI or Enigmail: (from the main TB/SM window) -> OpenPGP -> Manage Keys -> File -> Import (twice, once for the public keyring and once for the secret keyring. Trust settings I would set manually in Enigmail (you may select multiple keys) according to your today's knowledge about your communication partners. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Diese Email ist digital signiert und/oder verschl?sselt Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkrd5XgACgkQL/NBt8fdKe3lvwCfXU+4l4p4YaayVUOYAQyxV0Dr 6dwAmwbpRlxpWoFos9l6NfKU7vGDymXO =OIoO -----END PGP SIGNATURE----- From patrick at mozilla-enigmail.org Tue Oct 20 09:42:05 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 20 Oct 2009 18:42:05 +0200 Subject: [Enigmail] Problems with german umlauts in path or attachment In-Reply-To: References: <4AA632BF.3020301@mozilla-enigmail.org> Message-ID: <4ADDE85D.4090206@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Frank Becker wrote: >> Update to Enigmail v0.96.0 >> -Patrick > > Hello Patrick, > > I did so but the problem still exists. > The errormessage is: > gpg: '/home/apo-promotion/Projekte/T?niesweg 15/A Zettel.pdf' cannot be > opened. File or directory not found. > gpg: signing failed: Error opening the file. > > If the file has no german umlauts everybody is ok. I committed a number of fixes today; I think it should be fine with tomorrow's nightly builds (Thunderbird 3 beta only). - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSt3oXHcOpHodsOiwAQjI2gf9FFJzbRP+kt1kVpE0If7RqtggVNJMM9UI oh1XIeGxtr/FYrF9gisdOmxAM2K8M7ki8C4Flu0gwYD7EXnVqpMLgYzxF5SDvSW0 obhTXR3Zv9E9A9vIRkWJStbU9wkpasWClS0xQL8RHzdUVkt5XM3k6z+34HPUHzyx 3CVdNbL0TVp+utYa9rgO5eauw46pmAIJmkOeoTcYFGqz4c5q4CFH+3GGyU0mEMgZ Wcme3RdhaSpCF/4PQOPBIHiq0VLbyymVDdQSJDmSRw0s7Zbx3x0kr2pjWXx7sh+K jRfhmYN82AHSktN8X0yZf6v3LrqChYl1W+y9uoLgyGh0aLLBg4OcBg== =hFqN -----END PGP SIGNATURE----- From John at Mozilla-Enigmail.org Tue Oct 20 09:45:02 2009 From: John at Mozilla-Enigmail.org (John Clizbe) Date: Tue, 20 Oct 2009 11:45:02 -0500 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG In-Reply-To: <4ADDE579.8080805@mozilla-enigmail.org> References: <4ADDE14A.3010203@iki.fi> <4ADDE579.8080805@mozilla-enigmail.org> Message-ID: <4ADDE90E.1090708@Mozilla-Enigmail.org> Olav Seyfarth wrote: > Hi Jari, > >> I have a PGP keyring file from a PGP installation that I do not have any >> more. > >> Is it possible to import to GnuPG somehow? This may be offtopic for this >> list, but I think someone here might know the answer anyway. As long as you have secring.skr and pubring.pkr, you should have no problems > I haven't tried the last couple of years but once PGP and GnuPG keyrings were > even binary compatible, I shared the same files between PGP 7 and GnuPG 1.x > once. Still are (for the time being). Trust is the only thing that doesn't transfer and has to be set manually in GnuPG. > You should not have any problem just importing the files using GnuPG CLI or > Enigmail: (from the main TB/SM window) -> OpenPGP -> Manage Keys -> File -> > Import (twice, once for the public keyring and once for the secret keyring. > Trust settings I would set manually in Enigmail (you may select multiple keys) > according to your today's knowledge about your communication partners. Yep all there is to it. I'd do the secret ring first. -- John P. Clizbe Inet:John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net or mailto:pgp-public-keys at gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 679 bytes Desc: OpenPGP digital signature URL: From jarif at iki.fi Tue Oct 20 10:01:11 2009 From: jarif at iki.fi (Jari Fredriksson) Date: Tue, 20 Oct 2009 20:01:11 +0300 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG In-Reply-To: <4ADDE90E.1090708@Mozilla-Enigmail.org> References: <4ADDE14A.3010203@iki.fi> <4ADDE579.8080805@mozilla-enigmail.org> <4ADDE90E.1090708@Mozilla-Enigmail.org> Message-ID: <4ADDECD7.1050004@iki.fi> 20.10.2009 19:45, John Clizbe kirjoitti: > Olav Seyfarth wrote: >> Hi Jari, >> >>> I have a PGP keyring file from a PGP installation that I do not have any >>> more. >> >>> Is it possible to import to GnuPG somehow? This may be offtopic for this >>> list, but I think someone here might know the answer anyway. > > As long as you have secring.skr and pubring.pkr, you should have no problems > >> I haven't tried the last couple of years but once PGP and GnuPG keyrings were >> even binary compatible, I shared the same files between PGP 7 and GnuPG 1.x >> once. > > Still are (for the time being). Trust is the only thing that doesn't transfer > and has to be set manually in GnuPG. > >> You should not have any problem just importing the files using GnuPG CLI or >> Enigmail: (from the main TB/SM window) -> OpenPGP -> Manage Keys -> File -> >> Import (twice, once for the public keyring and once for the secret keyring. >> Trust settings I would set manually in Enigmail (you may select multiple keys) >> according to your today's knowledge about your communication partners. > > Yep all there is to it. I'd do the secret ring first. > Yup I imported secring.skr and all seems to be swell ;D Thanks guys. I changed my signature key now that I got the old key back, hopefully it does not cause problems ;) Cheers! > > > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail -- http://www.iki.fi/jarif/ Harp not on that string. -- William Shakespeare, "Henry VI" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From John at Mozilla-Enigmail.org Tue Oct 20 10:13:36 2009 From: John at Mozilla-Enigmail.org (John Clizbe) Date: Tue, 20 Oct 2009 12:13:36 -0500 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG In-Reply-To: <4ADDECD7.1050004@iki.fi> References: <4ADDE14A.3010203@iki.fi> <4ADDE579.8080805@mozilla-enigmail.org> <4ADDE90E.1090708@Mozilla-Enigmail.org> <4ADDECD7.1050004@iki.fi> Message-ID: <4ADDEFC0.5050504@Mozilla-Enigmail.org> Jari Fredriksson wrote: > Yup I imported secring.skr and all seems to be swell ;D > > Thanks guys. I changed my signature key now that I got the old key back, > hopefully it does not cause problems ;) Looks fine OpenPGP Security Info UNTRUSTED Good signature from Jari Fredriksson Key ID: 0xECA34AB6 / Signed on: 10/20/2009 12:01 Key fingerprint: A349 262D 6D9D 0BC6 9D48 F825 28BE 08CC ECA3 4AB6 -- John P. Clizbe Inet:John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net or mailto:pgp-public-keys at gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 679 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Tue Oct 20 10:32:12 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Tue, 20 Oct 2009 13:32:12 -0400 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG In-Reply-To: <4ADDE579.8080805@mozilla-enigmail.org> References: <4ADDE14A.3010203@iki.fi> <4ADDE579.8080805@mozilla-enigmail.org> Message-ID: <4ADDF41C.7040701@sixdemonbag.org> Olav Seyfarth wrote: > I haven't tried the last couple of years but once PGP and GnuPG > keyrings were even binary compatible, I shared the same files between > PGP 7 and GnuPG 1.x once. As of PGP 9.x and GnuPG 1.4.x/2.x, they are still binary compatible. I haven't done any testing beyond those versions, and I can't claim to have done exhaustive testing -- but the keyrings I tried worked just fine. From jarif at iki.fi Tue Oct 20 10:32:40 2009 From: jarif at iki.fi (Jari Fredriksson) Date: Tue, 20 Oct 2009 20:32:40 +0300 Subject: [Enigmail] Lost HTML messages view after installing Enigmail Message-ID: <4ADDF438.1080603@iki.fi> I guess and remember there was such selection in the installation/setup wizard. Somehow the question was such that I selected to see plain text. But now I want to see html. I can't find such in the OpenPGP settings. Where is that toggle? Newspapers send html mail, and I have ThunderBrowse to see them fully. I want html back ;) Anyone? -- http://www.iki.fi/jarif/ Good day for a change of scene. Repaper the bedroom wall. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From jmoore3rd at bellsouth.net Tue Oct 20 10:39:57 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Tue, 20 Oct 2009 13:39:57 -0400 Subject: [Enigmail] Lost HTML messages view after installing Enigmail In-Reply-To: <4ADDF438.1080603@iki.fi> References: <4ADDF438.1080603@iki.fi> Message-ID: <4ADDF5ED.7030309@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Jari Fredriksson wrote: > > I guess and remember there was such selection in the installation/setup > wizard. > > Somehow the question was such that I selected to see plain text. But now > I want to see html. > > I can't find such in the OpenPGP settings. Where is that toggle? > > Newspapers send html mail, and I have ThunderBrowse to see them fully. I > want html back ;) Under the 'View' Tab on the T-Bird Toolbar. Then progress to 'Message Body As'. HTH When Composing just hold down the 'Shift' Key while clicking 'Write' or 'Reply'. JOHN ;) Timestamp: Tuesday 20 Oct 2009, 13:39 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJK3fXrAAoJEBCGy9eAtCsPXWUH/A+1DEHqqLDFjJhBb8L8378K suAj7NgRUN/8nGRnTh1SsM8/grW904FHILQf7pEvHGvbbWTYfaZogs2RnzMtkIA0 fpHG3bAmOBSf6ENeci9vjKAbpLu0CLnb2a1pv8PF8SGUivmEGuWJIlin2mytsDzP qwCKi2yPnZ25KJ3qCfNHn1/AYmS8AESYCT0IjZsk6bak011/CHBo1CVpfgBSThgn 3bjEVy7ANmCRlPKGx4IAc0uZbw9J0KkT7xZnUcj1ZXPNpToPKuf+dhdsZKLODutq zVYAtpYqp1CcYBxHm8GEU7GMTevSEEoadj6Q4M2Ao39oTvDUU9c+nm7dhOR7L10= =TnFm -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Tue Oct 20 10:58:49 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Tue, 20 Oct 2009 19:58:49 +0200 Subject: [Enigmail] (Offtopic?) PGP private key to GnuPG In-Reply-To: <4ADDF41C.7040701@sixdemonbag.org> References: <4ADDE14A.3010203@iki.fi> <4ADDE579.8080805@mozilla-enigmail.org> <4ADDF41C.7040701@sixdemonbag.org> Message-ID: <4ADDFA59.5080506@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi list, > As of PGP 9.x and GnuPG 1.4.x/2.x, they are still binary compatible. mind that PGP's default installation keeps the keyrings locked, so you might get GnuPG file access failure errors if GPG service is running in the background. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Diese Email ist digital signiert und/oder verschl?sselt Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkrd+lUACgkQL/NBt8fdKe2+ZwCgmlRHvQUtdGGhPqlqbuudY5C+ NJwAnjx0geHiL5sS5hCWXP6TqMasgu6I =Op0n -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Tue Oct 20 11:03:33 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Tue, 20 Oct 2009 20:03:33 +0200 Subject: [Enigmail] Lost HTML messages view after installing Enigmail In-Reply-To: <4ADDF438.1080603@iki.fi> References: <4ADDF438.1080603@iki.fi> Message-ID: <4ADDFB75.2010003@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Jari, > Somehow the question was such that I selected to see plain text. But now > I want to see html. Mind that the combination HTML + INLINE PGP is error prone. If you permanently use HTML email (which I personally discourage) then make sure to use PGP/MIME by default (which may cause other oddities with certain clients, see Enigmail Documentation on the website). I installed https://addons.mozilla.org/thunderbird/addon/1556 and use plain text as default. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Diese Email ist digital signiert und/oder verschl?sselt Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkrd+3QACgkQL/NBt8fdKe2NCwCeOAc5xNWeDMLv1KeBcx5ebDAa chYAoJEcM3FpXAnNrGz016XGfKR3lkiZ =fHdN -----END PGP SIGNATURE----- From jarif at iki.fi Tue Oct 20 11:18:30 2009 From: jarif at iki.fi (Jari Fredriksson) Date: Tue, 20 Oct 2009 21:18:30 +0300 Subject: [Enigmail] Lost HTML messages view after installing Enigmail In-Reply-To: <4ADDFB75.2010003@mozilla-enigmail.org> References: <4ADDF438.1080603@iki.fi> <4ADDFB75.2010003@mozilla-enigmail.org> Message-ID: <4ADDFEF6.6050503@iki.fi> 20.10.2009 21:03, Olav Seyfarth kirjoitti: > Hi Jari, > >> Somehow the question was such that I selected to see plain text. But now >> I want to see html. > > Mind that the combination HTML + INLINE PGP is error prone. If you permanently > use HTML email (which I personally discourage) then make sure to use PGP/MIME > by default (which may cause other oddities with certain clients, see Enigmail > Documentation on the website). > > I installed https://addons.mozilla.org/thunderbird/addon/1556 and use plain > text as default. > > Olav Well.. I use PGP/MIME by default, and I was just about to ask why some people do use inline pgp. It looks awful to those who do not use pgp at all. Well, except that in Outlook Express PGP/MIME looks awful, because it shows the text part as an attachment also, and a blank message ;) Well, people use inline pgp probably because some of their mailing partners can't handle PGP/MIME.. right? I use PGP/MIME by default, and the HTML mail I receive does not have any PGP at all. I prefer to send with PGP, plain text. But I do receive HTML sans PGP from newspapers. They have nice images and all that makes a news nice to read. > I installed https://addons.mozilla.org/thunderbird/addon/1556 and use > plain text as default. I do not need such addons. I receive all kinds of email with pleasure, filtered with amavisd-new, F-Prot, ClamAV, BitDefender and Windows Security Essentials. I post only plain text with PGP using the Thunderbird settings. No addons needed. _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail -- http://www.iki.fi/jarif/ You will experience a strong urge to do good; but it will pass. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Tue Oct 20 11:32:51 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Tue, 20 Oct 2009 14:32:51 -0400 Subject: [Enigmail] Lost HTML messages view after installing Enigmail In-Reply-To: <4ADDFB75.2010003@mozilla-enigmail.org> References: <4ADDF438.1080603@iki.fi> <4ADDFB75.2010003@mozilla-enigmail.org> Message-ID: <4ADE0253.5050306@sixdemonbag.org> Olav Seyfarth wrote: > Mind that the combination HTML + INLINE PGP is error prone. If you > permanently use HTML email (which I personally discourage) then make > sure to use PGP/MIME by default (which may cause other oddities with > certain clients, see Enigmail Documentation on the website). I agree with this advice, but I think we may want to rethink our counsel. For the non-engineers on this list, a good rule of thumb is that simple systems are more reliable than complicated ones. Plain text email is very simple. We've known how to do it since the early 1970s. Plain text email is also a fixed, known quantity: the internet standards that define plain text email have not been substantially changed in many, many years. HTML email is orders of magnitude more complex. On top of that, the HTML standards keep changing. HTML email of today is not HTML email of five years ago. HTML clients often render things very differently (e.g., Thunderbird on OS X cannot display a block indent, but Thunderbird on Linux or Windows can). And on top of that, HTML's complexity makes it much easier for people to infect your computer with malware. Those two things are why many engineers very much prefer plain text email to HTML email. But, I think we also need to face reality. The world has moved to HTML email whether we want them to or not. For us to say, "HTML email is bad, use plain text!", well... to most users it sounds like we're wearing the hairshirt.[*] When we tell people to not use HTML email, we're really telling them, "don't embed YouTube clips in your email, give up using neat fonts and colors and styles, forget about sending photographs to your friends," etc., etc. It turns people off, and makes people stop listening to us. I think that we need to change our minds on HTML email. Instead of saying, "don't use HTML email," I think we should instead encourage people to use safer HTML clients (like Thunderbird) and to remind people to keep their antivirus software up to date. [*] For non-English native speakers: a "hairshirt" is a medieval garment made out of an extremely coarse and irritating wool. Religious zealots would wear them in order to inflict severe discomfort on themselves, in order to show how "pure" and "Christlike" they were. In idiomatic speech, "wearing the hairshirt" means "deliberately inflicting pain on yourself in order to show moral superiority." From rjh at sixdemonbag.org Tue Oct 20 11:36:26 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Tue, 20 Oct 2009 14:36:26 -0400 Subject: [Enigmail] Lost HTML messages view after installing Enigmail In-Reply-To: <4ADDFEF6.6050503@iki.fi> References: <4ADDF438.1080603@iki.fi> <4ADDFB75.2010003@mozilla-enigmail.org> <4ADDFEF6.6050503@iki.fi> Message-ID: <4ADE032A.2010109@sixdemonbag.org> Jari Fredriksson wrote: > I use PGP/MIME by default, and I was just about to ask why some people > do use inline pgp. It looks awful to those who do not use pgp at all. You're absolutely right. PGP/MIME is a far better standard. The problem comes from MTAs (Mail Transfer Agents). Many MTAs will, in the interests of fighting malware, strip off attachments from email. Many mailing lists are configured to disallow attachments. Things like this remove attachments and thus break PGP/MIME. Ten years ago this was a very big problem. Nowadays it's less so. PGP/MIME is the recommended way to send traffic _if you know it'll arrive intact_. If you don't know, though, inline PGP is more reliable, albeit a little more primitive. Also, some old (read: broken) clients can't read PGP/MIME. People using these clients really, really need to upgrade. From mlisten at hammernoch.net Tue Oct 20 12:12:06 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Tue, 20 Oct 2009 21:12:06 +0200 Subject: [Enigmail] Lost HTML messages view after installing Enigmail In-Reply-To: <4ADE0253.5050306@sixdemonbag.org> References: <4ADDF438.1080603@iki.fi> <4ADDFB75.2010003@mozilla-enigmail.org> <4ADE0253.5050306@sixdemonbag.org> Message-ID: <4ADE0B86.1090109@hammernoch.net> Robert J. Hansen wrote on 20.10.09 20:32: > I think that we need to change our minds on HTML email. Instead of > saying, "don't use HTML email," I think we should instead encourage > people to use safer HTML clients (like Thunderbird) and to remind people > to keep their antivirus software up to date. The big paradoxon is, that the most HTML messages come from a client, that cannot display PGP/MIME, at least out of the box. Want to say: One would need to start a real real big campaign to change the attitudes. Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From kyshk at bc.iij4u.or.jp Tue Oct 20 19:06:19 2009 From: kyshk at bc.iij4u.or.jp (kyshk at bc.iij4u.or.jp) Date: Wed, 21 Oct 2009 11:06:19 +0900 Subject: [Enigmail] Problem of 7bit characters (epecially ISO-2022-JP) In-Reply-To: <4ADC2396.1050104@mozilla-enigmail.org> References: <4AAE2E8C.8000600@gmail.com> <4AAE4CCB.1000601@mozilla-enigmail.org> <4AAE61C2.30504@bc.iij4u.or.jp> <4AAF56B5.3040504@mozilla-enigmail.org> <4AB077A5.1050204@bc.iij4u.or.jp> <4AB08989.5020802@mozilla-enigmail.org> <4AB0911D.4040904@bc.iij4u.or.jp> <4AB098D0.1040103@mozilla-enigmail.org> <4AB0A9C8.3030608@bc.iij4u.or.jp> <4AB0AE26.9070008@mozilla-enigmail.org> <4AB0B193.2070906@gmail.com> <4AB0CD22.7070300@mozilla-enigmail.org> <4AB0D760.6090602@gmail.com> <4AB0F7D5.6060003@mozilla-enigmail.org> <4AB1B15F.4050600@gmail.com> <4AB1E185.1050104@mozilla-enigmail.org> <4AB1EA19.5010902@gmail.com> <4ADAABAA.4040000@gmail.com> <4ADB4E30.8080304@mozilla-enigmail.org> <4ADBE778.7040008@gmail.com> <4ADC2396.1050104@mozilla-enigmail.org> Message-ID: <4ADE6C9B.3040700@bc.iij4u.or.jp> Thank you, Patrick! -- kiyo From haloris-tx at yahoo.co.uk Thu Oct 22 05:56:10 2009 From: haloris-tx at yahoo.co.uk (Carson Hewitt) Date: Thu, 22 Oct 2009 14:56:10 +0200 Subject: [Enigmail] encryptToSelf preference Message-ID: Hello, In my setup, setting 'extensions.enigmail.encryptToSelf' to false does not seem to make a difference. Enigmail keeps inserting --encrypt-to and -r switches based on the from address or the keyID rule (I want to rely on gpg.conf for this). Version: TBird 2.0.23 Enigmail 0.96.0 MacOS 10.6.1 I'll try again later on another OS. Does anyone else see this ? -- From haloris-tx at yahoo.co.uk Mon Oct 26 06:57:06 2009 From: haloris-tx at yahoo.co.uk (Carson Hewitt) Date: Mon, 26 Oct 2009 14:57:06 +0100 Subject: [Enigmail] encryptToSelf preference References: Message-ID: In article , Carson Hewitt wrote: > Hello, > > In my setup, setting 'extensions.enigmail.encryptToSelf' to false does not > seem > to make a difference. Enigmail keeps inserting --encrypt-to and -r switches > based on the from address or the keyID rule (I want to rely on gpg.conf for > this). > Please ignore. Today it's working as expected. Go figure. Perhaps some people had better stay away from computers. From mnyromyr at tprac.de Tue Oct 27 02:33:48 2009 From: mnyromyr at tprac.de (=?ISO-8859-1?Q?Karsten_D=FCsterloh?=) Date: Tue, 27 Oct 2009 10:33:48 +0100 Subject: [Enigmail] show/hide messagepane broken (F8) Message-ID: Moin! Using the Enigmail nightly "0.97b (20091027-0459)" in SeaMonkey 2.0RC2, I can't toggle the messagepane via F8 anymore. "View->Layout->Message Pane" still works (as does clicking the grippy), but F8 just flashes the statusbar with "Loading Message". Is this known? Should I file a bug? Karsten From patrick at mozilla-enigmail.org Tue Oct 27 03:28:24 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 27 Oct 2009 11:28:24 +0100 Subject: [Enigmail] show/hide messagepane broken (F8) In-Reply-To: References: Message-ID: <4AE6CB48.8030902@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Karsten D?sterloh wrote: > Moin! > > Using the Enigmail nightly "0.97b (20091027-0459)" in SeaMonkey 2.0RC2, > I can't toggle the messagepane via F8 anymore. > "View->Layout->Message Pane" still works (as does clicking the grippy), > but F8 just flashes the statusbar with "Loading Message". > > Is this known? Should I file a bug? Hi Karsten, please file a bug. I fixed the messagepane toggling for TB3, but probably broke it for SeaMonkey ... - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSubLR3cOpHodsOiwAQgNjAf+PeBlr1L3Gpf9oVE76MaOHGqKul7xK64e IwHQwCDR2I963vnvjNLUX6MJDyJT4vcufUlnL7Y/UugmSmpgbdokNAPwrMZ3PeSQ UBifjXuY0u4MIsu74lo6DWiIcVh0aTX158+sxXNztcC5i4JeJ88As4JNt3km8K8C tJ/CQC653EYTl1gGcn17HWVzn6Bjq4FjkTVCWee7OsUCeVldiVorXTjeZRfMShkN X++nw3Wzk6EHucFrvhgHn5FBA4vmGtgTl8bcj5kHkJUzJJTofQFPqFxWY1/SB4q7 N3A3tJY0hgizo5ag02yWc1Es79+f+dTcFzN0AK+YlT8OWwUIsdDwgw== =y4Ft -----END PGP SIGNATURE----- From mnyromyr at tprac.de Tue Oct 27 03:30:10 2009 From: mnyromyr at tprac.de (=?ISO-8859-1?Q?Karsten_D=FCsterloh?=) Date: Tue, 27 Oct 2009 11:30:10 +0100 Subject: [Enigmail] show/hide messagepane broken (F8) In-Reply-To: References: Message-ID: Karsten D?sterloh wrote: > Using the Enigmail nightly "0.97b (20091027-0459)" in SeaMonkey 2.0RC2, > I can't toggle the messagepane via F8 anymore. > "View->Layout->Message Pane" still works (as does clicking the grippy), > but F8 just flashes the statusbar with "Loading Message". Forgot to mention this: Error: mimeMsg is null Source File: chrome://enigmail/content/enigmailMessengerOverlay.js Line: 524 Karsten From mnyromyr at tprac.de Tue Oct 27 03:43:08 2009 From: mnyromyr at tprac.de (=?ISO-8859-1?Q?Karsten_D=FCsterloh?=) Date: Tue, 27 Oct 2009 11:43:08 +0100 Subject: [Enigmail] show/hide messagepane broken (F8) In-Reply-To: References: Message-ID: Karsten D?sterloh wrote: > Karsten D?sterloh wrote: >> > Using the Enigmail nightly "0.97b (20091027-0459)" in SeaMonkey 2.0RC2, >> > I can't toggle the messagepane via F8 anymore. >> > "View->Layout->Message Pane" still works (as does clicking the grippy), >> > but F8 just flashes the statusbar with "Loading Message". > Forgot to mention this: > > Error: mimeMsg is null > Source File: chrome://enigmail/content/enigmailMessengerOverlay.js > Line: 524 Filed . Karsten From michaeljgruber+mozdevnews at fastmail.fm Tue Oct 27 07:50:11 2009 From: michaeljgruber+mozdevnews at fastmail.fm (Michael J Gruber) Date: Tue, 27 Oct 2009 15:50:11 +0100 Subject: [Enigmail] Import from keyserver not working (T3beta) Message-ID: Hi there, is "import from keyserver" supposed to be working with T3beta (comm-1.9.1)? Specifically, after clicking on details, Enigmail asks (for confirmation and) for the key server and then gives an alert saying: Error - No valid armored OpenPGP data block found After clicking that away, a dialog is open (Downloading OpenPGP Keys), with progress bar at 100%, OK greyed out. This happens reproducibly for keys which I can "gpg --recv-key" without problems. Builds: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5pre) Gecko/20091027 Lightning/1.0pre Shredder/3.0pre Enigmail version 0.97a (20091023-1604) Fedora 11 x86 And yes, tested with a different profile, although this used to work in my main profile. Cheers, Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 261 bytes Desc: OpenPGP digital signature URL: From patrick at mozilla-enigmail.org Tue Oct 27 10:03:51 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 27 Oct 2009 18:03:51 +0100 Subject: [Enigmail] Enigmail and SeaMonkey 2.0 Message-ID: <4AE727F7.2020202@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 With the SeaMonkey 2.0 release today, some people may wonder whether there is an Enigmail version supporting SeaMonkey officially. Here is the answer: There is no finaly version of Enigmail for SeaMonkey 2.0 available yet, however I'm planning to release a new version soon (latest when Thunderbird 3.0 will be released). The reason for this is that I still want to fix some recently discovered bugs in Enigmail. Until then, those using SeaMonkey 2.0 please use the nightly builds of Enigmail. Even though they are attributed "alpha", they are stable and work quite nicely. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSucn9XcOpHodsOiwAQh4qwf+Jq3qaZ5KttnB5+rjb6FNrmVfpiWOkh1O wFDCAI6f3fOZqPFJtA0RIZ6xiBA7Hw3TaWxgyRH3uS30XygwJLmgvEMUAGvMU4Yv UXn5IpQX2eStk7qCrsn1tqf88tmIxRSzN3lWqq3++WPjBdJKvEdRt4fbUMZUm439 uoNbPzjwJyL/Y16eJQyzB0/qDCFnfniewzKQgX+UsAF/1NvsUkGUE6HPx3HSA2Ja r8gay8+NNYzNk6AHs/Np9JNwszXNWuz9HhGZFR2SJecsF0qL5dCkCUWC2ksFfOeP l/k6EU8kGoGwkPrpR0qssw5tlH5uJ9sOFQ5KN5pNz/oEvP/khEyt5w== =hujn -----END PGP SIGNATURE----- From cai.0407 at gmail.com Tue Oct 27 19:05:14 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Wed, 28 Oct 2009 11:05:14 +0900 Subject: [Enigmail] Enigmail and SeaMonkey 2.0 In-Reply-To: <4AE727F7.2020202@mozilla-enigmail.org> References: <4AE727F7.2020202@mozilla-enigmail.org> Message-ID: <4AE7A6DA.8040401@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, Patrick On Wed Oct 28 2009 01:51:13 GMT+0900, Cai wrote: > There is no finaly version of Enigmail for SeaMonkey 2.0 available yet, > however I'm planning to release a new version soon (latest when > Thunderbird 3.0 will be released). The reason for this is that I still > want to fix some recently discovered bugs in Enigmail. When will UI string be frozen for 0.97? - -- Kosuke Kaizuka OpenPGP key has been superseded; 0x4E8E48D9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJK56bZAAoJEFI91dNOjkjZzsYP/A/18/YLK3z2AOdXekA8ngge bbNXT59/+PvYB6CyIiasdtzl+AktdTQwbgi8HNWonurVFYNiSNMcSJDGe/sSUrvs gvMjFReh14HHoJH3Eb+SkFAQI40eLFs5p87nQymdHmr6jfDzv6Nn+8wJh5qk6ler xWmHGY4sgZjcD81G2XzchUm5cSEQyDgfqQaNt5I3N/YY/Tu97ftMecN6+xKjxtxO M6GruXNVwO0SMDO/CuRPaaF4i8L9/ZvkQnCnsvZwY+qoEXR4L5zcsUBkOtXa506K nuR4ThAbORCGDyK34WpX3dEvkQlwALMSYwRb2myFjYlZabQsO4WVcCrRpqu8MHLs YYLTsQh+HNfhp8s39qNicdNdb08hcwmsM3UH5H5wvIekesWhKuXjepnqda/qrXmb t0W/Qvo9jdaSJI9b3p+nAgMZrG7KMtJbzALx3wrXGrPmWwU7nj4U8vqKEsYfdAQG yhdg4rwdX24DC2VUshYZFNfZ85ck5vMDaYg2Mm80hZkiBs/rqiHAcaQvKgGc03vN CM6mDO8Ud7WrvK6gNnAjST13ci5qTGM2K5MHK5+5yZtfkrMnhFAG0XJc1dFmOC0y xCbBsXufj1KyIjKpQ5xv6Pu6811EIFu/EHpFcXic9aS4MYPukEjSlYKIHvyfSW3r usLqLGsuizocq/ukFc5B =T5y3 -----END PGP SIGNATURE----- From patrick at mozilla-enigmail.org Wed Oct 28 01:35:35 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Wed, 28 Oct 2009 09:35:35 +0100 Subject: [Enigmail] Enigmail and SeaMonkey 2.0 In-Reply-To: <4AE7A6DA.8040401@gmail.com> References: <4AE727F7.2020202@mozilla-enigmail.org> <4AE7A6DA.8040401@gmail.com> Message-ID: <4AE80257.70801@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Kosuke Kaizuka wrote: > Hi, Patrick > > On Wed Oct 28 2009 01:51:13 GMT+0900, Cai wrote: >> There is no finaly version of Enigmail for SeaMonkey 2.0 available yet, >> however I'm planning to release a new version soon (latest when >> Thunderbird 3.0 will be released). The reason for this is that I still >> want to fix some recently discovered bugs in Enigmail. > > When will UI string be frozen for 0.97? As soon as you'll get an email ;-) - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSugCVncOpHodsOiwAQiNVwgAqyg9ApWepfrS57uCdJbnuKdievrHLYHR Y2aw13RDalqVfpJepvGBXUUgGSyi3v38sx9kWxxpJ71vvmKmKhaJ0/5BO5Z1v3bJ pB4sFygNkzMy9poprGdkaEUqnNUVCAS6iPMY4nvltwqU+jStQjDhVLambG70Uh/W wQowYWZpAGUSdOW9ewa1sK++RcxaX0OhrBYITCOgOzGWv0esQHmaJ/7RBgCr+piC NySQT1gEA/8IHvHlmK+uB6l1Z/a4u8sIKuoYAZu8FINJ7gmANrVgO7We0bOTntUk FrMS+bOWT3baMIPfVypf2IugmPCS9+P2dl44YVlVuoyqqunVWvjZGA== =jVp/ -----END PGP SIGNATURE----- From ammistpaul at googlemail.com Wed Oct 28 10:15:54 2009 From: ammistpaul at googlemail.com (Ammi St. Paul) Date: Wed, 28 Oct 2009 18:15:54 +0100 Subject: [Enigmail] secret key question Message-ID: <4AE87C4A.2050106@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have exchanged keys with someone. They have sent me an encrypted message. I get: Error - secret key needed to decrypt message; click on 'Details' button for more information when I try to decrypt. I have looked through the info I can find and I am still confused about what process I take it exchange my key. In Thunderbird in a mac do I 'attach public key' from the openpgp menu? or do I Export keys to text file from key manager? Thank you. Ammi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJK6HxHAAoJEBfjPqcJXhKmriUH/0lZVKtgE1HM0tlFKgiMB2aa 3nSYprJbJBjbDertyHpRL/2mLq7nw0QEYiXoGhF7splEpUCqvTb5ykp+SEe0bQjD rTLQhCPKjJLZcfCqqwMmPnEh2aQ52bPBhi4riNHQf3w67X0p1umJxf0Hu867Iud8 EOzmrxV3X2S1YbPbi6KuhwLt4VSjoOclf830WY/W4h6BksiWcWe99GtunqTy2L0P wKUPWtnd3gUjI3dt2ebKP98Ds854U7etSW49FUK104wAhlh+WAJuTD7o1FuqiQZg oy1b5T1RLUjGpI88tuQdCv6A8TPAcRYPvUHLHX+/YP12Ntdoy7fhULWq33ws8FM= =tGXE -----END PGP SIGNATURE----- From shavital at mac.com Wed Oct 28 10:30:02 2009 From: shavital at mac.com (Charly Avital) Date: Wed, 28 Oct 2009 13:30:02 -0400 Subject: [Enigmail] secret key question In-Reply-To: <4AE87C4A.2050106@gmail.com> References: <4AE87C4A.2050106@gmail.com> Message-ID: <4AE87F9A.3030903@mac.com> Ammi St. Paul wrote the following on 10/28/09 1:15 PM: > Hi, Hi, verification of your signed e-mail: Good signature from Ammi St. Paul Key ID: 0x095E12A6 / Signed on: 10/28/09 1:15 PM Key fingerprint: F85C DBDE 0B86 3DE8 D094 3ED0 17E3 3EA7 095E 12A6 In my system, when I tried to verify your signed e-mail, Enigmail searched the keyserver set in OpenPGP Preferences, and after finding your key, it downloaded it, imported it in my public keyring, and checked your signature. > I have exchanged keys with someone. They have sent me an encrypted message. > > I get: Error - secret key needed to decrypt message; click on 'Details' > button for more information > > when I try to decrypt. The message you have received has not been encrypted with *your* public key. The sender of that message used (probably) his/her own public key only, without adding your public key. Your public key is used to encrypt messages addressed to you. You need your secret key to decrypt those messages. > > I have looked through the info I can find and I am still confused about > what process I take it exchange my key. > > In Thunderbird in a mac do I 'attach public key' from the openpgp menu? If you want to attach *your* public key, you should use the option: OpenPGP/Attach My Public Key. If you use the option OpenPGP/Attach Public Key..., you will be take to a list of the public keys included in your public keyring, so that you can select the public key you want to send to your correspondent. As I indicated above, your public key 0x095E12A6 can be found in the keyservers. > > or do I > > Export keys to text file from key manager? This is possible, but unnecessary, when the required public key is already in your keyring. If you already Charly MacOSX 10.6.1 32bits MacBook5,1 - 0xA57A8EFA Gnupg 1.4.10 - MacGPG2 2.0.13 - Running Enigmail version 0.97b (20091027-0956) From rasmith1959 at gmail.com Wed Oct 28 10:35:10 2009 From: rasmith1959 at gmail.com (Roy Smith) Date: Wed, 28 Oct 2009 12:35:10 -0500 Subject: [Enigmail] secret key question In-Reply-To: References: Message-ID: Ammi St. Paul wrote: > Hi, > > I have exchanged keys with someone. They have sent me an encrypted message. > > I get: Error - secret key needed to decrypt message; click on 'Details' > button for more information > > when I try to decrypt. > > I have looked through the info I can find and I am still confused about > what process I take it exchange my key. > > In Thunderbird in a mac do I 'attach public key' from the openpgp menu? > > or do I > > Export keys to text file from key manager? The attach public key is just an automated way of extracting your public key, opening the compose window and attaching the public key to the email. Though from the way things sound, you've already sent your public key to your friend and they have created a encrypted message. Now have you imported their public key to your keyring? Until you do that you will not be able to decrypt their messages. If your friend has sent you their public key as an email attachment then importing it is easy. Just view their email that has the attached key, then click on OpenPGP - Decrypt/Verify and Enigmail will ask if you want to import the attached key. Click on yes/ok and you're done. Now you should be able to decrypt your friends message once you've completed this step. -- Roy Smith Windows XP Pro SP3 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 897 bytes Desc: OpenPGP digital signature URL: From beer at cptcnc.de Tue Oct 27 23:19:08 2009 From: beer at cptcnc.de (Beer) Date: Wed, 28 Oct 2009 07:19:08 +0100 Subject: [Enigmail] sign emails Message-ID: <4AE7E25C.1020506@cptcnc.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello John, I'm from Germany. Sorry for my mistakes in Grammar and Orthography. I have sometime trouble with my key. When I sign a mail and the email is in the file "sended" it shows an error at the key. The key wouldn't be correct. In the OpenPGP information I can see, that the has no "0X". If I send the email again, it works. What can be the mistake? Thanks for your help. Ronny -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJK5+JbAAoJEHDE40TtmnAFTOkH/1NzPoU4LMcpK8VAtXHfale7 /gFAkuyK5DwJSPKoKtpEfdOzL8R5QaeeK5lckF6P46GifdsRwXRh1A5f3SmeQ7z+ WZw5fmthPtTZBGBHazOYk6cs1Go8CyfFL4aU8TrYGZilgKaxBdU9bxEC5IuQEbEe l0g6/sCEREHLhmHJVXBscmNNaFAEnthYjlmecRRe00AdOesniNRRUdF0FBju81F4 hy6p2UcyM7XUQEGxSM3llwmtRXV9Pzse+GenEKGQsjx8U4BeYIj5+F0cIW+3t9+O QXt6YfstR/OfQfzyUtub15Ms3KvWipiUpCKolgorksIo2iXsq4W7eUXBhUr2NJI= =grw7 -----END PGP SIGNATURE----- From rjh at sixdemonbag.org Wed Oct 28 12:20:40 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Wed, 28 Oct 2009 15:20:40 -0400 Subject: [Enigmail] sign emails In-Reply-To: <4AE7E25C.1020506@cptcnc.de> References: <4AE7E25C.1020506@cptcnc.de> Message-ID: <4AE89988.4000301@sixdemonbag.org> Beer wrote: > Hello John, Guten tag, Beer! Vielleicht du sollst mit Olav und/oder Patrick sprechen? Patrick aus der Schweiz, und Olav ist Deutscher. Sie k?nnten gibt dir ein Antwort im Deutch, ich denke. === English, for the list: Hello, Beer! Perhaps you should speak with Olav and/or Patrick? Patrick's Swiss, and Olav's German. They can give you an answer in German, I think. From cai.0407 at gmail.com Wed Oct 28 18:50:39 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Thu, 29 Oct 2009 10:50:39 +0900 Subject: [Enigmail] Enigmail and SeaMonkey 2.0 In-Reply-To: <4AE80257.70801@mozilla-enigmail.org> References: <4AE727F7.2020202@mozilla-enigmail.org> <4AE7A6DA.8040401@gmail.com> <4AE80257.70801@mozilla-enigmail.org> Message-ID: <4AE8F4EF.3000500@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2009/10/28 17:35, Patrick Brunschwig wrote: > Kosuke Kaizuka wrote: >> Hi, Patrick > >> On Wed Oct 28 2009 01:51:13 GMT+0900, Cai wrote: >>> There is no finaly version of Enigmail for SeaMonkey 2.0 available yet, >>> however I'm planning to release a new version soon (latest when >>> Thunderbird 3.0 will be released). The reason for this is that I still >>> want to fix some recently discovered bugs in Enigmail. > >> When will UI string be frozen for 0.97? > > As soon as you'll get an email ;-) Okay, I'll wait :-) - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJK6PTuAAoJEFI91dNOjkjZX70P/ig1r3mLHaVg2HMSogtLVLOk 5SmzrsF5h3ptwG4i+t1kR5df3Q869gKtNKHa9Ck5GCvzBSoOlZjFw7Z7DcQOMnIj NrHEVWZHOU7Qb4/kEs+JJ7ESbY5HE90YDvgBh3xfyhxENFFeE+FhmOd2wm22knGe 2iD1GFRd4EBmmMKqvpvhDXS/5imRG0mnrkwvlS29t8sws4l+BUlIG7r2qcVpUUOV n4VAI9ppu5hMP5CPJommNHDNwPDPweMQ1L/DtNvecj3Swo/12RDx4hTP9lEsOkus VcBQgkNgJk2xr6MdtNn1BfqacEuDDmZWXmnoceV9Bpu8MzeTH9GkQWGQ3JX8lVnh XqptE7nn2P3QxDHK7t0fAo5wohGSX9oki2L7fTqy+9OowlkZ/slJoAgaX7XGmTZE zUoUAkdigrPJUqXE7q44eUvECcWZjo0rxPgBzxW6OFvyCCvQCSaJLBqbb7CEqpn6 Ekn3pOWUioLczTsl9gDB0Hh7zDVaZoL/pFPOH/ks63Nzek6Lnb/YKa9Kmuqpki1x x99BjsLZsldimvDuf2URMNT40f7MWoItQQs+UJF1/GCiYJ+EEIxDMsjh1ZlMPkib mVX7NyIAQkhg4Uh9UzXuwk8DaUkQFT/EDGT+qN9hb7Baa3/Rd1C+6kixndxtK146 7fkLxOdWGfYu8OfoF4WH =57+P -----END PGP SIGNATURE----- From dan at mozilla-enigmail.org Thu Oct 29 03:47:13 2009 From: dan at mozilla-enigmail.org (Daniele Raffo) Date: Thu, 29 Oct 2009 11:47:13 +0100 Subject: [Enigmail] secret key question In-Reply-To: References: Message-ID: Roy Smith wrote: > Now have you imported their public key to your keyring? Until you do > that you will not be able to decrypt their messages. > > If your friend has sent you their public key as an email attachment then > importing it is easy. Just view their email that has the attached key, > then click on OpenPGP - Decrypt/Verify and Enigmail will ask if you want > to import the attached key. Click on yes/ok and you're done. Now you > should be able to decrypt your friends message once you've completed > this step. This is wrong. You don't need someone else's public key to decrypt messages sent from him to you. You need this to verify his signature instead. The *sender* is the only actor in the process who can decide whether you'll be able or not to decrypt a message sent from him. He does this by encrypting the message with one or more public key(s): if you own the companion secret key of a public key used to encrypt, you'll be able to read the message. (Obviously, he's supposed to use the public key of the intended recipient.) -- Dan From ayush.cena at gmail.com Thu Oct 29 05:02:41 2009 From: ayush.cena at gmail.com (ayush sharma) Date: Thu, 29 Oct 2009 13:02:41 +0100 Subject: [Enigmail] sign emails In-Reply-To: <4AE89988.4000301@sixdemonbag.org> References: <4AE7E25C.1020506@cptcnc.de> <4AE89988.4000301@sixdemonbag.org> Message-ID: Nice German Robert! Besides the placement of the verb (I goof up with that on a regular basis), your German rocks! ;) 2009/10/28 Robert J. Hansen > Beer wrote: > > Hello John, > > Guten tag, Beer! Vielleicht du sollst mit Olav und/oder Patrick > sprechen? Patrick aus der Schweiz, und Olav ist Deutscher. Sie k?nnten > gibt dir ein Antwort im Deutch, ich denke. > > === > > English, for the list: > > Hello, Beer! Perhaps you should speak with Olav and/or Patrick? > Patrick's Swiss, and Olav's German. They can give you an answer in > German, I think. > > > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkg at fifthhorseman.net Thu Oct 29 13:52:19 2009 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Thu, 29 Oct 2009 16:52:19 -0400 Subject: [Enigmail] dealing with large messages over IMAP Message-ID: <4AEA0083.6010005@fifthhorseman.net> hey enigmail folks-- i'm an IMAP user. while the vast majority of my communications in IMAP are reasonable, there are a few people or machines who unavoidably send me large mails -- usually with large attachments, encrypted to my OpenPGP key. Enigmail can't seem to decrypt these larger e-mails directly via IMAP (this appears to be true against two different IMAP servers i regularly connect to, BINC imapd and dovecot -- i haven't tested others). My current workaround is to move the offending messages to a special subfolder in thunderbird's (well, icedove's really) "Local Folders", and let enigmail work from there. I'd rather not have to do that, though. The folders in my various IMAP boxes are the right place for the messages, and it's a clunky workaround at best. Is this a fundamental limitation, or is it a bug that might be fixable? should i file a ticket about it? a search on https://www.mozdev.org/bugs didn't turn up anything relevant that i could see. Thanks for all the work on enigmail, --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 891 bytes Desc: OpenPGP digital signature URL: From Andreas.Fenner at thalesgroup.com Thu Oct 29 22:50:11 2009 From: Andreas.Fenner at thalesgroup.com (Andreas Fenner) Date: Fri, 30 Oct 2009 06:50:11 +0100 Subject: [Enigmail] dealing with large messages over IMAP In-Reply-To: <4AEA0083.6010005@fifthhorseman.net> References: <4AEA0083.6010005@fifthhorseman.net> Message-ID: <4AEA7E93.5070907@thalesgroup.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Daniel, have you tried to disable the "Only download attachments when opened" button in the Advanced Preferences tab? Best regards / Mit freundlichen Gr??en, Andreas Fenner - -- - ---------------------------------------+------------------------------- Thales Rail Signalling Solutions GmbH | Dept. TS/ESP-2 | Lorenzstrasse 10 | phone: +49 711 869-49823 D-70435 Stuttgart | fax: +49 711 869-46598 - ---------------------------------------+------------------------------- Sitz der Gesellschaft/Domicile of the Company: Stuttgart Amtsgericht/District Court: Stuttgart HRB 720908 Gesch?ftsf?hrer/Managing Directors: Hans Leibbrand (Vorsitzender/Chairman), Manfred Riedinger - ----------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrqfpMACgkQmxsLTgRoLtxeWgCdH5KA+YSuJVqp7nApnM8XlMoA zsoAoPgrZ+R8lOwn8j2qceZDIePlRgho =fZ8P -----END PGP SIGNATURE----- From dkg at fifthhorseman.net Thu Oct 29 23:13:20 2009 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Fri, 30 Oct 2009 02:13:20 -0400 Subject: [Enigmail] dealing with large messages over IMAP In-Reply-To: <4AEA7E93.5070907@thalesgroup.com> References: <4AEA0083.6010005@fifthhorseman.net> <4AEA7E93.5070907@thalesgroup.com> Message-ID: <4AEA8400.2010105@fifthhorseman.net> On 10/30/2009 01:50 AM, Andreas Fenner wrote: > have you tried to disable the "Only download attachments when opened" > button in the Advanced Preferences tab? Hey, that works, thanks! If i have "only download attachments when opened (IMAP only)" unchecked, then i can view these larger e-mails directly from the IMAP server (both BINC and dovecot). Thank you, Andreas! Now if only i could understand *why* that makes a difference; i don't think i understand what that checkbox means. Can someone try explaining it to me in more detail? Why would it cause a decryption failure if the box was checked? --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 891 bytes Desc: OpenPGP digital signature URL: From patrick at mozilla-enigmail.org Fri Oct 30 00:54:45 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 30 Oct 2009 08:54:45 +0100 Subject: [Enigmail] dealing with large messages over IMAP In-Reply-To: <4AEA8400.2010105@fifthhorseman.net> References: <4AEA0083.6010005@fifthhorseman.net> <4AEA7E93.5070907@thalesgroup.com> <4AEA8400.2010105@fifthhorseman.net> Message-ID: <4AEA9BC5.9000804@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Daniel Kahn Gillmor wrote: > On 10/30/2009 01:50 AM, Andreas Fenner wrote: > >> have you tried to disable the "Only download attachments when opened" >> button in the Advanced Preferences tab? > > Hey, that works, thanks! If i have "only download attachments when > opened (IMAP only)" unchecked, then i can view these larger e-mails > directly from the IMAP server (both BINC and dovecot). Thank you, Andreas! > > Now if only i could understand *why* that makes a difference; i don't > think i understand what that checkbox means. Can someone try explaining > it to me in more detail? > > Why would it cause a decryption failure if the box was checked? By default Thunderbird 2 makes use of an IMAP feature: download attachments to a message only when requested. Thus TB will only download the first ca. 40 kB of a message. But this way, the end of the message will be missing for larger messages, leading to simply fail Enigmail (there is no way Enigmail could recover at the moment this happens). With option above you change TB's behavior to always download the complete message at once. - -Patrick PS. TB 3 will by default download all messages in order to index them; this way this shouldn't be a problem either. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSuqbxHcOpHodsOiwAQjmIgf+M/4CX2v20IHCQGFr9lt8sWQrdTRi+x0H DOVf+4GXEjj/1FqXYaogD4aCYnmnkJDo1B7t59N1uAFvCwICcK6cXB9tfZjyAqXb nQB6m2ScCcZCHUsZi+TDIhViOh0B+GOW9ogP2/hvy1o6dgQcydxrI5jcl7wsTfcs 6v0wuRsTrpEOUkeehCV+iepMlh9lnaAY97AG2dMJ4a43uXrzf8h1p39vSL1Yw8K6 Ln5CmeoWzWSEzKOLj3J/24lLLJA3F9WnzmjYcbVnPPxYnWs9SyOrkzWGZagn9WXn NGk9wgD28jmiiraltNY65a+q+Nc+JZ20m4LQOYpSg9GodhlPHgr4fg== =ZDD1 -----END PGP SIGNATURE----- From dkg at fifthhorseman.net Fri Oct 30 07:33:01 2009 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Fri, 30 Oct 2009 10:33:01 -0400 Subject: [Enigmail] dealing with large messages over IMAP In-Reply-To: <4AEA9BC5.9000804@mozilla-enigmail.org> References: <4AEA0083.6010005@fifthhorseman.net> <4AEA7E93.5070907@thalesgroup.com> <4AEA8400.2010105@fifthhorseman.net> <4AEA9BC5.9000804@mozilla-enigmail.org> Message-ID: <4AEAF91D.1090906@fifthhorseman.net> On 10/30/2009 03:54 AM, Patrick Brunschwig wrote: > Daniel Kahn Gillmor wrote: >> Why would it cause a decryption failure if the box was checked? > > By default Thunderbird 2 makes use of an IMAP feature: download > attachments to a message only when requested. Thus TB will only download > the first ca. 40 kB of a message. But this way, the end of the message > will be missing for larger messages, leading to simply fail Enigmail > (there is no way Enigmail could recover at the moment this happens). > > With option above you change TB's behavior to always download the > complete message at once. gotcha, this makes sense now. Thanks for the explanation, Patrick. Yet another reason to look forward to TB3! Regards, --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 891 bytes Desc: OpenPGP digital signature URL: From bijan at psq.com Fri Oct 30 12:02:18 2009 From: bijan at psq.com (Bijan Soleymani) Date: Fri, 30 Oct 2009 15:02:18 -0400 Subject: [Enigmail] Encrypted received message on imap server Message-ID: Hi, I would like the ability to encrypt messages sitting on my IMAP server. I realize that this isn't really that much of a protection as the message has already traveled unencrypted through the internet, etc. But it would still protect against my IMAP server or my IMAP account being compromised. Anyways I couldn't figure out how to do this. Is there a button or option that I am missing? Also I found a post to this list from 2004 entitled: "Feature Request: Encrypt received messages to self (e.g. on IMAP server)" And it seems the only way to do that was to edit the message and then save it as a draft. But ideally I'd like just a button to click, or a key to press. It seems like an easy thing to do, so I don't mind coding the feature. Thanks in advance, Bijan From rjh at sixdemonbag.org Fri Oct 30 14:56:27 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Fri, 30 Oct 2009 17:56:27 -0400 Subject: [Enigmail] Encrypted received message on imap server In-Reply-To: References: Message-ID: <4AEB610B.6070605@sixdemonbag.org> Bijan Soleymani wrote: > Anyways I couldn't figure out how to do this. Is there a button or > option that I am missing? It is not possible to do this. > It seems like an easy thing to do, so I don't mind coding the > feature. If you want to write the patch, feel free. However, as a word of warning, it will involve a /lot/ of work. You'll have to patch Thunderbird to support arbitrary manipulations of stored messages, possibly patch the IMAP protocol to support message manipulation, get those patches accepted at Thunderbird and the IETF, and only then can you work on introducing this to Enigmail. It's a big can of worms, made even worse by the fact TB3 is coming out really soon and will totally change Thunderbird's internals. If we were to do this in a way that works with TB2, we would probably have to totally rewrite it to work with TB3. From bijan at psq.com Fri Oct 30 17:42:32 2009 From: bijan at psq.com (Bijan Soleymani) Date: Fri, 30 Oct 2009 20:42:32 -0400 Subject: [Enigmail] Encrypted received message on imap server In-Reply-To: References: Message-ID: Robert J. Hansen wrote: > Bijan Soleymani wrote: >> Anyways I couldn't figure out how to do this. Is there a button or >> option that I am missing? > > It is not possible to do this. Oh well... Too bad. Thanks for letting me know. I was thinking that it was simple so I had to be missing something. >> It seems like an easy thing to do, so I don't mind coding the >> feature. > > If you want to write the patch, feel free. However, as a word of > warning, it will involve a /lot/ of work. You'll have to patch > Thunderbird to support arbitrary manipulations of stored messages, > possibly patch the IMAP protocol to support message manipulation, get > those patches accepted at Thunderbird and the IETF, and only then can > you work on introducing this to Enigmail. > > It's a big can of worms, made even worse by the fact TB3 is coming out > really soon and will totally change Thunderbird's internals. If we were > to do this in a way that works with TB2, we would probably have to > totally rewrite it to work with TB3. I don't mind writing it. It seems not impossible to do. If Thunderbird can move a message from one IMAP server to another, that is: download a message from server1, and add it to server2, it should be able to download a message from server1 and add an encrypted copy to server1. It is clear that in the case of moving from server1 to server2 Thunderbird has to transmit the contents of the message to server2, and Thunderbird could probably send it anything it wants (not necessarily identical to the original message)... It's ok if Thunderbird doesn't manipulate the message in place. It is fine for me if it creates a new encrypted message which is identical to the original except for being encrypted and then deletes the original. Anyways I will look into it. Thanks again, Bijan From bijan at psq.ocm Fri Oct 30 22:23:37 2009 From: bijan at psq.ocm (Bijan Soleymani) Date: Sat, 31 Oct 2009 01:23:37 -0400 Subject: [Enigmail] Encrypted received message on imap server In-Reply-To: References: Message-ID: Bijan Soleymani wrote: > Robert J. Hansen wrote: >> Bijan Soleymani wrote: >>> It seems like an easy thing to do, so I don't mind coding the >>> feature. >> If you want to write the patch, feel free. However, as a word of >> warning, it will involve a /lot/ of work. You'll have to patch >> Thunderbird to support arbitrary manipulations of stored messages, >> possibly patch the IMAP protocol to support message manipulation, get >> those patches accepted at Thunderbird and the IETF, and only then can >> you work on introducing this to Enigmail. >> >> It's a big can of worms, made even worse by the fact TB3 is coming out >> really soon and will totally change Thunderbird's internals. If we were >> to do this in a way that works with TB2, we would probably have to >> totally rewrite it to work with TB3. > > I don't mind writing it. It seems not impossible to do. If Thunderbird > can move a message from one IMAP server to another, that is: download a > message from server1, and add it to server2, it should be able to > download a message from server1 and add an encrypted copy to server1. It > is clear that in the case of moving from server1 to server2 Thunderbird > has to transmit the contents of the message to server2, and Thunderbird > could probably send it anything it wants (not necessarily identical to > the original message)... > > It's ok if Thunderbird doesn't manipulate the message in place. It is > fine for me if it creates a new encrypted message which is identical to > the original except for being encrypted and then deletes the original. There is a command in the IMAP protocol called APPEND which basically tells the IMAP server to store a message in a folder. Its syntax is something like: APPEND (flags) "DATE" {size} Message Line 1 Message Line 2 ... ... ... So when I move a mail from Gmail to my personal IMAP server Thunderbird does the following: connect to gmail imap connect to personal imap fetch message from gmail append message to personal But it is possible to simply connect to personal and run the append command directly. There appears to be a function called appendmsgfromfile in thunderbird. I think this is the javascript interface, and the actual function is something like nsImapAppendMsgFromFile. I can't find the c++ source for this function so I'm not sure it does what I want. But I'm hoping I can download the message, encrypt it, put it in a file, and call that function to upload the file to the server. Bijan From Nomis101 at web.de Sat Oct 31 10:28:33 2009 From: Nomis101 at web.de (Nomis101 at web.de) Date: Sat, 31 Oct 2009 18:28:33 +0100 Subject: [Enigmail] How to build enigmail (0.97a) on Mac OS X? Message-ID: <1035983541@web.de> Hi enigmail list, I build my own Thunderbird for a few years now. I also want to build my own localized version of Enigmail, but I'm not able to get this to work. It doesn't compile. :( On the web I found this version of a german localized version of enigmail for Thunderbird 3: http://www.thunderbird-mail.de/wiki/Enigmail_OpenPGP How can I build a (german) version like this for TB3 on Mac OS X? I've tried anything, but with no success. Hope anybody can help me with this. Regards, Simon PS: I'm at the moment on Mac OS X 10.6.1 _______________________________________________________________ Neu: WEB.DE DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://produkte.web.de/go/02/ From mlisten at hammernoch.net Sat Oct 31 10:41:36 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Sat, 31 Oct 2009 18:41:36 +0100 Subject: [Enigmail] How to build enigmail (0.97a) on Mac OS X? In-Reply-To: <1035983541@web.de> References: <1035983541@web.de> Message-ID: <4AEC76D0.8020109@hammernoch.net> Hi Simon, Nomis101 at web.de wrote on 31.10.09 18:28: > Hi enigmail list, > > I build my own Thunderbird for a few years now. I also want to build > my own localized version of Enigmail, but I'm not able to get this to > work. It doesn't compile. :( On the web I found this version of a > german localized version of enigmail for Thunderbird 3: > http://www.thunderbird-mail.de/wiki/Enigmail_OpenPGP How can I build > a (german) version like this for TB3 on Mac OS X? I've tried > anything, but with no success. Hope anybody can help me with this. > > Regards, Simon > > > PS: I'm at the moment on Mac OS X 10.6.1 I'm the one who contributes the enigmail nightly for Mac OS X. Right now, I'm building on 10.5.8 using an adapted script originally supplied by Patrick, who is building the Linux and Windows versions. How can I help you? Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From cai.0407 at gmail.com Sat Oct 31 19:43:21 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Sun, 01 Nov 2009 11:43:21 +0900 Subject: [Enigmail] How to build enigmail (0.97a) on Mac OS X? In-Reply-To: <1035983541@web.de> References: <1035983541@web.de> Message-ID: <4AECF5C9.9020907@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Simon, I'm the localizer for ja-JP. Did you try "Translate Enigmail to a new language" in http://enigmail.mozdev.org/download/langpack.php ? Or other way? In another way, you can add other language resources to existing Enigmail nightly binary without build, just unzip/zip because xpi file is zip archive. 1. Prepare language resources (enigmail.dtd, .properties etc.). 2. Zip language resources and name it enigmail-locale.jar. 3. Unzip enigmail xpi file. 4. Add enigmail-locale.jar to chrome/ (same as enigmail.jar and enigmail-skin.jar). 5. Add a line "locale enigmail jar:chrome/enigmail-locale.jar!/locale//enigmail/" to chrome.manifest. 6. Zip and name it *.xpi. I made ja-JP including version in same way. http://www.chaoticshore.org/moz/Enigmail/enigmail-trunk-tb-win32-trunk-20091026-ja-JP.xpi Some UI strings have been added to nightly since 0.96 release. You will have to add these strings to your locale. Regards, Kosuke On 2009/11/01 02:28, Nomis101 at web.de wrote: > Hi enigmail list, > > I build my own Thunderbird for a few years now. I also want to build my own localized version of Enigmail, but I'm not able to get this to work. It doesn't compile. :( On the web I found this version of a german localized version of enigmail for Thunderbird 3: http://www.thunderbird-mail.de/wiki/Enigmail_OpenPGP > How can I build a (german) version like this for TB3 on Mac OS X? I've tried anything, but with no success. Hope anybody can help me with this. > > Regards, > Simon > > > PS: I'm at the moment on Mac OS X 10.6.1 > _______________________________________________________________ > Neu: WEB.DE DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! > http://produkte.web.de/go/02/ > > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJK7PXJAAoJEFI91dNOjkjZ8zQP/j7OaBel68/JguuxkXDKxC+P LVWw51clgDi1y7wjZ0c4ni1rKSkTY9fYyZSXb/HdUwVhkyNKQdoM+bretZs0GytO k309ByG3lEujXvDZB/WzSPgUOLLQaHPFBOB9UnpXvoVq6v4yAD4YASNYr2pFX2F0 XrQMIeE5id/SvCJRDzaScPYywiiW2EgplNrSmqhc5UBnPqmF9RroFOx5G8mhVuXQ dyfYTf1juAdmc0gs86nTyJ3fEMMa5q5RRcVC/OCIXMZZJmXrB0WjNQboEBuZCTx1 9px8OKUEmztKkHxgRjEc2UePGMJx/hOxwLg58wbgbsBQjthwJx73PIpH5dHC6rTM uStDoR83AqYNwHIogksODvbVjghLF6s2kB/TscSRCopWgTSS/1HE963vIKlAI90N LR6fSehzEBq5+AOv8FSkUeXGCbJV55Tx+smUyjRdb6jkPojZtM8fNdLfQin2eq+K E1ty9u2qh+LTLWARkHoA3s10mk6oant9wMeOFzCNEIp7oDCOvs/keuQQ3d0ik8B7 yi2irl8P3B/7XBapSaxD3HC5aZATh6NNU4WhfpzCEPt5FdLdmcOqpcpTmpTF4QyL xk5HqqwPrPpS2Lj/jkkzRbH1QMbK9P5ymIn4IlY3T8VtrT151ukRVyMuOOJSUGWc 3EIS0hBPzbBiFBjFRKNw =K3FZ -----END PGP SIGNATURE-----