As mentioned, a stack trace would be needed, either via a coredump or a non-forking run inside gdb.
Another possibility is that a particular message is tripping the failure. In that case you can start sendmail with the flag "-d71.100" and the MTA will quarantine the mail it was processing at the time the crash occurred. If the same message causes the crash each time, a copy of the two quarantined queue files left behind might be extremely useful. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
