I don't have very many clients and already have separate SSL's for the 
web server and email server. The problem is the Apache web server I have 
doesn't support the newer browser upgrades for Chrome and FireFox which 
prevent customers from accessing our online store because of TLS. 
Surgemail supports that and that's how I narrowed down what the issue 
was that happened overnight with customers complaining they couldn't get 
onto our websites. I tried to update my Apache but it it kept loading my 
old Apache plus I had other legacy middleware that didn't play well with 
anything I tried. So I decide to move my webserver of site where it 
would play well with everything but I can't do that until I get 
Surgemail properly configured for that transition.

I'm going to wait until this weekend to do what was mentioned in this 
thread so I don't mess up the business day tomorrow and have us dead in 
the water.


On 8/6/20 7:47 PM, Frank Bulk wrote:
> I'm not sure how many clients you have, but if it's a lot, you can facilitate a smoother transition by getting an SSL certificate that supports both ehowe.com and mail.ehowe.com.
>
> Frank
>
> -----Original Message-----
> From: Randy Zumwalde <zumwalde.rl@ehowe.com>
> Sent: Thursday, August 6, 2020 3:12 PM
> To: surgemail-list@netwinsite.com
> Subject: [SurgeMail List] Domain name change
>
> I need to change my Surgemail domain name from ehowe.com to mail.ehowe.com
>
> Currently email client's use ehowe.com as the server hostname for IMAP,
> POP and SMTP.
> I need them to change that to mail.ehowe.com.
> When I change my server hostname field in my email client to
> mail.ehowe.com it doesn't work. I'm guessing because the SSL certificate
> is for ehowe.com.
>
> Currently I have:
> domain_name = ehowe.com
> url_host = ehowe.com
>
> My DNS entries are
> A record is mail.ehowe.com
> MX record is mail.ehowe.com
>
> I'm not sure what to change for DNS or Surgemail and I'm afraid of
> messing the server up. I do know I will have to redo the SSL certificate
> though.
>
> I appreciate any insight so I don't screw my server up.
>
> Thanks,
> Randy
>
>