Hi there,
This is more like a feature request and not a bug report. Sorry, I don't know where to file requests instead of bugs.
Anyway, our particular email setup generates this warning when editing DNS records:
Warning - errors were found in this domain's DNS records : This domain has email enabled, but none of the MX records mail.bommelnetworks.net fallback.bommelnetworks.net point to it. Either the MX records should be corrected, or the email feature disabled if mail is hosted externally.
Is it possible to add an option in the Virtualmin settings to not check or at least not warn?
The warning alarms some users in our case while email functioning as expected.
An alike feature exists to not check resolv.conf. Such as switch is perfect.
Thanks!
Regards, Kees
Comments
Submitted by JamieCameron on Sat, 09/21/2013 - 11:27 Comment #1
There is an option to disable the resolv.conf check, at System Settings -> Virtualmin Configuration -> Advanced options -> Check resolv.conf for this system?
How does email get delivered to your system if none of the MX records point to it though?
Submitted by signet on Thu, 09/26/2013 - 02:19 Pro Licensee Comment #2
All Virtual Servers use the same MX record, e.g. "mail.company.com". The main reason for that is that we use TLS for SMTP and we'd like other mail servers to be able to verify the SSL certificate using the correct common name mentioned in the certificate. Obviously, "mail.company.com" points to the Virtualmin server.
The DNS plugin is unable to match "mail.company.com" to the Virtual Server and gives the warning menionted earlier.
For setups as such it makes sense to add a switch to disable the check or warning, just like the existing "do not check revolv.conf" setting.
Submitted by JamieCameron on Thu, 09/26/2013 - 11:24 Comment #3
Does mail.company.com resolve to one of the IPs on the virtualmin system?
Submitted by signet on Fri, 09/27/2013 - 02:58 Pro Licensee Comment #4
Yes, it does.
Submitted by JamieCameron on Fri, 09/27/2013 - 13:21 Comment #5
Ok, it looks like the real issue here is a bug in the way Virtualmin validates the MX IP addresses. I'll fix that in the next release.
Submitted by Issues on Fri, 10/11/2013 - 13:31 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.