Murray S. Kucherawy <[EMAIL PROTECTED]> writes: > 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.
Hmmm. I turned on Diagnostics. There was no "DiagnosticDirectory" in the sample file, but I added a line with that as well, and pointed it to an existing directory. I enabled _FFR_ZTAGS in the site config file and recompiled and reinstalled, and restarted the service. I also turned on MilterDebug and set it 1 I see _zero_ changes in any debug output in the maillog, and no files created in the directory. I'm probably missing something or looking in the wrong place. > 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. Probably close, but no cigar just yet. ;-) Thanks again for your generous help! ------------------------------------------------------------------------- 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
