Correct way to configure email programs (SSL + moving servers)
I have a question for a long time: what is the best way to configure the e-mail programs of my clients considering I can move them between my servers?
Using the configuration shown in cPanel, would be set up with the server name, for example, server.mycompany-server1.com, but if I move the client across servers, they have to reconfigure all e-mail programs, for example, to server.mycompany-server2.com.
Because of this, I'm using mail.myclient.com format, the MX entry, mail. + client domain. But this way, as I understand, will always cause problems with the server certificate if the client uses 465 SMTP, 995 POP3 or 993 IMAP ports, regardless if the certificate is verified or self-signed, because OutLook will not accept "mail.myclient.com" (OutLook) X "server.mycompany-server2.com" (certificate after connected)...
So, what is the best way to set up OutLook that I can move clients between servers while not generate invalid certificate warnings in e-mail programs?
Thanks!
-
Hello :) Have you considered using the "Mail SNI" feature? Mail SNI configures the mail services to use the SSL certificate for your domain instead of the server's default certificate. Thank you. 0 -
Hello Michael, but, in this case, I need a SSL certificate for every client. I have more than 300. I'm looking for a way to use mail.myclient.com using a valid SSL certificate (not auto-signed) but for the server only (server.mycompany-server1.com). Is possible? Thunderbird shows an error once, and is possible accept the "error" (exception). But Outlook shows an "invalid certificate" message everytime clients open the program and send/receive a message using TCP 465/587/995... Thanks. 0 -
Hello :) There's no other way around this issue unless you install a SSL certificate for each domain name and enable the "Mail SNI" feature. You will simply need to have your clients update their email client configuration details after migrating them to a server with a new hostname. Thank you. 0
Please sign in to leave a comment.
Comments
3 comments