Submitted by sgrayban on Fri, 11/12/2010 - 03:08
Is there anyway to debug the DKIM initialization ?
Trying to get mine to work fails...
Finding virtual servers to enable DKIM for ..
.. found 2 servers
Extracting public key from private key in /etc/dkim.key ..
.. done
Setting domain and selector in DKIM filter configuration ..
DKIM setup failed!
Looking at all the standard logs doesn't show anything why its failing.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 11/12/2010 - 12:40 Comment #1
Was that the whole output from the setup process??
Submitted by sgrayban on Fri, 11/12/2010 - 12:43 Comment #2
That's it.
Submitted by JamieCameron on Fri, 11/12/2010 - 17:13 Comment #3
Ok, I see the issue - this can happen if you enter a selector name that clashes with a file in the
/etc/directory , likedefault. If you enter something like2010instead, it will work OK.There is a separate bug that the error message telling you this isn't working, which will be fixed in the 3.83 release.
Submitted by sgrayban on Fri, 11/12/2010 - 21:39 Comment #4
And debian uses /etc/default/ for program defaults.
Maybe you need to change default to say alpha in the code then.
Submitted by sgrayban on Fri, 11/12/2010 - 22:08 Comment #5
This is odd -- the selector default works once with debian but if you disable and try to re-enable it you get a the same error.
So why doesn't /etc/default/ break dkim the first time ?
Why would /etc/default/ even be a issue in the first place ?
Submitted by JamieCameron on Fri, 11/12/2010 - 22:54 Comment #6
The next Virtualmin release will use the year as the default selector to avoid this issue.
The 3.82 release made a change to support larger numbers of domains that requires a file be created in the
/etc/directory with the same name as the selector. This cannot clash with any other file or directory under/etc/. I would have preferred to name the file something more unique (perhaps by adding an extension), but the DKIM server doesn't allow this.Submitted by sgrayban on Fri, 11/12/2010 - 23:10 Comment #7
Umm why are you using the /etc folder ? Wouldn't be better to create a directory called /etc/dkim/ and use that for all signing ?
The selector default is already a suggested key to use according to the docs. I know you can call it anything you want but wouldn't it be better to use the defaults when you can ?
Submitted by JamieCameron on Sat, 11/13/2010 - 11:15 Comment #8
The current code uses the same folder as the DKIM configuration file, which is /etc/dkim.conf . I've changed the docs to suggest using
2010, and the next Virtualmin release will use that as the default root.Submitted by Issues on Sat, 11/27/2010 - 12:20 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.