• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 471
  • Last Modified:

One mail domain smtp routing to exchange 2007 organization, exchange 2003 and postfix

Hello,
Currently we have Postfix mail server, responsible for myorg.lt domain (holds mx record). It uses Transport mapping to sync with our AD  (ldap protocol), and creates smtp records for ad.user@myorg.lt  smtp=192.168.0.5 (Exchange 2003 srvA). In this way postfix knows, when to send mail to internal Exchange organization, when to generate NDR. It has pop3 mailboxes for myorg.lt domain too.
Exchange 2003 srvA has one smtp connector to route all outgoing mail to ISP SMTP server, and routing group connector to route *@myorg.lt to Exchange 2003 srvB, witch is located in other routing group. Exchange 2003 srvB has one smtp connector, sending all outgoing mail to ISP smtp server.

We are planning to implement Exchange 2007 server, with Exchange 2007 Edge server.
Main objective is to make new Exchange 2007 resposible for myorg.lt domain, so edge server gets all antispam work.
In Exchange 2007 i will make Internal relay domain for myorg.lt domain, and route all @myorg.lt mail to postfix server.
The problem as i see will be linux sending NDR for users that are in Exchange 2007 organization. No ldap or other connections with Exchange 2007 AD will be created for linux.
In later steps we plan to decomission postfix linux server (now it has too many pop3 mailboxes) and  Exchange 2003 srvA .

Anyone can help with routing ? :)
0
smeklius
Asked:
smeklius
  • 5
  • 4
1 Solution
 
MesthaCommented:
It isn't clear what you are trying to achieve here.
Are you deploying Exchange 2007 for all the users or not? Is the Exchange 2007 system going in to the same Exchange org as the Exchange 2003 server?

Simon.
0
 
smekliusAuthor Commented:
It will be new domain with new users, old exchange will remain with old ad/organization and old users. No domain/forest trusts will be used.
0
 
MesthaCommented:
You are trying to share the SMTP address space.
Exchange 2007: http://technet.microsoft.com/en-us/library/bb676395.aspx
Exchange 2003: http://support.microsoft.com/kb/321721

You need to decide which one is the primary server and then adjust its configuration appropriately.

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
smekliusAuthor Commented:
Thank you for links, it helped me in some points.

Ok my primary (mx record for domain) server will be Exchange 2007, and as sharing SMTP adress space it will forward all mails (that are not  in Ex2007 AD organization) to myorg.lt domain to old system Exchange 2003, and Exchange 2003 will be  responsible for NDR generation (authoritative for myorg.lt domain).
If i set Ex2003 organization to route mails that are sent to myorg.lt  to Ex2007 organization, it will then end in message loop  between servers.
What then is good solution to route mail from Ex2003 to Ex2007 without causing message loop ?
0
 
MesthaCommented:
As long as there is nothing on the Exchange 2003 server that says to send anything to the Exchange 2007 that doesn't exist, an email loop shouldn't be created.

However do be careful with NDR generation, as that can cause loops, which is why it is best that recipient validation for example is done at the point of delivery.

Simon.
0
 
smekliusAuthor Commented:
Ok, if i will make Ex2007 a point of delivery  (domain mx record), and it will be authoritative (recipient validation?), how then i can create mail routing/forwarding, to Ex2003, if Ex2007 doesnt know what users Ex2003 has ?

Unless i will create user/contact for every Ex2003 user in Ex2007 domain.
Maybie thats the best solution ?
0
 
MesthaCommented:
It would only be able to do recipient validation for addresses it knows about. If you want to forward failed addresses to another server then recipient validation cannot be used. That means you have to accept all of the junk and viruses that are sent to machine generated email addresses.

If you create a contact for each user in the other domain, then you need to find a way of getting email to the other domain, because a contact becomes an object that Exchange recognises and will not deliver the message to unless it has an additional email address in another domain.

Simon.
0
 
smekliusAuthor Commented:
Thank you for your thoughts, they were very valuable !
Now i'm making some virtual testing, to check if everything works as planed.
0
 
smekliusAuthor Commented:
Thanks for pointing in the right direction :)
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now