At beginning of September there was a problem with changing of text encoding, a bug which "fixed" on next update. Really???
An option to manage message (email) text encoding. It works for "text/html" content of message, but not "plain/text" (it remains default, and use US-ASCII). In fact of this issue many automated systems does not understand the set of question marks (should be the message text). 
Please FIX it completely!!! An example is provided bellow: 
------------------------------------------------------------------
This is a multipart message in MIME format.

--70c31b7f96bb4e30a2172fdea71b2f4f
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

?????????
?????????

Parasa ant visu... laisku



--70c31b7f96bb4e30a2172fdea71b2f4f
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div style=3D"font-family: arial; font-size: 12px;"><div data-empty=3D"true=
">=C4=85=C4=8D=C4=99=C4=97=C4=AF=C5=A1=C5=B3=C5=AB=C5=BE</div><div data-emp=
ty=3D"true">=C4=84=C4=8C=C4=98=C4=96=C4=AE=C5=A0=C5=B2=C5=AA=C5=BD</div><di=
v data-empty=3D"true"><br></div><div contenteditable=3D"false"><div>Parasa =
ant visu... laisku</div></div></div>

--70c31b7f96bb4e30a2172fdea71b2f4f--

------------------------------------------------------------------