Hello Jeff,
As far as results you are seeing with your milter, it could be related or
an issue with your milter.
Generally speaking "Authentication-Result" headers are read just fine
"except" for when mail comes from domains using Office 365.
On Thu, Jan 10, 2019 at 6:28 PM Jeff Anton <antonfb_at_hesiod.org> wrote:
> Regarding the "failed to parse," I've found that is reported because I'm
> also running senderid-milter which adds an Authentication-Results header
> and opendkim-milter sees that and reports the error you see.
>
> IMO that's a minor opendkim milter bug. Milters need to tolerate and
> share the Authentication-Results headers.
>
> I changed the order of the milters in my sendmail configuration such that
> opendkim runs before senderid and those warnings go away.
>
> Jeff Anton
> On 1/10/19 11:21 AM, Ken wrote:
>
> Hello Ole
>
> Actually the sample should have been:
>
> [sample start]
> failed to parse Authentication-Results: header field
> bad signature data
> Milter insert (1): header: Authentication-Results: server.my-domain.com;\n\tdkim=fail
> reason="signature verification failed" (1024-bit key) header.d=
> uconn.onmicrosoft.com header.i=_at_uconn.onmicrosoft.com header.b=JTRDdrro
> [sample end]
>
> DNS resolves it just fine on my end as well (it was the first thing I
> tested).
>
> It's more likely it's failing because it doesn't have a key to match the
> query to, due to the header parse failure
>
> Ken
>
> ....
>
Received on Fri Jan 11 2019 - 00:13:29 PST