Eric's right 'if' the server is running both apache and surgemail
and you are trying to share the letsencrypt certificate, then it
can be fairly irritating, but this looks like a case where the
mail server is being moved to 'mail.xyz.com' so in that case
letsencrypt is easier as there is no conflict. As a rule of thumb,
if surgemail is going to use port 443/80 directly then letsencrypt
is easy - if surgemail doesn't have port 80, then letsencrypt is a
pain :-).
Also the built in letsencrypt feature is completely automatic,
nothing needs updating manually - that may have changed since Eric
was using it.
ChrisP.
On 7/08/2020 10:57 am, Eric Vey wrote:
Excuse me for butting in, but if the same certificate is intended
to be used for a web server that also hosts Surgemail on the same
machine, you might want to stick with a purchased certificate.
Let's encrypt needs to be updated every 2-3 months and has a fixed
path to do that and things begin to get more and more complicated
after that. All kinds of permission troubles, if using Linux, and
configuration file headaches.
I finally gave up and bought one for not much money, pointed
everything at it and solved my headaches.
Eric Vey
On August 6, 2020 6:43:00 PM EDT,
Surgemail Support <surgemail-support@netwinsite.com>
wrote:
On 7/08/2020 10:21 am, Randy Zumwalde wrote:
Okay that exactly what I needed.
DNS A record for mail.ehowe.com will stay the same and I will change
the A record for ehowe.com to the new IP for the webserver.
Definitely going to try the letsencrypt method vs. re-issuing my
current certificate. Do I need to do anything there or will
letsencrypt overwrite my current certificate?
With the settings from that page it will replace the existing
certificate as soon as you run the command. (it actually puts in in a
new folder so the old one is still there if u really needed it)
Then after I do all this, I will have to let everyone know to change
their SMTP, IMAP and POP hostname to mail.ehowe.com instead of their
current value ehowe.com correct?
Oh yes most definitely.
ChrisP.
Thanks so much!
Randy
On 8/6/20 5:43 PM, Surgemail Support wrote:
Change only the URL_HOST setting to mail.ehowe.com
Then check the dns a entry for mail.ehowe.com points to your mail
servers ip address. (it looks like it does already).
Then yes regenerate your ssl (use letsencrypt it's easy and free)
-https://surgemail.com/knowledge-base/enable-ssl/
ChriSP
On 7/08/2020 8:12 am, Randy Zumwalde wrote:
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
--
Sent from my Android device with K-9 Mail. Please excuse my
brevity.
--
p.s. We'd love a link from your website to our new domain: https://surgemail.com if/when u have time.
|