Menu

#81 retain the passing DKIM selector

1.0.0
open
nobody
None
2014-08-01
2014-04-30
t_mk1
No

Request: update to retain passing DKIM selector, and report on it, as this example from IronPort:

<record>
<row>
<source_ip>209.85.160.197</source_ip>
<count>1</count>
<policy_evaluated>
<disposition>none</disposition>
<dkim>pass</dkim>
<spf>fail</spf>
</policy_evaluated>
</row>
<identifiers>
<header_from>youtube.com</header_from>
<envelope_from>youtube-subscriptions.bounces.google.com</envelope_from>
</identifiers>
<auth_results>
<dkim>
<domain>youtube.com</domain>
<selector>20120806</selector>
<result>pass</result>
</dkim>
<spf>
<domain>youtube-subscriptions.bounces.google.com</domain>
<scope>mfrom</scope>
<result>pass</result>
</spf>
</auth_results>
</record>

Discussion

  • t_mk1

    t_mk1 - 2014-04-30

    That did not come out well. Here is a file with the intended content.

     
  • Murray S. Kucherawy

     
  • Murray S. Kucherawy

    The DKIM information reported by OpenDMARC is extracted from Authentication-Results, which has no standard method to relay selector information. The agent upstream would have to add it in some de facto standard way, and it would only be available if both agents agree on how it should be done.

    Another way would be to have OpenDMARC do its own DKIM validation so it has access to that information.

     
  • Murray S. Kucherawy

    Planned for next major release.

     
  • Murray S. Kucherawy

    • assigned_to: Murray S. Kucherawy
     
  • Murray S. Kucherawy

    • assigned_to: Murray S. Kucherawy --> nobody
     

Log in to post a comment.

MongoDB Logo MongoDB