If you do as I was suggesting, to change the VMMARK2.CONFIG file, hosts files, and VM names, this does not require you to change the hostname of Mailserver. The Windows HOSTNAME (WIN-0FBCUBV1XIX) is different from the VMmark workload name, which I was suggesting you change to Mailserver0. It is the VMmark workload name that must be in each VMs' hosts file, not the Windows hostname.
You can try using WIN-0FBCUBV1XIX as the workload name but it is a risk. I don't know for sure that the Mailserver workload will work when there is "-" in the name like this. You are already getting errors with Mailserver authentication; it may be because of this or because of a different reason.
When you made Mailserver a domain controller, you should have picked a domain name. Is the domain name you picked "WIN-0FBCUBV1XIX"? If so, if you do not want to change your VMmark Mailserver workload name, then this would be correct:
MailServer/SERVERS="WIN-0FBCUBV1XIX"
MailServer/MailDomains="WIN-0FBCUBV1XIX"
MailServer/MailQualifier="your.company.com"
- The Windows HOSTNAME of mailserver is WIN-0FBCUBV1XIX.
- Your workload name (as recognized by VMmark; "MailServer/SERVERS") is WIN-0FBCUBV1XIX.
- Your domain name ("MailDomains") (which you should have already chose, when you made the Mailserver the domain controller,) the mailserver is a member of this domain: WIN-0FBCUBV1XIX
- The DNS ("MailQualifier") is your.company.com.
- The full computer name is WIN-0FBCUBV1XIX.your.company.com
- The fully qualified domain name would be WIN-0FBCUBV1XIX.WIN-0FBCUBV1XIX.your.company.com
- as <hostname>.<maildomain>.<mailqualifier>