Only thing I noticed was that there were multiple Auth-Res: headers in Andreas's example, one dkim= result per header. Slightly different from below, where multiple dkim= results are living in a single header.
HTH, =- Tim > On Jun 15, 2015, at 4:50 PM, John Levine via dmarc-discuss > <[email protected]> wrote: > >> It looks like the OpenDMARCs AR-header parser fail to recognise the >> AR-header generated by OpenDKIM. > > It must be more than that. I also use both opendkim and opendmarc, and > multiple > DKIM signatures are not a problem: > > Authentication-Results: iecc.com; spf=neutral [email protected] > spf.helo=spmpdv02.ieee.org; > dkim=pass header.d=iecc.com header.b="I8oYyArI"; dkim=pass > header.d=taugh.com header.b="YRY5Bjv7"; > dmarc=pass header.from=taugh.com policy=none > > I do run them in the same process and pass the DKIM results to DMARC > via API calls. If you ever want to implement p=reject that seems > unavaoidable. > > R's, > John > _______________________________________________ > dmarc-discuss mailing list > [email protected] > http://www.dmarc.org/mailman/listinfo/dmarc-discuss > > NOTE: Participating in this list means you agree to the DMARC Note Well terms > (http://www.dmarc.org/note_well.html) _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
