Hello, Todd Lyons:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1On 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-milterYes, that's what happens when a bug crosses boundaries between two apps.Capturing a session might be quite a challenge as it crashes randomly at any time, usually once every 3-4 days...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.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.
So should it start it like so? tcpdump -i 4445 -F /tmp/dkim.logOr do I need more switches. I am actually determined to help the maintainers spot the problem so all advice greatly appreciated!
-- Zbigniew Szalbot www.LCWords.com
smime.p7s
Description: S/MIME Cryptographic 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
