X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=115-188-36-24-adsl.sparkbb.co.nz; envelope-from=<surgemail-support@netwinsite.com>;
X-Received: from [192.168.1.160] (115-188-36-24-adsl.sparkbb.co.nz [115.188.36.24])
by netwin.co.nz (SurgeMail 7.4p) with ESMTP (TLS) id 25822697-1391920
for <surgemail-list@netwin.co.nz>; Thu, 06 Aug 2020 22:43:04 +0000
X-Return-Path: surgemail-support
Subject: Re: [SurgeMail List] Domain name change
To: surgemail-list@netwin.co.nz
References: <db0d3f3d-9791-b34e-1c0f-1bab76390cfc@ehowe.com>
<c7f73ab7-bd6d-a91c-f89c-f42d58c05e55@netwinsite.com>
<fdc8dff5-9de1-6c7f-687b-de2cf39bf294@ehowe.com>
From: Surgemail Support
Message-ID: <bd086b0e-f2c5-e233-9130-c86592a910dc@netwinsite.com>
Date: Fri, 7 Aug 2020 10:43:00 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <fdc8dff5-9de1-6c7f-687b-de2cf39bf294@ehowe.com>
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: : 0.000000
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-IP-stats: Incoming Last 0, First 23, in=379, out=0, spam=0 ip=115.188.36.24
List-Unsubscribe: <mailto:surgemail-list-leave@netwin.co.nz?subject=unsubscribe>
X-Mailing-List: surgemail-list@netwin.co.nz
List-ID: <surgemail-list@netwin.co.nz>
Precedence: bulk
Reply-To: surgemail-list@netwin.co.nz
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
>>>
>
>
--
p.s. We'd love a link from your website to our new domain: https://surgemail.com if/when u have time.
|