jgillfeather
asked on
Extending SMTP name space
Hi Experts,
I have a situation where we have taken over an existing organisation with their own SMTP domain name and Exchange 2000 (we run 2003 sp1).
The business wants them to send and recieve as our name space (as well as still receive on theirs).
Am i correct in thinking i can change their MX records to our host, add the name space to my recipient policy, and extend my name space to their exchange org (as per M$ article http://support.microsoft.com/default.aspx?kbid=321721) ?
After re-reading the above i think maybe not, as their org will not be authoritative for our name space?
n.b. their is currently a VPN link between the physical sites, but no forest/domain links.
a tried and tested methodology would easily be worth 500 pts...
I have a situation where we have taken over an existing organisation with their own SMTP domain name and Exchange 2000 (we run 2003 sp1).
The business wants them to send and recieve as our name space (as well as still receive on theirs).
Am i correct in thinking i can change their MX records to our host, add the name space to my recipient policy, and extend my name space to their exchange org (as per M$ article http://support.microsoft.com/default.aspx?kbid=321721) ?
After re-reading the above i think maybe not, as their org will not be authoritative for our name space?
n.b. their is currently a VPN link between the physical sites, but no forest/domain links.
a tried and tested methodology would easily be worth 500 pts...
ASKER
HI Exchgen,
correct - Domain B wants to be able to send/recieve as domain A, as well as recieve as B
They do not need to be able to send as B, and in fact we want to route akk e-mail via our exchange org.
correct - Domain B wants to be able to send/recieve as domain A, as well as recieve as B
They do not need to be able to send as B, and in fact we want to route akk e-mail via our exchange org.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Simon,
That sounds much easier - will let you know how it goes.
That sounds much easier - will let you know how it goes.
ASKER
Hmmm,
working, in a round-about sort of a way.
I have-
Created a Recipient policy in Org B to add an alias for DomainA.
Created an SMTP connector in Org B that connects to DomainA's exchange server as a smart host for the name space domainA.com
created a test account in DomainB, primary address is DomainA, alias for DomainB
created the same test account in DomainA, with domainB address as its primary and domainA as an alias
When sending to/from the DomainA address, it seems to work ok, however when looking at the headers, the DomainA server is simply forwarding on to DomainB (i.e. back out the internet connector). Similarly, when originating e-mail from the domainB mailbox, it goes out the local internet connector, rather than up the SMTP connector created above.
Not so good, as i assume the outgoing e-mail will get categorised as spam as the From address will not match the sending server.
Am I correct in assuming that i need to create another SMTP connector from DomainA to DomainB specifying all domainB mail should go to the domainb server as a smarthost, and similarly change the routing value on the domainb connector i created earlier to be lower than the local SMTP route? (thus all outgoing will route through the VPN rather than local internet connectors)
working, in a round-about sort of a way.
I have-
Created a Recipient policy in Org B to add an alias for DomainA.
Created an SMTP connector in Org B that connects to DomainA's exchange server as a smart host for the name space domainA.com
created a test account in DomainB, primary address is DomainA, alias for DomainB
created the same test account in DomainA, with domainB address as its primary and domainA as an alias
When sending to/from the DomainA address, it seems to work ok, however when looking at the headers, the DomainA server is simply forwarding on to DomainB (i.e. back out the internet connector). Similarly, when originating e-mail from the domainB mailbox, it goes out the local internet connector, rather than up the SMTP connector created above.
Not so good, as i assume the outgoing e-mail will get categorised as spam as the From address will not match the sending server.
Am I correct in assuming that i need to create another SMTP connector from DomainA to DomainB specifying all domainB mail should go to the domainb server as a smarthost, and similarly change the routing value on the domainb connector i created earlier to be lower than the local SMTP route? (thus all outgoing will route through the VPN rather than local internet connectors)
The SMTP Connector for the other domain is just for internal email.
Email destined for external users, but coming from the "other" domain will go out with all the other internet email that your server generates.
As long as both servers have reverse DNS, SMTP banner etc then you shouldn't have any problems with email delivery. Some sites are using SPF records to score spam, but they will not cause messages to be blocked.
Simon.
Email destined for external users, but coming from the "other" domain will go out with all the other internet email that your server generates.
As long as both servers have reverse DNS, SMTP banner etc then you shouldn't have any problems with email delivery. Some sites are using SPF records to score spam, but they will not cause messages to be blocked.
Simon.
DomainA is you and DomainB is the new company...
DomainB wishes to send email for DomainA as well as DomainB. (SMTP name space)
Am is correct?
Raghu