Firefox 4 Beta 9 breaks DKIM option in Virtualmin GPL

Submitted by arjones85 on Sun, 01/16/2011 - 19:35

For some reason enabling outgoing DomainKeys signing on my Virtualmin GPL box requires me to do it twice for it to show "Yes" in the "DomainKeys Identified Mail" section. Doing it once enable the records in the DNS files and starts the dkim-filter service, however if I go back to the DKIM section the "Signing of outgoing mail enabled?" shows "No". I have to click "Yes" again, save the options, and then it shows "Yes".

This appears to be an issue with only Firefox 4 Beta 9, as using Firefox 3 enables/disables it properly. This does not appear to be a caching issue with the browser however, as when enabled in Virtualmin the first time with Firefox 4, it shows No in both Firefox 4 and Internet Explorer. The DNS options are made and the service is running however.

Status: 
Active

Comments

Submitted by JamieCameron on Sun, 01/16/2011 - 22:37

That is really odd. Are you sure Firefox isn't caching form options?

If this only happens in Firefox (and not Chrome or IE), it suggests to me a caching bug ..

Submitted by arjones85 on Mon, 01/17/2011 - 02:02

Yep, like I mentioned:

This does not appear to be a caching issue with the browser however, as when enabled in Virtualmin the first time with Firefox 4, it shows No in both Firefox 4 ==> and Internet Explorer <==. The DNS options are made and the service is running however.

Just to clarify, I set it to "Yes" once in Firefox 4, then went back to the DKIM section and the option showed "No" even though DNS was set and the DKIM service was running. I then opened Internet Explorer, logged in, and it showed "No" also in IE.

I do not believe IE and Firefox share the same cache, and there are no other caching mechanisms in place on my local network.

Are you able to replicate this at all?

Unfortunately in the mean time I've had to completely disable DKIM on this box as I am being bitten by this same issue that has been reported by a few other people: http://www.virtualmin.com/node/16251

Haven't been able to figure out the cause for this issue either. Hostname and its corresponding DNS entry is set properly.

Submitted by JamieCameron on Mon, 01/17/2011 - 14:56

Which Virtualmin version are you running there? The 3.83 version (which is in the process of being released) fixes a few DKIM-related bugs, one of which might be the cause of this ..

Submitted by JamieCameron on Mon, 01/17/2011 - 21:13

You might want to try the 3.83 GPL version, which is available from http://www.webmin.com/vdownload.html

If you get the RPM, you can just install it with a command like :

rpm -U http://download.webmin.com/download/virtualmin/wbm-virtual-server-3.83.gpl-1.noarch.rpm