> The time on the server signing the message is incorrect. It's not a > timezone issue; i.e. it does not matter whether the signing server is > in EST and the verifying server is in PST. You should be concerned > about the error as some verifiers may reject the message.
Yep. I came to that conclusion off-list with help from Todd Lyons. The server's time is now in sync, and the signature is now passing the test at [EMAIL PROTECTED] > > >I attempted to disable this by including "SignatureTTL 0" in the > >configuration file, and restarting the milter, but the > signature still > >includes the timestamp and it's still marked as an error by the > >autoresponder. > > Comment out the SignatureTTL line. I commented that line out and it still produced error messages about the timestamp; however, this point is moot since we fixed the root cause of the timestamp problem (see above). Thanks, Peter ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
