On Sun, 16 Nov 2008, Jim Hermann - UUN Hostmaster wrote: > I was not using the asynchronous (ARLIB) resolver, so I compiled > dkim-filter version 2.7.0 with define(`bld_USE_ARLIB', `True').
In that case any leftover descriptors prior to your rebuild are in use by (and perhaps leaked by) your system's resolver library. > After a week with the new dkim-filter, there are 25 netstat udp entries > for my Upstream Nameserver #1 and 5 entires for the local nameserver, > all for dkim-filter. I've been running dkim-milter 2.8.0.Beta2 for eight days now and it has one TCP port open on which it is listening and two UDP ports open which aren't associated with anything in particular. The former is for accepting connections from the MTA; the latter are presumably for DNS work. If you have "lsof" installed, using it on your dkim-filter process would be really helpful in corroborating what "netstat" is claiming. I would trust the output of "lsof" before that of "netstat" in terms of tracking down a possible problem. > DKIM does not release the tcp ports either. It has 6 tcp ports open to > port XXXX on the local machine. That would be the MTA connecting to dkim-filter. There's one of those for every connection your MTA has open. That's normal. The connections go away when the SMTP client disconnects from the MTA. Try it yourself; telnet to your own port 25 and you should see one more TCP connection appear between the MTA and the filter; disconnect, and it should go away. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
