Submitted by jrhosting on Tue, 02/17/2015 - 06:47
Hi,
Please adjust dkim-lib.pl to the following:
# diff -u dkim-lib.pl.orig dkim-lib.pl
--- dkim-lib.pl.orig 2015-02-17 13:42:40.390900000 +0100
+++ dkim-lib.pl 2015-02-17 13:42:55.541496134 +0100
@@ -64,7 +64,7 @@
{
return &get_dkim_type() eq 'ubuntu' ? 'opendkim' :
&get_dkim_type() eq 'debian' ? 'dkim-filter' :
- &get_dkim_type() eq 'freebsd' ? 'milteropendkim' :
+ &get_dkim_type() eq 'freebsd' ? 'milter-opendkim' :
&get_dkim_type() eq 'redhat' ? 'dkim-milter' : undef;
}
The startup file is named milter-opendkim instead of milteropendkim. After that the system recognizes the installation.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Wed, 02/18/2015 - 00:05 Comment #1
I wonder of the init script name changed in some FreeBSD release between when we initially added the DKIM support and the current version. Which FreeBSD version do you have there?
Submitted by jrhosting on Wed, 02/18/2015 - 17:41 Comment #2
10.x but that does not matter, the port is installing the startup script and that is the same for all versions of FreeBSD. I cannot find an easy reference (small peek, not looked at the code changes itself) to check when it might have changed.
https://svnweb.freebsd.org/ports/head/mail/opendkim/files/ it's at least like that for 12+ months...
Submitted by JamieCameron on Thu, 02/19/2015 - 00:40 Comment #3
Thanks - I will fix this in the next Virtualmin release.
Submitted by Issues on Thu, 03/05/2015 - 00:41 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Thu, 03/05/2015 - 00:41 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.