On Sunday, 30 October 2022 at 18:52 (-0400), David Rosenstrauch wrote:
On 10/30/22 6:48 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing
the problem?
After a quick google, this appears to be a known and old problem:
https://stbuehler.de/blog/article/2011/05/19/dkim_fails_at_content-transfer-encoding.html
Good find - thanks!
I'm not even sure where/how that encoding is being set. Must be
something that Thunderbird is doing. I'll do some digging into it.
Doing some testing of my own (via mutt), it appears to be something the
client does automatically when non-ascii characters are included in the
mail.
I just checked, and OpenDKIM correctly verifies signatures for base8
encoded emails sent directly to my server. Consider this email as a test
for what the Arch Liunx lists do: α, β, γ, …
Jaron
