Sorry if this is answered already - I’ve searched and can’t find it.
When setting up a new virtual server I want the admin email to always default to sysadmin @ example .com - at the moment is seems to default to a randomly created one user @ domain .com
I’ve gone through every menu and added my preferred sysadmin email to wherever I can, but still the server default appears to be created with the random one. Is there a separate template that works differently for migrated servers?
The reason I ask is that I have checked the server-template and have looked everywhere to see how I can set a default Contact email / ownersemail for the Administrator. in Virtualmin Configuration, there is a setting “Default email address for new domains”
Option 1: Domain owner’s mailbox Option 2: add my own < i filled in option2.
However, I migrated a cPanel site in, and it still defaults to Administrator’s mailbox (username@ domain dot com)
I do see at the migration level - a box to add a different specific email, but is there someplace I can set a hard default for all virtual server creations to be sysadmin (not the randomly created one) - regardless of whether it is a new or imported virtual server ?
I don’t think that would be simple to implement. Also, as I mentioned on that other ticket you linked, it’s probably simpler and better not to include features in the cPanel backup that you don’t want to be restored.
Being able to set a default administrator username through the Virtualmin config page or by using templates would be a good improvement. What do you think, @Jamie?
This is not practical.When you aquire a cpanel account from another provider the relationship between them and the client sometimes has broken down and you are lucky to get the backup at all, let alone one configured as needed.
You can do a cpanel backup configured only with the features you want? Did not knwo this was a think and if it is, probably only through the CLI
I don’t disagree.
If you use features where they are applied live, then once the import is concluded then the user can be assigned to that feature set.
Would it work if each domain had an alias like sysadmin@domain.com that forwarded to the actual admin, which is normally formatted like domain@domain.com ?
Just a suggestion but why can’t have a master template for the migrate virtual server page? I have to import / migrate a lot of sites, why do we have to manually complete the form each time we do a new import
A master template for migrations would be similar to the existing migrate form - just use a saved default. The values could be applied to all new migrations but of course individually changed during an import as needed.
In my case, I just migrated a big cpanel account that had 26 sub-domains (I know right !) . Virtualmin enabled mail and logins for all of them and I had to go through and remove that from each of them, before I could remove the mail from the primary domain. I know I can do that via SSH but why not simply have a ‘master’ we can save and use as required.
This would include the default services to allow and the admin email (set as a master).
I was thinking of something like in the screenshot
You may find it easier to use the virtualmin migrate-domain shell command in that case - it’s easier if you to run a large number of similar migrations.
