On Fri, 9 Nov 2007, Micah Anderson wrote: > How can I figure out why these aren't getting signed? [...] > I was hoping I could coax dkim-milter into telling me why it wasn't > signing mails, this would be really useful to me to see what decisions > dkim-milter is making. For example if dkim-milter were to log: > > Not signing 32DB7B3294, ENVELOPE_FROM does not match FROM: > "ENVELOPE_FROM" == "riseup.net" && "FROM != "gmail.com"; > Not signing 54JD3J3943, originating IP not in internal hosts file: > "ENVELOPE_FROM" == "riseup.net" && "FROM == "riseup.net" && "IP == > 4.2.2.2"
Since you're not the first person to suggest such a thing, you might want to open a feature request on SourceForge for this. It won't make it into 2.4.x (already in Beta) but at the rate things keep evolving it won't be long before I can put some time into adding it. I'll take a more detailed look at your cases in a bit. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
