❦ 28 septembre 2012 12:01 +0800, Thomas Goirand <[email protected]> :
> I believe the problem you are facing is that the init script
> uses --conf_file ${DKOUT_CONF} when it should really be using:
> --conf_file=${DKOUT_CONF} (eg = sign instead of space). This has
> already been fixed in the SID version, only the stable version of this
> package doesn't have the fix, but it certainly does not "renders
> package unusable".
I am a bit unsure since I am still using 1.2-6, but some arguments are
overriding the configuration file. For example, in my configuration
file (dkimproxy_out.conf), I have several domains, but since on the
command line, only one domain is used, the other domains are ignored.
Suppose my domain name is X and I have in dkimproxy_out.conf:
domain X,Y,Z
Then, dkimproxy is run with --domain=X
--conf_file=/etc/dkimproxy/dkimproxy_out.conf and when I send an email
From "alfred@Y", dkimproxy will sign with domain=X and not domain=Y.
Removing the --domain from command line fixes the problem for me. I see
the init.d script still do that in 1.4.1-3 but I don't know if dkimproxy
now favors the configuration file or not.
--
Many a writer seems to think he is never profound except when he can't
understand his own meaning.
-- George D. Prentice
signature.asc
Description: PGP signature
