Benjamin Kaineder

Hello Chip, Thanks for your response. I did extensive testing to isolate the reason. The summarize, I can send an e-mail in three ways: do not specify charset, e-mail contains only ASCII => Blat specifies ISO-8859-1 / 7BIT => DKIM=PASS do not specify charset, e-mail contains e.g. one umlaut => Blat specifies ISO-8859-1 / 8BIT => DKIM=FAIL specify charset=UTF-8 => Blat specifies UTF-8 / 8BIT => DKIM=PASS Option 2 fails because the "final" upstream server (Microsoft O365) does not like the ISO encoding...

Doing some more testing, I tried to used -bodyF with a file saved with iso-8859-1 charset, same thing happened, the upstream server changes to utf-8 because of the "ö". Consequentially, if I specify the charset as -charset "UTF-8" on the command line, the DKIM result is PASS This is a fix at least for my test setup. Mails with umlauts are passing now. But there are two caveats with this fix, one, mail headers are reading Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="UTF-8" So...

quoted-printable not encoding umlaut / DKIM problems