Hello all, Thanks Todd for the beta rpms.... Any chance someone out there could provide me with all possible values, that opendmarc would be looking for, for the standard DKIM & SPF results as they appear in message headers? I believe in my case, i can create filters that can create "custom" headers based on the existence of other headers, rather than hacking opendmarc. I can just create the headers opendmarc is looking for based on what axigen gives me. I'd appreciate any help anyone can offer me on this. thanks a lot everyone! - Fabian S. On Wed, 04/23/2014 03:40 PM, "Murray S. Kucherawy" wrote: > On Tue, 22 Apr 2014, Fabian Santiago wrote: > > It only allows me to apply milters at SMTP connect, before any SPF or > > DKIM processing, so that won't work. > > Does that mean it only allows connection filtering, and doesn't include > the ability to analyze content? > > > It also doesn't produce standard email headers so I doubt opendmarc > > would even know how to read them if it were run at the correct step in > > the process. These are the relevant headers it produces that I'm > > assuming opendmarc would have to read: > > > > X-AXIGEN-DK-Result: No records > > DomainKey-Status: no signature > > X-AXIGEN-DKIM-Result: Uncertain > > DKIM-Status: bad format > > Yeah, those are non-standard local header fields. You'd have to hack > opendmarc to support those. > > It's this kind of thing that compelled me to add Lua support to OpenDKIM, > which allows you to do all kinds of custom work like this without having > to add that suppot natively. We might consider doing this for OpenDMARC > if this turns out to be a common problem. > > > Does anyone have any Axigen experience they can weigh in with here? > > Otherwise, I'm probably just going to build myself a Postfix / Dovecot > > or what have you server so I can make stuff work the way I want it to. > > You'd certainly get better support for postfix or sendmail in this group > than you would for your current solution. :-) > > -MSK >