On 9/8/2016 10:04 PM, NoOp wrote: > On 9/8/2016 6:58 PM, NoOp wrote: >> On 9/8/2016 4:33 PM, NoOp wrote: >>> User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 >>> Firefox/43.0 SeaMonkey/2.40 >>> Build identifier: 20160120202951 >>> (but also occurs in SeaMonkey/2.40 linux and Windows&linux Thunderbird) >>> >>> When reading messages with Content-Type: text/plain; charset=UTF-8, the >>> actual text is not displayed (see screenshot >>> https://s15.postimg.io/vs2gxad2z/utf8problem1.png). >>> >>> However when I view the message body via View|Message Source/Ctrl+U I >>> can read the actual message (see screenshot >>> https://s22.postimg.io/ovcshm2nl/utf8problem2.png) >>> Note: full message can be viewed here: >>> http://permalink.gmane.org/gmane.comp.handhelds.android.k9mail/4896 >>> >>> Count the problem be that the header contains: >>> Mime-Version: 1.0 >>> Content-Type: multipart/signed; boundary="=-=-="; >>> micalg=pgp-sha1; protocol="application/pgp-signature" >>> see https://s14.postimg.org/upuq7zpkh/utf8problem3.png) >>> >>> Is there a setting that I can adjust to enable the message body to be >>> displayed normally? >>> >> >> Forgot to add that I've no problems reading/viewing the message in Opera >> Mail: https://s22.postimg.org/jcqf5eqtt/utf8problem4.png >> > > Profile related - new profile works just fine. Now I need to figure out > what in the existing profiles cause the problem - suggestions welcome. > > G >
It's an Enigmail extension issue. Disabling Enigmail 1.9.5 allows the text to be displayed. I've a question over on Enigmail mailing list to see if perhaps it is an Enigmail setting issue or bug. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
