Hi there,

Murray S. Kucherawy pisze:

That startup script is using a local socket instead of having dkim-filter listen on that port.

But why would it do that if the config file specifies
Socket                  inet:[EMAIL PROTECTED]

and I have
milterdkim_cfgfile="/usr/local/etc/mail/dkim-filter.conf"
in /etc/rc.conf

If there's a "-p" on the command line, that overrides your configuration file setting.


I am confused. How should then dkim-filter be started?

1/ by calling /usr/local/libexec/dkim-filter -x /usr/local/etc/mail/dkim-filter.conf? I would have to add a cron job to make sure it is started when system reboots?

2/ by setting /etc/rc.conf entry? I already have:
milterdkim_enable="YES"
milterdkim_uid='mailnull'
milterdkim_cfgfile="/usr/local/etc/mail/dkim-filter.conf"
As you can see there is no -p switch but this way of starting milter does not cause it to sign all domains configured in the conf file.

--
Zbigniew Szalbot
www.lc-words.com

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss

Reply via email to