Not usable email content encoding

[Martin Liška]

On 3/16/20 2:47 PM, Richard Earnshaw wrote:
> This isn't new.  It's usually the sender that controls that, though it's often automatic in their email client.

Jakub told me that he sees:

Ten mail byl:
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

while the email reaching the mailing list has:

Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Martin