Re: [dkim-milter-discuss] Why is my dkim-milter-2.3.2 crashing?

[SM <sm...@re...>]

Hi Jim,
At 04:52 15-11-2007, Jim Hermann - UUN Hostmaster wrote:
>The dkim-milter ran longer this time.  After 6 minutes, it crashed again:
>
>Nov 15 06:28:47 host dkim-filter[22179]: Sendmail DKIM Filter v2.3.2
>starting (args: -x /etc/mail/dkim-filter.conf)
>Nov 15 06:29:10 host sm-acceptingconnections[22313]: lAFCT9Tj022313: Milter
>insert (1): header: DKIM-Signature:  v=1; a=rsa-sha256; c=relaxed/simple;
>d=uuism.net; s=host;\n\tt=1195129750;
>bh=wJRqpfSkoFfTdKnAriNos+6dde+GcwrXH8qk+fM05Ec=;\n\th=From:To:Subject:Date:O
>rganization:Message-ID:MIME-Version:\n\t
>Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:\n\t X-MimeOLE;
>b=1Thl0Q+agJtgqB6qheNyM8J4eQueNnDkiIcmNXYqvZJO6x9+tLkRC\n\tamfBh9p/hg5SefsR7
>Rl+i9IZ3s5GBS4xQ==
>Nov 15 06:29:10 host dkim-filter[22179]: lAFCT9Tj022313 "DKIM-Signature"
>header added
>Nov 15 06:29:10 host sm-acceptingconnections[22313]: lAFCT9Tj022313: Milter
>insert (1): header: X-DKIM:  Sendmail DKIM Filter v2.3.2 host.uuserver.net
>lAFCT9Tj022313
>Nov 15 06:29:19 host dkim-filter[22179]: lAFCTHk9022343 DKIM verification
>successful
>Nov 15 06:29:19 host sm-acceptingconnections[22343]: lAFCTHk9022343: Milter
>insert (1): header: Authentication-Results:  host.uuserver.net; dkim=pass
>(1024-bit key) header.i=@sendmail.net
>Nov 15 06:29:19 host sm-acceptingconnections[22343]: lAFCTHk9022343: Milter
>insert (1): header: Authentication-Results:  host.uuserver.net;
>domainkeys=pass (testing) header.from=sa...@se...
>[snip]
>Nov 15 06:35:08 host sm-acceptingconnections[23938]: lAFCZ7C6023938: Milter
>insert (1): header: X-DKIM:  Sendmail DKIM Filter v2.3.2 host.uuserver.net
>lAFCZ7C6023938
>Nov 15 06:35:14 host sm-acceptingconnections[23971]: lAFCZE5Y023971:
>milter_sys_read(dkim-filter): cmd read returned 0, expecting 5

Define DKIMDEBUG as t in your environment before starting dkim-filter 
in signing mode only.  See whether it crashes on the first message 
signed, then post the log.

>I don't think that Fedora Core 4 supports coredumps.  I'll look into using
>gdb.

A backtrace is better as it can help determine what the problem is.

Regards,
-sm