dkim milter bug

Submitted by sgrayban on Wed, 01/26/2011 - 14:55

There is something very wrong with this filter... no local emails are being sent eg cron emails or local cron scripts.

see http://www.virtualmin.com/node/16752

This is a crippling bug because you either have to disable the milter or fix dkim-filter.conf each time you edit dns or create/delete a domain

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Wed, 01/26/2011 - 15:13

If your system's hostname is not one of the domains for which DKIM is enabled, the milter will reject email due to not finding a key to sign it with. The solution in Virtualmin 3.83 is to add your hostname to the "Additional domains to sign for" field on the DKIM page.

Submitted by sgrayban on Wed, 01/26/2011 - 15:18

I don't think that is right either as in my case roddenberry.borgnet.us is not a domain that is hosted on my billing server so it cant edit the dns.

I think the correct way is to not use the Domain * variable as the docs say.

Submitted by JamieCameron on Wed, 01/26/2011 - 17:04

Virtualmin shouldn't be setting Domain * as of the 3.83 release...

The real problem is that as far as I know, the DKIM milter cannot be told to not sign for domains it doesn't have a key for..

Submitted by sgrayban on Wed, 01/26/2011 - 18:12

Then this plugin is pointless especially when the new cloudmin plugin for remote central dns is released.

I disabled it on all the servers I manage because its breaking cron jobs.

Submitted by JamieCameron on Wed, 01/26/2011 - 20:18

Yeah, the behavior of dkim-milter in this case is annoying. Let me see if there anything that can be done to improve it ..

Submitted by JamieCameron on Wed, 01/26/2011 - 20:20

Yeah, the behavior of dkim-milter in this case is annoying. Let me see if there anything that can be done to improve it ..

Submitted by sgrayban on Wed, 01/26/2011 - 20:44

You need to remember that most people have more then one server and each server is usually using the primary domain name of that business.....

eg *.borgnet.us is what I use and I name each server different host. I have other clients that do the same thing simple because its easier. You can't use a hostname that is the same as the primary domain because postfix will start bitching. That's why you have to name them as host.domain.tld

dkim simply can't handle that which is why I never installed it and why I never suggested it.

Submitted by JamieCameron on Thu, 01/27/2011 - 18:13

I've figured out what is going wrong with the DKIM signing for mail from cron, and will include a fix in the next release ..

Also, DKIM will work fine with Cloudmin's upcoming centralized DNS feature.

Submitted by JamieCameron on Sat, 01/29/2011 - 01:05

Like you said, using Domain * was wrong.

Submitted by sgrayban on Sat, 01/29/2011 - 01:21

w00t ! I was right ! /me must log this in my daily journal :)

Submitted by Issues on Sat, 02/12/2011 - 04:21

Automatically closed -- issue fixed for 2 weeks with no activity.