[Enigmail] [ANN] Enigmail v0.96.0 available

[kyshk at bc.iij4u.or.jp]

Hi!
Enigmail is always dependable.

I tried the Enigmail 0.96.0 but It is unusable Japanese language. It can
not send ISO-2022-JP encode encrypt message.

bad Thunderbird - Enigmail encode linkage.
(Enigmail 0.95.7 is OK)


,----[ example ]- send non PGP/MIME ISO-2022-JP encrypt message
| X-Enigmail-Version: 0.96.0
| Content-Type: text/plain; charset=UTF-8
| Content-Transfer-Encoding: 8bit
| Status: U
|
| -----BEGIN PGP MESSAGE-----
| Charset: ISO-2022-JP
| Version: GnuPG v1.4.8 (MingW32)
| Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
`----


,----[ not ]-
| Content-Type: text/plain; charset=UTF-8
| Content-Transfer-Encoding: 8bit
`----

,----[ but ]-
| Content-Type: text/plain; charset=ISO-2022-JP
| Content-Transfer-Encoding: 7bit
`----

use:
Thunderbird 2.0.0.22 (20090605)
Enigmail 0.96.0 (20090717-0949)
settings:
--rfc2440
extensions.enigmail.warnIso2022jp=2

source message encoding is ISO-2022-JP

1.non PGP/MIME encrypt :UTF-8 (bad)
2.non PGP/MIME signed  :ISO-2022-JP (good)
3.non PGP/MIME signed+encrypt :UTF-8 (bad)
4.PGP/MIME encrypt :UTF-8 (bad)
5.PGP/MIME signed  :UTF-8 (bad)
6.PGP/MIME signed+encrypt :UTF-8 (bad)

message(1,3,4,5,6) maybe can not read other MUA. (mojibake)
Content-Type header be distinct from contents.

Thunderbird 2.0.0.22 can not accurate encode.
(wrong Content-Type header)
Enigmail ignore [extensions.enigmail.warnIso2022jp] param.

and Japanese standard encrypt(or signed) message is NO UTF-8 and NO
quoted-printable.
--
kiyo