The log segment you cited included lots of stuff from postfix but nothing from dkim-filter. Does dkim-filter log nothing during this time? Do you have logging enabled? Are you checking all of the log files produced by syslog (e.g. "daemon" vs. "mail")?
The SMFIC_HEADER message causes a call to mlfi_header(). That function basicaly always returns a success status unless memory allocation or regular expression functions fail, and it tries to log (at LOG_ERR level) in both of those cases. For ECONNRESET to happen, the filter would have to either crash or decide that the MTA talking to it is sending gibberish and shut the connection down. Is there any evidence of a crash (e.g. change of process ID, coredump, etc.)? ------------------------------------------------------------------------- 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
