Problem with text encoding setting within messages
Problem reported by Rajmund Andruskevic - November 21, 2017 at 10:19 AM
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.

Content-Type: text/plain;
Content-Transfer-Encoding: 7bit


Parasa ant visu... laisku

Content-Type: text/html;
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=
v data-empty=3D"true"><br></div><div contenteditable=3D"false"><div>Parasa =
ant visu... laisku</div></div></div>


1 Reply

Reply to Thread
I have exactly the same issue. Any fix in the meantime?

Reply to Thread