Hep with SMTP domains

HCL Domino Domino Forum
1

I have a clients that was bought out and migrated to Exchange. All previous Notes email clients are on their system. There are still some mail in databases used for projects, and some apps that send emails out as workflow.So…

The new owners do not want email addressed to the mail in dbs using the origdomain.com name. They want all email addressed to newdomain.com. I have the SMTP to accept email to both domains for now. All clients now have their person docs to have a forwarding address to newdomain.com

Here’s the problem.

An app on the domino server sends an email to username@newdomain.com. The domino server attempts to send the mail out, but sees that it will accept mail for newdomain.com, find the person in the Domino Directory, and try to deliver it. The forwarding address again tries to send it to username@newdomain.com. The email gets caught in a loop and when it exceeds it hop limit, it fails.

I have tried a few different scenarios to stop this behavior, but have not yet been successful. I need to have the server accept email addressed to newdomain.com for the apps, but have it send outgoing smtp mail away from the server when addressed to username@newdomain.com

Any ideas will be most helpful.

Thanks,

ddubos@virtualcon.com

2

Subject: Hep with SMTP domains

have you tried setting the internet address field for all your users to username@origdomain.com and setting the internet address for the mail in databases to database@newdomain.com. Then go into the configuration document, Router → SMTP Basic Tab and configure inbound recepient lookups for full smtp address only. You will then need to set up a smart host that points to your exchange smtp server.

I have not had a chance to try it, but as you have told the router to ONLY match on the full smtp address it should fail to find username@newdomain.com. It should then foward that to the smart host which as its the smtp server for that user, should match ok.

However username@origdomain.com should match and cause the fowarding to take place.

database@origdomain.com will no longer work unless you put a dummy group / person document in the nab to foward to database@newdomain.com.

However database@newdomain.com will match and should not get fowarded to the smart host.

anyway thats the theory!