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.
>>>
>>>
>>
>
>