X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=115-188-33-171-adsl.sparkbb.co.nz; envelope-from=<surgemail-support@netwinsite.com>;
X-Received: from [192.168.1.75] (115-188-33-171-adsl.sparkbb.co.nz [115.188.33.171])
by netwin.co.nz (SurgeMail 7.4b) with ESMTP (TLS) id 15250760-1391920
for <surgemail-list@netwin.co.nz>; Sun, 15 Sep 2019 22:48:51 +0000
X-Return-Path: surgemail-support
Subject: Re: [SurgeMail List] rerouting incoming mail for a domain
To: surgemail-list@netwin.co.nz
References: <4da5ba58-5338-8b07-57e5-6cae538d9759@lcrcomputer.info>
<020b9381-f1c1-4770-9b5d-9dbb5075b6d8@netwinsite.com>
<b7f83457-052c-ed1d-8c3e-34b29abba893@lcrcomputer.info>
From: Surgemail Support
Message-ID: <c6db0205-b608-47fb-ad0d-593b7b56fbc5@netwinsite.com>
Date: Mon, 16 Sep 2019 10:48:44 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <b7f83457-052c-ed1d-8c3e-34b29abba893@lcrcomputer.info>
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 20, in=531, out=0, spam=0 ip=115.188.33.171
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
Yes, they will need to login using the new name. e.g.
vdomain name="old.fred.com"
Then when they login their username must be:
bob@old.fred.com instead of 'bob@fred.com"
So yes annoying, but also good that it makes it clear they are
definitely logging into the old system and not using it by mistake...
ChrisP
On 14/09/2019 1:15 PM, Lyle wrote:
> Will renamed the domain in surgemail.ini cause any changes to log in
> to the old mailboxes? I know test test test and test some more...
>
>
> Lyle
>
>
> On 09/13/19 16:27, Surgemail Support wrote:
>> My preference, is to rename the domain, just the vdomain setting in
>> surgemail.ini, that will avoid any confusion. I think that's the safe
>> option.
>>
>> But if you insist, you can do this:
>>
>> g_route_local "true"
>>
>> g_route to="*@xyz.com" dest="newhost.xyz.com"
>>
>>
>> ChrisP.
>>
>>
>> On 13/09/2019 1:38 PM, Lyle wrote:
>>> I have been meaning to ask about this.
>>>
>>> I have a domain, example.com and they are moving from my surgemail
>>> server to hosted exchange with Microsoft. They want to be able to
>>> keep their old email for a period of time on my server.
>>>
>>>
>>> Problem is that there are other customers that need to email them.
>>> If they send email to example.com, it will drop into the local inbox
>>> and not be routed to their new exchange mailbox.
>>>
>>>
>>> Is there a way (beyond renaming the domain) to reroute local
>>> incoming mail for example.com to their hosted exchange rather than
>>> their local inbox? I don't know the priority that Surgemail uses
>>> and if gateway setting take priority for local incoming mail?
>>>
>>>
>>> Lyle Giese
>>>
>>> LCR Computer Services, Inc.
>>>
>>>
>>
>
>
|