[Enigmail] Enigmail Digest, Vol 60, Issue 20
Michael Hofrichter
omnil at gmx.de
Tue Jun 17 14:58:09 PDT 2008
i am installing linux debian at the moment there is not much time for me but i got a good clock
-------- Original-Nachricht --------
> Datum: Mon, 16 Jun 2008 07:34:12 -0700
> Von: enigmail-request at mozdev.org
> An: enigmail at mozdev.org
> Betreff: Enigmail Digest, Vol 60, Issue 20
> Send Enigmail mailing list submissions to
> enigmail at mozdev.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.mozdev.org/mailman/listinfo/enigmail
> or, via email, send a message with subject or body 'help' to
> enigmail-request at mozdev.org
>
> You can reach the person managing the list at
> enigmail-owner at mozdev.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Enigmail digest..."
>
>
> Today's Topics:
>
> 1. forwarding S/MIME encrypted email failed (Stefan X)
> 2. Re: forwarding S/MIME encrypted email failed (Alexander Dahl)
> 3. Re: forwarding S/MIME encrypted email failed (Patrick Brunschwig)
> 4. Re: Configuring default Key Selection (Simon Lowen)
> 5. Re: Development question about MIME format (otrmail02 otrmail)
> 6. Re: Configuring default Key Selection (Faramir)
> 7. Re: Configuring default Key Selection (Phil Stracchino)
> 8. Re: Development question about MIME format (Patrick Brunschwig)
> 9. Re: forwarding S/MIME encrypted email failed (Stefan X)
> 10. Re: Configuring default Key Selection (Robert J. Hansen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 16 Jun 2008 00:21:36 +0200
> From: Stefan X <stefanxe at gmx.net>
> Subject: [Enigmail] forwarding S/MIME encrypted email failed
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <485595F0.2070208 at gmx.net>
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>
> I received a S/MIME encrypted email (which I could not decrypt because I
> did not have the required certificate and did not used S/MIME at all).
> Thunderbird failed to simply forward this email to another recipient
> with the error message "pgpMime.sMime.incompatible". For the receiver
> rules are in Enigmail defined to send all emails encrypted. I also tried
> to send the forwarded email unencrypted but failed with an error message
> explaining me that Thunderbird can not find the defined encryption
> certificate or the certificate is expired. What to do?
>
> Stefan
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 16 Jun 2008 07:42:27 +0200
> From: Alexander Dahl <post at lespocky.de>
> Subject: Re: [Enigmail] forwarding S/MIME encrypted email failed
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <0MKwtQ-1K87UR0rfT-0004B4 at mrelayeu.kundenserver.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Stefan,
>
> > certificate or the certificate is expired. What to do?
>
> Did you try to bounce/redirect the message? You can use the following
> extension for that: http://mailredirect.mozdev.org/
>
> Greets
> Alex
>
> --
> ***** http://www.lespocky.de *******************************************
> Those who would give up essential Liberty, to purchase
> a little temporary Safety, deserve neither Liberty nor Safety.
> (Benjamin Franklin)
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 258 bytes
> Desc: OpenPGP digital signature
> Url :
> http://www.mozdev.org/pipermail/enigmail/attachments/20080616/b2a04a92/attachment-0001.bin
>
> ------------------------------
>
> Message: 3
> Date: Mon, 16 Jun 2008 08:28:03 +0200
> From: Patrick Brunschwig <patrick at mozilla-enigmail.org>
> Subject: Re: [Enigmail] forwarding S/MIME encrypted email failed
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <485607F3.9090804 at mozilla-enigmail.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stefan X wrote:
> > I received a S/MIME encrypted email (which I could not decrypt because I
> > did not have the required certificate and did not used S/MIME at all).
> > Thunderbird failed to simply forward this email to another recipient
> > with the error message "pgpMime.sMime.incompatible". For the receiver
> > rules are in Enigmail defined to send all emails encrypted. I also tried
> > to send the forwarded email unencrypted but failed with an error message
> > explaining me that Thunderbird can not find the defined encryption
> > certificate or the certificate is expired. What to do?
>
> Forward the email as attachment and activate the option OpenPGP > Ignore
> per-recipient rules.
>
> - -Patrick
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEVAwUBSFYH83cOpHodsOiwAQKU/ggAwBp6VZMLB0HQ2zWrbKcuNwGoXVRJqIJ9
> AjWJ954OgDlrEnpF90E1K8dFqDUcNjUyPsKBNcF0GmR/JuWv0AJBsar9pCT19MFJ
> CvQW5naHw1q+ggLiaNSXsPn5vyM8AexyYv+8vFNnu6WsnadxcyTNiG/HJmsnoF33
> XCZh3evBsHCfrsY7gi8kapF7f8FvPmlL9de8boU03GijIvcLGbvui+Ggs7xWYlnk
> WaedXMXTdYOlVm22IWItCQDpSO/fpWZhLCKm1YnSUlhxsCWtwIvwmFHea8+66uqA
> LDAP0UzIJNYIMGuk88ftpsjBTf2qdOrrWGlvpoPRumdEY7TQ0wMvXQ==
> =d8pU
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 16 Jun 2008 10:58:15 +0200
> From: Simon Lowen <simon at simonloewen.com>
> Subject: Re: [Enigmail] Configuring default Key Selection
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <48562B27.3030004 at simonloewen.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Dear all,
>
> I have tried to configure my other half's Enigmail to automatically
> encryt and decypt emails. With help from this mailing list I have got
> this working.
>
> I have a question:
>
> When she sends her email it adds a very large signature to the bottom of
> it. I am concerned because my signature on my email (and others) only
> occupies 2 or 3 lines, while her signature is 13 lines !! My concern
> is that the private key is being sent as well. If this is not the case,
> then please would someone explain to me why her public key is so large.
> There is no passphase. The key is not uploaded to a public key server.
>
> Regards, S.
>
>
> Below is my signature and then her sig for comparision.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIVinXKTaqpMPqlXYRCvd/AJ9fZQAubr1Ojfvx/62Gbe81u1XaKgCgjkf+
> ha0faJJUr9dyCeZHp6vWvLA=
> =rt/D
> -----END PGP SIGNATURE-----
>
>
>
> And here is hers:
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iQIVAwUBSFYo3mylYaeiCjbPAQIThA/+OLEEx1VikARDxUjHlL0rGwcxww1yrJoN
> VyMImxmMKtRT8j9Blsb76qDwMlNrcIROSoXGenUFzzWY9Pg/08fgFAe6F41BHIWe
> zLAy9VemTNfSnSR8ZtdldBLWNO2u6/2FhbKNS42+ZjRBfaiwOXdKgC3PjzV6sXKx
> GYTCVGjT9ZpCvKQUf6ZOE37k4LYMZQROTMedp+8f8TWeo78RSKsWKRGYRgrwtWU4
> SyL3UhsejtB8pv/266xjbKIvrwJOctN3nF7NNN5wxynQtQs9QYLaQMY0V5KUFGnW
> 80efMyCkiaiWYL1WMDqRBVzLi7BxT+zRIo0yVLwaSb9U825gk3PpdFAlzrmxeEN6
> F6x3xvt4os49/hGdBgibINh1HTvvwgImsohlm4sKwLeIWm7pj/k+s/AN0SLIqXBx
> dTTa3oPfFXhfrGuty/Hqdpdgmk3D7oePFgWwTlesr52cefWFpwt4M0clwz/+XuVU
> di/vAM51f5HXiSZie/XkISesXBmnJkZcHg0ISjEC+NxaDVRRG4nf32dcalGAirI2
> 5c1trpRFP+KtnPzCD7ieNBlSklHlWm6PyzR+bjtodUQgAcHXBxfSYAH3tVsG1I41
> pdG097aCcLxlfY+W46CsDXP+gb28C2nJkuucfaq/OIFbm5M3Rp1OY8BOTyqRbWRA
> J6q/SDo3GQg=
> =8Hn/
> -----END PGP SIGNATURE-----
>
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 16 Jun 2008 17:09:37 +0800
> From: "otrmail02 otrmail" <otrmail02 at gmail.com>
> Subject: Re: [Enigmail] Development question about MIME format
> To: "Enigmail user discussion list" <enigmail at mozdev.org>
> Message-ID:
> <c44d79d70806160209s54319621hcd99856e0a89728e at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> Thanks for reply, Patrick. I have study about the
> enigmailMsgComposeOverlay.js. But i still confuse about how does the
> method
> is invoked automatically. Could you tell me more about it? Or any
> reference
> that i can refer to it. Thanks.
>
> Regards
> Lai
>
> On Thu, Jun 12, 2008 at 8:32 PM, Patrick Brunschwig <
> patrick at mozilla-enigmail.org> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > otrmail02 otrmail wrote:
> > > Hi,
> > >
> > > I am doing an extension for Thunderbird. The extension will send a
> mail
> > > with MIME Security with OpenPGP format (RFC3156).
> > > Understand that enigmail is using a method WriteEncryptedHeaders() in
> > > nsEnigMsgCompose.cpp to write the format. I am wondering how does the
> > > method is called and when is called. Hope any of can answer my
> question.
> > > Thanks in advance.
> > >
> > > regards
> > > Lai
> >
> > You have to register your class in with the component registrar, like
> > it's done in enigmail.js in Enigmail.prototype.initialize(). 1st thing
> > in that method does is to register nsEnigMsgCompose for secure message
> > sending.
> >
> > The methods are automatically invoked if
> > gMsgCompose.compFields.securityInfo is defined and specifies that the
> > message should be encrypted. See enigmailMsgComposeOverlay.js, function
> > enigEncryptMsg().
> >
> > - -Patrick
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.9 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >
> > iQEVAwUBSFEXYncOpHodsOiwAQIW8Af/UpuVH4b6Zzw2HfTkkyCWhPvwxieDhiks
> > ejx0YrX9BVVKXogvi/eCI+sDLNAd4wqDe2pUep6YPaXby91yGGmP7PBIMP1bLFcq
> > ulu9AfMxFlBe9n4zo/CIrDf2XTr6R8XzrFFpa3M92VSsFfywb06cWpeomuBzeTym
> > RyBi40Kd3g8bGlKp8OB5uWCVjYglvHp28C9GorwUqmVWzzBUHrAWVErGPB9R4/Q6
> > 9sNAi9LIu1dtWdi1X4+pJM8IrIf6kOM8FsWBvwjgt2LbeI243zTTWlsGvJC9LgG3
> > LWyFmZDJ83KEJg8b4XSNBmcvJ3npdQNl1p7Cul5coGigcZDKNBDvTA==
> > =KVKO
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > Enigmail mailing list
> > Enigmail at mozdev.org
> > https://www.mozdev.org/mailman/listinfo/enigmail
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://www.mozdev.org/pipermail/enigmail/attachments/20080616/bed74db8/attachment-0001.html
>
> ------------------------------
>
> Message: 6
> Date: Mon, 16 Jun 2008 05:47:21 -0400
> From: Faramir <faramir.cl at gmail.com>
> Subject: Re: [Enigmail] Configuring default Key Selection
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <485636A9.4000807 at gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Simon Lowen escribi?:
> > Dear all,
> >
> > I have tried to configure my other half's Enigmail to
> automatically
> > encryt and decypt emails. With help from this mailing list I
> have got
> > this working.
> >
> > I have a question:
> >
> > When she sends her email it adds a very large signature to the
> bottom of
> > it. I am concerned because my signature on my email (and
> others) only
> > occupies 2 or 3 lines, while her signature is 13 lines !!
> My concern
> > is that the private key is being sent as well. If this is not
> the case,
> > then please would someone explain to me why her public key is
> so large.
> > There is no passphase. The key is not uploaded to a public
> key server.
> >
> > Regards, S.
> >
> >
> > Below is my signature and then her sig for comparision.
>
>
> Are both of you using the same kind of keys? I have read (I am not sure
> if it was in this list, or in gnupg list) RSA signatures are larger than
> DSA signatures, so if you are using a DSA key, and your other half
> is using RSA keys, maybe that would explain the diference.
>
> My signature is 7 lines long, longer than your signature, but shorter
> than her signature... Anyway, Enigmail doesn't have the "attach private
> key" option (at least, not anywhere I can see it), and it would be an
> incredible bug if that was the case... unless she installed a tampered
> version of Enigmail, it is unlikely to happen. Anyway, I suggest she
> should set a passphrase, just in case somebody get access to her
> computer... without a passphrase, it is easy to export the private key,
> or to revoke it...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iQEcBAEBAgAGBQJIVjapAAoJEMV4f6PvczxAw3AH/2hrCID9fncYquQ4vZhKnKk7
> ppb5OON3UJzUMTJIB17HfWBzo1g4B2Y9TeH8th960C09IFDBR18kahLV9IBczhpX
> jggameb9MozvdLbWad53Ry8lbJFVWUajxo7oby4eDPyWQbSm0W8qw3gK2uHKKwdv
> 93nksFHLr/qDa9bt8+k8I7GHdb0vZBladWXrtQh09RSXsz3Er8ZjIow3++/D5e84
> 0yuBmQkDTYbWGGynK9tJYP0ZtrD121CnKUNYKWT7+WS1HvygdIp4PeWViCg7+qkK
> +lzmRfBXTsQhtfdE8kN+ftek4AjK8yemEMFKELSB7FjqHr66D0DOz1CJqi36NsA=
> =rdo7
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 16 Jun 2008 06:27:04 -0400
> From: Phil Stracchino <alaric at metrocast.net>
> Subject: Re: [Enigmail] Configuring default Key Selection
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <48563FF8.4080709 at metrocast.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Simon Lowen wrote:
> > Dear all,
> >
> > I have tried to configure my other half's Enigmail to automatically
> > encryt and decypt emails. With help from this mailing list I have got
> > this working.
> >
> > I have a question:
> >
> > When she sends her email it adds a very large signature to the bottom of
> > it. I am concerned because my signature on my email (and others) only
> > occupies 2 or 3 lines, while her signature is 13 lines !! My concern
> > is that the private key is being sent as well. If this is not the case,
> > then please would someone explain to me why her public key is so large.
> > There is no passphase. The key is not uploaded to a public key server.
> >
> > Regards, S.
> >
> >
> > Below is my signature and then her sig for comparision.
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> >
> > iD8DBQFIVinXKTaqpMPqlXYRCvd/AJ9fZQAubr1Ojfvx/62Gbe81u1XaKgCgjkf+
> > ha0faJJUr9dyCeZHp6vWvLA=
> > =rt/D
> > -----END PGP SIGNATURE-----
> >
> >
> >
> > And here is hers:
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> >
> > iQIVAwUBSFYo3mylYaeiCjbPAQIThA/+OLEEx1VikARDxUjHlL0rGwcxww1yrJoN
> > VyMImxmMKtRT8j9Blsb76qDwMlNrcIROSoXGenUFzzWY9Pg/08fgFAe6F41BHIWe
> > zLAy9VemTNfSnSR8ZtdldBLWNO2u6/2FhbKNS42+ZjRBfaiwOXdKgC3PjzV6sXKx
> > GYTCVGjT9ZpCvKQUf6ZOE37k4LYMZQROTMedp+8f8TWeo78RSKsWKRGYRgrwtWU4
> > SyL3UhsejtB8pv/266xjbKIvrwJOctN3nF7NNN5wxynQtQs9QYLaQMY0V5KUFGnW
> > 80efMyCkiaiWYL1WMDqRBVzLi7BxT+zRIo0yVLwaSb9U825gk3PpdFAlzrmxeEN6
> > F6x3xvt4os49/hGdBgibINh1HTvvwgImsohlm4sKwLeIWm7pj/k+s/AN0SLIqXBx
> > dTTa3oPfFXhfrGuty/Hqdpdgmk3D7oePFgWwTlesr52cefWFpwt4M0clwz/+XuVU
> > di/vAM51f5HXiSZie/XkISesXBmnJkZcHg0ISjEC+NxaDVRRG4nf32dcalGAirI2
> > 5c1trpRFP+KtnPzCD7ieNBlSklHlWm6PyzR+bjtodUQgAcHXBxfSYAH3tVsG1I41
> > pdG097aCcLxlfY+W46CsDXP+gb28C2nJkuucfaq/OIFbm5M3Rp1OY8BOTyqRbWRA
> > J6q/SDo3GQg=
> > =8Hn/
> > -----END PGP SIGNATURE-----
>
>
> The first question that occurs to me is: What type and length are the
> keys being used?
>
>
> - --
> Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
> alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org
> Renaissance Man, Unix ronin, Perl hacker, Free Stater
> It's not the years, it's the mileage.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEAREIAAYFAkhWP/gACgkQ0DfOju+hMknasQCg6XRAmuM4EEI8TNNn8AjbIaXF
> HgcAnjvopfRWICSsB66IhrrnIQLT8t/K
> =Tmfk
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 8
> Date: Mon, 16 Jun 2008 13:43:32 +0200
> From: Patrick Brunschwig <patrick at mozilla-enigmail.org>
> Subject: Re: [Enigmail] Development question about MIME format
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <485651E4.5040106 at mozilla-enigmail.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> There is no at mozilla.org available on this topic :-(
>
> The code is automatically invoked by Mozilla if you set the
> securityInfo. If you want to know more, you'll have to study the Mozilla
> code in mailnews/compose/src, in particular nsMsgSend.cpp and
> nsMsgSendPart.cpp
>
> - -Patrick
>
>
> otrmail02 otrmail wrote:
> > Hi,
> >
> > Thanks for reply, Patrick. I have study about the
> > enigmailMsgComposeOverlay.js. But i still confuse about how does the
> > method is invoked automatically. Could you tell me more about it? Or any
> > reference that i can refer to it. Thanks.
> >
> > Regards
> > Lai
> >
> > On Thu, Jun 12, 2008 at 8:32 PM, Patrick Brunschwig
> > <patrick at mozilla-enigmail.org <mailto:patrick at mozilla-enigmail.org>>
> wrote:
> >
> > otrmail02 otrmail wrote:
> >> Hi,
> >
> >> I am doing an extension for Thunderbird. The extension will send a
> > mail
> >> with MIME Security with OpenPGP format (RFC3156).
> >> Understand that enigmail is using a method WriteEncryptedHeaders() in
> >> nsEnigMsgCompose.cpp to write the format. I am wondering how does the
> >> method is called and when is called. Hope any of can answer my
> > question.
> >> Thanks in advance.
> >
> >> regards
> >> Lai
> >
> > You have to register your class in with the component registrar, like
> > it's done in enigmail.js in Enigmail.prototype.initialize(). 1st thing
> > in that method does is to register nsEnigMsgCompose for secure message
> > sending.
> >
> > The methods are automatically invoked if
> > gMsgCompose.compFields.securityInfo is defined and specifies that the
> > message should be encrypted. See enigmailMsgComposeOverlay.js, function
> > enigEncryptMsg().
> >
> > -Patrick
> >
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org <mailto:Enigmail at mozdev.org>
> https://www.mozdev.org/mailman/listinfo/enigmail
>
> > ------------------------------------------------------------------------
>
> > _______________________________________________
> > Enigmail mailing list
> > Enigmail at mozdev.org
> > https://www.mozdev.org/mailman/listinfo/enigmail
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEVAwUBSFZR43cOpHodsOiwAQLwjwgAiII0Hi85i4iEfqVoR31h5Ge/ANWSQr+3
> fxu/aUW9xMvii+ZDm9Aq82/LkcO6pWa/bQ1ZWIKpaUHQzO9v0S0V+8VUVcCJtNim
> efk7CNmH0jHHuxYx6aVMgiTTwLxq2LHH2xzP+Rgh/UyPnnYO+92bpop3zXgA3rzg
> QM8BDUQ02tafbnCw4vf34l+cYMPq727tly1xBvLARMwNNWl2n7eNqeWRCNmzLXnF
> aVJLqC9NajsY68SNfF0RF7MQd1Hmvl7x8v61ryq7LMJW1TFHP8ODFyEX40/p5agg
> 3Om2GD7bkJX+lUMYVLnfF/qjmRPWCH5i0eupGYGJEq/ecRTBHErriw==
> =b8mz
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 9
> Date: Mon, 16 Jun 2008 14:58:46 +0200
> From: Stefan X <stefanxe at gmx.net>
> Subject: Re: [Enigmail] forwarding S/MIME encrypted email failed
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <48566386.4020409 at gmx.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Patrick!
> I did exactly what you described which resulted in the mentioned
> (second) error message.
>
> Stefan
>
> Patrick Brunschwig schrieb:
> > Stefan X wrote:
> >> I received a S/MIME encrypted email (which I could not decrypt because
> I
> >> did not have the required certificate and did not used S/MIME at all).
> >> Thunderbird failed to simply forward this email to another recipient
> >> with the error message "pgpMime.sMime.incompatible". For the receiver
> >> rules are in Enigmail defined to send all emails encrypted. I also
> tried
> >> to send the forwarded email unencrypted but failed with an error
> message
> >> explaining me that Thunderbird can not find the defined encryption
> >> certificate or the certificate is expired. What to do?
> >
> > Forward the email as attachment and activate the option OpenPGP > Ignore
> > per-recipient rules.
> >
> > -Patrick
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail
>
>
>
> ------------------------------
>
> Message: 10
> Date: Mon, 16 Jun 2008 09:34:12 -0500
> From: "Robert J. Hansen" <rjh at sixdemonbag.org>
> Subject: Re: [Enigmail] Configuring default Key Selection
> To: Enigmail user discussion list <enigmail at mozdev.org>
> Message-ID: <485679E4.3020100 at sixdemonbag.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Simon Lowen wrote:
> > If this is not the case, then please would someone explain to me why
> > her public key is so large.
>
> Looking at the two signatures, it appears that one is a small DSA key
> (DSA1024), and the other is a large RSA key (RSA3072? RSA4096?). If I
> am correct, then that explains it completely. DSA signatures are much
> smaller than RSA signatures, and the larger the RSA key the larger the
> RSA signature becomes.
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail
>
>
> End of Enigmail Digest, Vol 60, Issue 20
> ****************************************
--
and he heard ugly kid joe while sputtering the disks in the fab after i asked: him why do you like working in germany: he answered: Hole Germany is a kindergarden: "why that" i asked again: he said "there are no weapons"
More information about the Enigmail
mailing list