[Enigmail] Enigmail bug or failure in my system?

[Charly Avital]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Patrick Brunschwig wrote the following on 5/7/08 5:43 AM:
[...]

> The -d can also be used to verify messages. In fact for signed input
> data "-d" delivers de-armored output.
> 
>> Since these problems only occured approximately after the release of Thunderbird
>> 2.0.0.14, might it be possible that it is a regression from TB (CR/FL issues)?
> 
> I doubt, and if so it would probably be Mac-specific.
> 
>> Charly, to debug, please move aside your program and profile directories and
>> install just a TB 2.0.0.14 + EM 0.95.6 (release version). If it yields the same
>> error, please try with TB 2.0.0.13 + EM 0.95.6 (release version).
> 
> I'd rather suggest to try with gpg 1.4.9, and/or to disable the
> extensions Signature, HE Calendar and TimeStamp.

Patrick,

I have done that (1.4.9 and/or disable those three extensions all
together, each at a time), no change.

About using 1.4.9 rather than 2.0.9, I didn't expect any change, because
as I reported previously, Eudora+Chang's AppleScripts uses 1.4.9 (1.4.*)
by default.

I have checked approximately 50 signed messages in Enigmail,
gnupg-users, and other archives, and there are, definitely (in my e-mail
archives, of course), *only 3* e-mails that cannot be processed in
TB+Enigmail (but that can be processed in two different systems), and
all of those three have in common:

Content-type: text/plain; charset=utf-8
Content-transfer-encoding: base64

(BTW, my assumption that base64 means rows of 64 characters was wrong: I
have found out that 76 characters rows are OK)

I have also searched the web as well as Mozilla's knowledge base for
occurrences of base64, found
<http://kb.mozillazine.org/Attachments_renamed>, that does not seem to
be directly related to the above described problem, but that still
points at versions prior to TB 2*.


I very much appreciate the time and efforts you and Olav have put into
helping me with this issue.

I prefer to leave things has they are, but if/when I received a new
e-mail with the same characteristics, I shall check it in Linux, and
report what happens there. Those three "affected" e-mails are not
present in my Linux system's archives.

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (Darwin)
Comment: GnuPG for Privacy
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJIIZYgAAoJEM3GMi2FW4PvZuwIAJ8sr8Xu/LwoAsOAFTueWPuv
vijadRJAKa0eBdNcYzJS2JOCIuLVvv/UArCzCoTd6UqF0dSYFIymoajoyzHfsJWc
AbzOGHunJwveN3fJIQ4AX++CDsjXOaSYU+C//iLwBYIyVmQbVpnBezMgIRhVCUJY
xxCBjpAzwkrPexwfb2Xrg8qAC4xvRG6F7A1vQA4ksgqiqZIiZ5BcSf0Nw4DXvo1N
JbrCPeHFk9m/8FVS+PJP1ALHNCHzVbUpG+Nj3tog+In4m3ZniBOWdsQVup/AAMkU
6u5alVARrhn9RaeoHWf01OHzEHvz80grmwtEYZtSYdmw3/0A5qXvJGx6Gf0zUzc=
=2L6I
-----END PGP SIGNATURE-----