-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jul 08, 2008 at 06:53:15AM +0200, Zbigniew Szalbot wrote:
>>As for how to debug dkim-milter, this is not the most appropriate >>mailing list. All I can do is tell you to record all postfix-to-milter Yes, that's what happens when a bug crosses boundaries between two apps. >>traffic with tcpdump including the full packet content, and if you >>can capture a session where dkim-milter crashes, then I can tell >>you what the packets meant. >Capturing a session might be quite a challenge as it crashes randomly at >any time, usually once every 3-4 days... It shouldn't be too hard. Just tell tcpdump to capture all packets on that specific port on localhost dumping to a local file. The last few packets will occur right before it dies. Start it in a screen session if you are afraid your ssh connection to the server will die. - -- Regards... Todd There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. --Ed Howdershelt Linux kernel 2.6.24-18-generic 10 users, load average: 0.05, 0.06, 0.07 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIc5UZY2VBGxIDMLwRAtBeAJ9W+k3gpqv84owLacmDD7kSs/ZG9wCfaQm7 09l4Q1g9qqiO7dVRs7tBCsA= =fvg1 -----END PGP SIGNATURE----- ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
