[Enigmail] Enigmail bug or failure in my system?

[Charly Avital]

Hi,

I am experiencing the following problem, when trying to process (verify)
signed messages posted by certain forum members.

This same problem existed when I was running Enigmail 0.95.6, and now
when I am running Enigmail version 0.96a (20080501).

I am running Thunderbird version 2.0.0.14 (20080421) Macintosh, on a
Macbook (Intel Processor), with gpg 1.4.9 or gpg2 2.0.9, see details below.

*Nothing* happens, the signed message is not processed, there is no
output of any kind.

I have tried two possible situations:
- when 'Automatically Decrypt/Verify Messages' is enabled.
- when the above option is not enabled, and I click the 'Decrypt' icon.

These messages have in common the following components:

- their raw source displays: Content-type: text/plain; charset=utf-8
Content-transfer-encoding: base64
- instead of the "usual" signed message with PGP headers and footers,
the raw source displays a block of rows that contain, each, 76 (seventy
six) characters. I would have expected 64 characters, as in base64 format.

When I process these same messages using other cryptographic systems,
the messages *are* processed, and display "BAD signature...". Those
systems are:

Apple's Mail with the GPGMail.bundle, using gpg2 2.0.9
Eudora's with Chang's AppleScripts, using gpg 1.4.9

All other messages I have received and continue to received, signed, or
signed and encrypted, are correctly processed (verified, decrypted,
verified).

Thanks in advance for your feedback.

Charly
MacOS 10.5.2 - MacBook Intel C2Duo - GnuPG 1.4.9 - GPG2 2.0.9 -
Thunderbird 2.0.0.14 - Enigmail 0.96a