On Sat, 29 Aug 2020 14:20:01 +0200 Ansgar <ans...@debian.org> wrote:
> Package: dkimpy-milter
> Version: 1.2.1-1~bpo10+1
> Severity: normal
> Tags: upstream
>
> I tried sending a mail with "From: 😸@43-1.org", "To: 😸@43-1.org",
> but dkimpy-milter didn't sign the message (it signs other mails) and
> the following error appeared in the log:
>
> +---
> | dkimpy-milter[454]: DKIM: The From header field MUST be signed
> +---
>
> If I use "From: {us-ascii-only}@43-1.org", "To: 😸@43-1.org", then the
> DKIM-Signature exists, but doesn't cover the "To" field:
>
> +---
> | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=43-1.org;
> | i=@43-1.org; q=dns/txt; s=2019; t=1598699673; h=subject : mime-version
> | : content-type : content-transfer-encoding : message-id : from : date
> | : from; bh=UjN96cC7omIGsgVag4PTJFDc2e+vxauhwCLS/rjCqvg=;
> +---
>
> It looks like dkimpy-milter silently discards header fields containing
> Unicode when signing.
>
> The same might happen when verifying mails (dkimpy-milter couldn't
> verify a signature where the signed "To" field contained unicode,
> while Spamassassin's DKIM check reported DKIM_VALID; not including the
> header when verifying the signature might be a possible explaination).
This should be fixed in the next dkimpy-milter release.
Scott K
