These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Configure Virtualmin email for email clients (like outlook.com, outlook. gmail.com) on the new forum.
I have the same problem, when you look at the logs, you see that your server does NOT report "mydomain.com" back, instead it reports the name of your bare metal machine.
-- your server is named "server.domain1.com"
-- you create a virtual host called "example.com"
-- you try to get mail from example.com using SSL/TLS
-- it fails
-- because postfix/dovecot are responding from "server.domain1.com"
I would LOVE to see this fixed, but the question has been asked many times.
I wonder if creating a "mail.example.com" domain alias would help.
There's nothing to fix. Connect to server.domain1.com to get email.
And that's why it doesn't get fixed. There's no SSL cert on "server.domain1.com" so it errors out.
That's a good point. The IMAP4 and POP3 servers on server.domain1.com will need to be configured with SSL certificates for either server.domain1.com or for *.domain1.com.
And so far as I can tell, Virtualmin won't do this, because Virtualmin always assumes that users always connect to their own domains. I think you will need to manually install the SSL certificate in this case.
One way of doing the above would be to let Virtualmin install the SSL certificate for a user's domain, call it example.com, into the mail daemons. Then search for the entry for that, and manually replace it with one for the SSL certificate for server.domain1.com or for *.domain1.com.
This assumption within Virtualmin, that each user connects to his own domain for email, and not to the underlying server, has led to a lot of confusion. I think in the next release they should simply have everybody connect to the server's name. All the big guys do it this way. If you put your website and email on Google Apps for Domains, you DO NOT connect your IMAP4 client to your own domain for email, you connect it to the name of Google's server.
So which are the right settings? Do we have to make changes to the ports and mail configurations?
gnnpls.com Creative Web Agency
There are some suggestions here: https://www.virtualmin.com/comment/751785#comment-751785.
Looking at the notes I made when recently setting up Virtualmin for the first time:
Assuming a user has been set up in Virtualmin > Edit Users > Add a user to this server - a user such as firstname.lastname@example.org,
the mail client settings are:
mail server: mail.mydomain.com
clear text authentication
my server requires authentication - yes
SSL outgoing 25 / incoming 995
Hope this is of some use. (Note the username format - this is what had me foxed to start with)
Thanks for this tip
OS: Centos7 Webmin version 1.851 Usermin version 1.720 Virtualmin version 5.99
I create dummy SSL enabled virtual servers for my mail server domain and my Webmin/Virtualmin server domain (e.g. mail.mailhosting.com & admin-v1.webhosting.com) then use the SSL management tools in Server Config for CSRs etc (or set up Let's encrypt for my Webmin virtual servers to periodically get me new certs). All I need to do is remember to click the appropriate [ Copy to Webmin ] [ Copy to Usermin ] [ Copy to Dovecot ] [ Copy to Postfix ] buttons every 2-3 months (or longer if it's a purchased cert). Note-I have nothing to do with webhosting.com or mailhosting.com - just using them as examples.
Craig Lawrie IT Services Manager DNG Technology
its working for me thanks for you & for your way in declaring the proper solution.