On Wed, Feb 3, 2010 at 11:54 AM, James R. Marcus <[email protected]> wrote: > dkim-milter is running like this, (I'm just pasting the relievant part of > the running process): > -p local:/var/run/dkim-milter/dkim-milter.sock > [r...@relay1 keys]# grep Socket /etc/mail/dkim-milter/dkim-filter.conf > ## Socket socketspec > # Socket inet:p...@localhost > Socket inet:20...@localhost
So the commandline is telling you were to put the socket, and the config file says to listen on a TCP port. I can't recall if dkim-milter can do both at the same time. Figure out which one or both, it is using with the lsof command. Find the pid of the dkim-milter process and do 'lsof -p $PID'. Look for listening TCP socket and for the unix socket. If it's only doing one or the other, then configure postfix to use the appropriate one. If the daemon cannot create the socket file in the correct directory, then either change the ownership of the directory so that it can create it, or change the user that it creates the socket to match the directory. -- Regards... Todd I seek the truth...it is only persistence in self-delusion and ignorance that does harm. -- Marcus Aurealius ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
