Murray, > provided no other forensics (e.g. a coredump with a -g build)
Btw, last time I tried debugging I gave up, because dkim-milter is a multithreaded program, which makes it more difficult (but I admit I haven tried very hard). Is there a simple way to prevent it from activating multithreading but still being able to speak a milter protocol, one session at a time? Mark ------------------------------------------------------------------------- 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
