Ralph Jenkin wrote: > Package: dkimproxy > Version: 1.0.1-1 > Severity: normal > Tags: patch > > Although dkimproxy ships with configuration files in /etc/dkimproxy, the > init script does not make use of them, meaning that if a setup more > complex than a single domain which can be derived from the hostname is > required then editing of the init script is needed. > > In addition, the existance of the config files could easily lead someone > to think that they are used rather than ignored. > > Happily, this situation is easily resolved, and I include a patch to do > so. You may wish to also update the config files to use the ports > specified in the existing init script and README.Debian (personally I > use the ports in the config files).
Hi, Thanks for your patch, I'll use it soon in the next release. I intend to have a new version uploaded because some of my cron job restarts the daemon, and it can't find /sbin/start-stop-daemon (as sbin is not in the path in cron jobs, it seems). I will include your patch at the same time. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
