Submitted by Hal9000 on Fri, 02/19/2010 - 04:15
Hi there! I installed the mail relay plugin, and in the default server template i setup the default mail relay hostname in the plugin settings. However, I still could not enable mail relay for a domain. It turns out that the "default" setting in other server templates does not work correctly, i.e. I had to manually add the default hostname to all of my server templates. So I guess this is a little bug? :) BTW I'm still running virtualmin 3.76, as 3.77 still is not in the repo for some reason...
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 02/19/2010 - 13:00 Comment #1
Sounds like a bug..
What did you manually add to the template though? Was it an MX record, or something else?
Submitted by Hal9000 on Fri, 02/19/2010 - 15:15 Comment #2
hmmm i just endered a valid fqdn...
Submitted by Hal9000 on Wed, 03/17/2010 - 08:09 Comment #3
so is this a bug or is there an error on my part? :)
Submitted by JamieCameron on Wed, 03/17/2010 - 13:00 Comment #4
Not sure - what did you mean by " I had to manually add the default hostname to all of my server templates" ?
Submitted by Hal9000 on Wed, 03/17/2010 - 13:02 Comment #5
basically, the hostname i inserted in the "default" server template did not propagate to the other templates, even though they were set so they should have gotten the setting from the default setting. i had to specifically edit each server template and manually enter the hostname there.
Submitted by JamieCameron on Wed, 03/17/2010 - 15:57 Comment #6
So in templates other than "Default Settings" you should be able to select the "Default" option to have the setting inherit from the "Default Settings" template..
Does that not work for you?
Submitted by Hal9000 on Wed, 03/17/2010 - 18:06 Comment #7
exactly, that does not work. virtualmin will complain about a missing hostname or something (don't remember exactly). i have to specify the hostname explicitly in each template for this to work.
Submitted by JamieCameron on Thu, 03/18/2010 - 01:57 Comment #8
Ok, I see the cause now .. I will fix this in the 3.78 Virtualmin release.
Submitted by Issues on Thu, 04/01/2010 - 03:20 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.