On Wed, 6 Feb 2008, Peter Wood wrote: > 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. > > Any thoughts on this?
SM answered the clock synchronization issue correctly. Here's some more detail about it: The UNIX time standard records time as the number of seconds since midnight, January 1, 1970, UTC. The time you see when you type "date" takes the local notion of that time and then convers it to your local time zone before displaying it. However, two synchronized systems in different time zones still have the same notion of that number of elapsed seconds. So if the autoresponder is synched to UTC and is complaining, your clock is probably fast. The default tolerance in dkim-milter is 300 seconds so, assuming elandsys.com's clock is synchronized to the Internet standard time, your clock is probably at least five minutes fast. To answer your second question, "SignatureTTL", if set, adds an additional parameter to signatures indicating after what time your signatures are no longer valid. After that time, even a signature that would otherwise validate has to fail. Thus, it's not helpful in solving the "future" problem. -MSK ------------------------------------------------------------------------- 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
