Re: Adjust Authentication-Results header and verify DKIM reports are being send

From: Pau Peris <pau_at_webeloping.es>
Date: Fri, 4 Apr 2014 17:41:48 +0200

Hi Murray,

ok, i understand the log generating behavior. Do you know if OpenDKIM needs
some kind of configuration to send the generated reports once they're
requested?

Regarding to Authentication-Results, no, there's no special restrictions
which forces me to go that way. I just wanted to be able to provide such
header results in case i could do it in an orthodox way, i mean by software
designed to do it.

Thank you so much for your support,


On Fri, Apr 4, 2014 at 6:56 AM, Murray S. Kucherawy <msk_at_blackops.org>
wrote:
>
> On Thu, 3 Apr 2014, Pau Peris wrote:
>>
>> Could someone tell if i do need to run a separate process/action to
accomplish that ot if i am missing something?
>
>
> If you have reporting enabled, then reports will be generated when a
signer requests them and a verification fails.
>
>
>> I'm wondering how could i generate something like the following? Note
i'm running SPF checks through Postfix:
>>
>> Authentication-Results: mx.google.com;
>> spf=pass (google.com: domain of pau_at_sender-domain-example.com
>> designates 91.121.120.208 as permitted sender)
>> smtp.mail=pau_at_sender-domain-example.com;
>> dkim=pass header.i=_at_sender-domain-example.com;
>> dmarc=pass (p=NONE dis=NONE) header.from=sender-domain-example.com
>
>
> Not with opendkim as defined. It will add only the DKIM-specific values.
You could probably arrange to add one for SPF as well inside opendkim using
the Lua interface and some tricks to get SPF status from postfix. For the
DMARC stuff, that would need to be done downstream by something that
evaluates DMARC, which means it would appear in a separate header field.
>
> Is there some reason it needs to all be in one header field?
>
> -MSK
Received on Fri Apr 04 2014 - 15:42:24 PST