[Enigmail] Enigmail fails to detect encrypted message

[Lachezar Dobrev]

  Well... This is more than an year later, but I finally figured out
that the culprit was not the quoted-printable (which was OFF by the
way), but the flawed text support.
  After looking at the code (Use the Source Luke!) I found out, that
Enigmail tries to disable flowed support upon installation. I am not
exactly sure whether upgrading executes the installation procedure, or
not. It seems flowed support has been  left active in my Thunderbird.
  I could not find the flowed text support option through-out
Thunderbird's menus and options, although I have the distinct feeling
I used to check it on somewhere.

  After manually disabling the flowed text support in Thunderbird
(using the Advanced Configuration Editor) signed and/or encrypted
in-line messages (non-PGP/MIME) are correctly detected and
decrypted/verified.

  Pity, 'cause I like flowed text, but whatever...

  I think I understand why Flowed Text and Quoted Printable break
encryption/signing, but are there any plans to support those? Or at
least disable those temporarily if the message is to be
signed/encrypted?
  How is signing/encrypting HTML messages implemented? I don't use
those, but maybe a similar approach could be useful?


2008/1/18 Lachezar Dobrev <l.dobrev at gmail.com>:
>   OK. I give up.
>
>> Quoted-printable is not an ideal choice for using with inline-PGP, there
>> are many problems with it that are due to the way Enigmail obtains the
>> messages from Thunderbird.
>   I see... That is a bit of a problem for me, but will have to just live
> with that.
>
>> I could decrypt both successfully on Linux and Windows. As said, by all
>> means avoid quoted-printable for inline PGP messages.
>   Well... You did...
>   However YOUR replies to the messages I sent you are also not detected as
> encrypted, and I had to manually decrypt them.
>
>   Anyway. Like I said I give up.
>
>   P.S. I have attached a screen snip to demonstrate I am not talking empty
> words.
>        I also attached two additional screen snips of a colleague's message
> and the effect of manually decrypting it.
>