On Fri, 11 Apr 2008, Hadar Pedhazur wrote: > Now to solve the main problem, of why the passing through of the message > through a third-party forwarding server causes dkim-filter to think that > an otherwise correctly signed header is bad, that's the remaining > vexation.
My suggestion would be to make use of the Diagnostics and DiagnosticDirectory features in the configuration files. You'll have to recompile enabling _FFR_ZTAGS to get the latter working. Then, when a message that fails verification comes to you, you will get a dump comparing the signed headers to the received headers in whatever directory you named, and you can examine them to see what got tweaked in transit to cause verifications to fail. That should show you what's munging the mail at one of the hops. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
