-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote: > > > The Sunday 2007-12-30 at 10:24 -0000, G T Smith wrote: > >> Carlos E. R. wrote: >>> >>> The Friday 2007-12-28 at 11:21 -0000, G T Smith wrote: >>> > >> <snip> > >>> >>> A bad one goes like this: >>> >>> ... > >> <snip> > >>> Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8 >>> Content-Transfer-Encoding: 8BIT > >> I think the second line is the issue for the certificate problem. When >> it is 7 bit we get the Content-Type line turning up in the main message >> but the signature is flagged as good. When it is 8 bit (the signature is >> probably corrupted) and the signature is flagged as bad. (Just got >> message flagged as having a bad signature and examining headers this is >> the only common denominator I can see). Now whether these are two >> different problems or symptoms of the same problem is a moot point... > > In my case the signature is correct, because if I check the same email > (the same folder) using other programs, like KMail or Balsa they say it > is correct. It is Thunderibird who says it is not. > > I'll use some local chars to force this one to use utf: áéíóúñ Uýú > > This email will not check in thunderbird, I think. I'll tell you later. > > -- Cheers, > Carlos E. R. >
No it did not... :-( Looking at it further in my case I enabled a foreign language work around for sending. If I am lucky my signature will come across in this reply as OK. What we are getting is.... enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -d gpg: Signature made Sun 30 Dec 2007 11:16:37 GMT using DSA key ID 6D8D47D5 gpg: BAD signature from "Carlos Robinson (Carlos) <[EMAIL PROTECTED]>" enigmail.js: Enigmail.decryptMessageEnd: Error in command execution enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -d gpg: Signature made Sun 30 Dec 2007 11:16:37 GMT using DSA key ID 6D8D47D5 gpg: BAD signature from "Carlos Robinson (Carlos) <[EMAIL PROTECTED]>" enigmail.js: Enigmail.decryptMessageEnd: Error in command execution enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -d gpg: Signature made Sun 30 Dec 2007 11:16:37 GMT using DSA key ID 6D8D47D5 gpg: BAD signature from "Carlos Robinson (Carlos) <[EMAIL PROTECTED]>" enigmail.js: Enigmail.decryptMessageEnd: Error in command execution at the enigmail console.... A good signature report is... enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -d gpg: Signature made Fri 28 Dec 2007 11:37:35 GMT using DSA key ID 6D8D47D5 gpg: Good signature from "Carlos Robinson (Carlos) <[EMAIL PROTECTED]>" gpg: aka "Carlos E. R. <[EMAIL PROTECTED]>" gpg: aka "Carlos E. R. (Carlos) <[EMAIL PROTECTED]>" gpg: aka "Carlos E. R. (Carlos) <[EMAIL PROTECTED]>" gpg: aka "Carlos E. R. (cer) <[EMAIL PROTECTED]>" gpg: aka "Carlos E. R. (Carlos) <[EMAIL PROTECTED]>" gpg: aka "Carlos E. R. (Carlos) <[EMAIL PROTECTED]> " gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1911 BE75 9892 8AD4 AA5C 53F5 B533 181C 6D8D 47D5 This is proceeded by two bad signature messages... Looking at enigmail site it looks as if it might be worth compiling a SuSE version at see if the problem continues... and then possibly see if modifying the gpg call sorts problem.... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHd4IDasN0sSnLmgIRAnYKAJ9Djdi9lKru9/Lww0J0G1tYQOWPAwCfYzwn 6EQ+fFjGAmGxExhOp/X95do= =hQ66 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
