I have testet moving to a new Domino Domain in a test environment. After moving into the new domain when users reply to mails received when they were in the old domain, the old domain is appended to the mail, and therefor the server cannot deliver the mail.reply address looks like :
name/certifier@OldDomain
And server cannot route, since server and users are now in NewDomain.
How do I set up routing so users in NewDomain can reply to mails received in the old domain?
Subject: …
Which is the Domain of the users in the person document?
Subject: OldDomain and NewDomain
Users were in OldDomain and are now moved into NewDomain. Person documents state NewDomain in person documents.But after moving to NewDomain replying to a mail received when all users were in OldDomain failes, since mail adresses are appended @OldDomain.
Subject: Update - more stuff to be aware of
HiA short update. I found recent contacts in personal address books holds old domain name. So remember to clear that view for all users when moving to a new domain.
Also remember to delete all local contacts in users personal address books imported from Domino Directory. Or edit them and replace domain name with new domain.
Consider also to edit calendar entries. Meetings will contain old domain name for invitees. Replace the domain name via script. You may only need to replace domain name for future meetings.
http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21108767
Subject: amend mail template
Hi, we have just been through this process and its hard to avoid some issues. Obviously you can tell your users how to strip out the domai and re-send if they get a mail failure. We also amended the mail template strip out the domain - this is the code we used:
Open your mail template in Designer
Click on Forms and double click on Reply form to open it
Click on the field InheritedSendTo (on second line of red hidden fields) - it should look like this:
Delete all the code shown above (from @if
(@ClientType="Notes"........etc down to SendTo:CopyTo
)
Copy and paste this code in instead:
@If
(@ClientType="Notes";
@If
(@IsDocBeingMailed | (@IsDocBeingSaved & @IsAvailable(PostedDate));
@Unavailable;
@If
(@IsNewDoc & @IsDocBeingLoaded;
@Unique(@ReplaceSubstring( SendTo: CopyTo;"@WINET":"@CLNET":"@WVC":"@SVNET":"@HQNET":"@LGENET";"")) : @If
(
(@Name([Abbreviate];From)!=@Name([Abbreviate];Principal) & Principal != "");
From;
"")
;InheritedSendTo)
);
SendTo:CopyTo
)
Then click on the InheritedFrom field
and do exactly the same - ie delete existing code and paste in the following code:
Who := @If
(@IsAvailable(Principal) & Principal != "";
Principal;
@IsAvailable(From);
From;
@Author
);
@ReplaceSubstring(
@If
(@IsAvailable(FromDomain);
Who + "@" + FromDomain;
Who
)
;“@WINET”:“@CLNET”:“@WVC”:“@SVNET”:“@HQNET”:“@LGENET”;“”:“”:“”:“”:“”:“”)
Close the form and save it
Open the Reply With History form and repeat all the above steps for the same 2 fields, then save and close
If you use more than one mail template , repeat all steps above on each template
WE still had some odd issues with re-schedulking old calender events, Hope this helps
Subject: That may be a workaround.
HiThanks for your reply. I didn’t think of removing the Domain appended to mails, but it looks like a doable solution.
I was hoping som sort of router configuration, domain tweaks, resend features etc. would do the trick…this would be my first choice.
I will test your solution and may go with that.
Subject: Create a non-adjacent domain document
Create a Non-adjacent domina document, Mail sent to domain: Old Domain
Route through domain: New Domain.
Make sure a connection with mailrouting exist for the new Domain.
This casues the Router to change Domain for the users.
No change has to be done on any templates.