[Enigmail] Help - Taum Tanlon

[Charly Avital]

Taum Hanlon wrote the following on 7/1/08 9:31 AM:
> 'Compose as HTML' was indeed checked.
> After unchecking this I sent a signed test message to another account
> and it says 'good signature'.
> 
> Hopefully everybody sees this one with a good signature as well.

Taum:
Signature now verifies.
I'm glad you could decrypt the message I sent you OFF LIST where your wrote:

> oh... I was able to decrypt this fine.
> Hopefully the issue was the 'compose as html' being checked.
> When thunderbird asks about sending as html I would choose text and
> didn't really think about messages being *composed as html and converted
> back to text before sending.

Olav Seyfarth wrote the following on 7/1/08 9:18 AM:
>> Hi Charly,
>> 
>>> No HTML tags show in the raw source.
>> 
>> the problem is that Enigmail does not sign correctly when the message is
>> composed as HTML and converted to plain text using TB2. My advice for the
>> moment is to avoid Thunderbird's HTML editor at all when using Enigmail
>> -- or using PGP/MIME as you said, but that with drawbacks in MUAs that may
>> not know about PGP/MIME.

Thank you, Olav.
The first thing I do with any MUA I use or test (currently four) is to
disable HTML (when it exists as an option or as a default) and to
compose only in plain-text.

But I can understand that there are users who may want to compose in
HTML. "Let the user beware", *adapted* from 'caveat emptor'.

Charly