At 00:55 30-12-2008, John Morris wrote:
>We're running CentOS, postfix and dk-milter 1.0.1 from the
>topdog-software.com RPM.
>
>All of the sigs dk-milter generated were bad, so with some twiggling I
>found that using "-o received" fixed things. Turning on the DKDEBUG
>switch revealed that the 3 Received: headers were being duplicated
>(triplicated?) 3 times each.
>
>Below is the debug information and the configuration that I thought would
>be relevant. If this isn't enough to point out the problem, please let me
>know what else I can provide.
[snip]
>Postfix configuration:
> smtpd_milters = unix:/var/run/dk-milter/dk.sock
> non_smtpd_milters = unix:/var/run/dk-milter/dk.sock
Dk-milter does not synthesize headers. It looks like Amavisd is
adding these Received headers. Are you sure that the message is not
being sent through Amavisd more than once?
Regards,
-sm

At 01:24 30-12-2008, John Morris wrote:
>CentOS 5.2, dk-milter 1.0.1 from topdog-software.com RPM
>
>Sometimes, after a 'service dk-milter stop' (which does a 'killproc
>dk-filter'), dk-filter appears to exit normally:
> Shutting down all DomainKeys milter (dk-filter): [ OK ]
> Cleanup for DomainKeys milter (dk-filter #0):
>
>However, the socket file is left in place:
> [root@... ldap]# /bin/ls -F /var/run/dk-milter/dk.sock
> /var/run/dk-milter/dk.sock=
>
>That causes an error when starting again:
> Dec 30 17:14:37 horseman dk-filter[1055]:
> Sendmail DomainKeys Filter: Unable to bind to port
> local:/var/run/dk-milter/dk.sock: Address already in use
> Dec 30 17:14:37 horseman dk-filter[1055]: Sendmail DomainKeys Filter:
> Unable to create listening socket on conn
> local:/var/run/dk-milter/dk.sock
> Dec 30 17:14:37 horseman dk-filter[1055]: smfi_opensocket() failed
>
>If the socket is removed, dk-filter can then start normally.
That error occurs as there is an existing socket.
>This can be worked around by cleaning up the socket from the init script.
>
>Is this a known problem? How have others solved this?
The init script is not part of the dk-milter tarball. dk-milter
cleans up the socket on exit. You can test that by stopping
dk-filter and see whether the socket file is still there.
Regards,
-sm

CentOS 5.2, dk-milter 1.0.1 from topdog-software.com RPM
Sometimes, after a 'service dk-milter stop' (which does a 'killproc
dk-filter'), dk-filter appears to exit normally:
Shutting down all DomainKeys milter (dk-filter): [ OK ]
Cleanup for DomainKeys milter (dk-filter #0):
However, the socket file is left in place:
[root@... ldap]# /bin/ls -F /var/run/dk-milter/dk.sock
/var/run/dk-milter/dk.sock=
That causes an error when starting again:
Dec 30 17:14:37 horseman dk-filter[1055]:
Sendmail DomainKeys Filter: Unable to bind to port
local:/var/run/dk-milter/dk.sock: Address already in use
Dec 30 17:14:37 horseman dk-filter[1055]: Sendmail DomainKeys Filter:
Unable to create listening socket on conn
local:/var/run/dk-milter/dk.sock
Dec 30 17:14:37 horseman dk-filter[1055]: smfi_opensocket() failed
If the socket is removed, dk-filter can then start normally.
This can be worked around by cleaning up the socket from the init script.
Is this a known problem? How have others solved this?
Thanks-
John