We migrated 150 domains from 4 inconsistently setup Virtualmin servers. What I mean inconsistent:
On some servers no SSL enabled per website, only some
On other servers no disk space monitoring because quotas were never setup properly from the start
Sometimes DMARC/DKIM enabled and sometimes not
3rd Party DNS setup so no DNS integration
What’s most concerning, and what’s overrunning the help desk with support calls, is the lack of autoconfig and autodiscover DNS records. Hours of time working with all the different mail clients and their inconsistent behaviors.
I need a way to insert autoconfig and autodiscover DNS records on around 150 domains on a server.
you have setup a global set of autoconfig / autodiscover rules
I’m not sure what you mean by that. I thought that autoconfig and autodiscover were per domain DNS records which simply allows destination email clients like Thunderbird and Outlook to query and find automatic email configuration data. That everything happens behind the scenes and that all is required are those records.
Are you implying that in order to make autoconfig and autodiscover DNS record work additional configuration is needed?
I can confirm that additional configuration is not needed: Virtualmin takes care of this on its own, out of the box, and that is how most of us leave it.
@tpnsolutions outlined a little hack which has the advantage of simplifying updates. This hack is entirely optional.
As of a few days ago when I use autoconfigure all the settings are picked up properly but Thunderbird is now defaulting to the wrong SMTP SSL and so can’t send mail without accepting a certificate warning.
I don’t understand what’s going on because when I do a Let’s Encrypt check the sites look correct.