SBS 2003 Server won't send to Exchange 2003 Standalone with same domain name as one listed in the Recipient Policy
Posted on 2006-05-03
I have a very interesting connundrum. I have a single SBS2003 server behind a Zywall 5 and about 15 users.
We are running Exchange with this network.
Our domain locally is companyname.com
Our local live internet domain is companycity.com
Then, in the recipient policies, we have setup the three domains that we send to.
We have the default policy set to companygroup.com, a external domain hosted in another city. Each user in the local city has to send email as this domain for compliance and simplicity purposes. So, users in Chicago for instance send emails out as firstname.lastname@example.org. Users in another city are members of another domain but we added a recipient policy to allow all internal users to send as email@example.com
The recipient policy is setup as follows:
@companygroup.com - default (Not responsible for this organization so the check box is unchecked inside the properties of this selection)
This is a second policy that is weighted higher.
This policy is at the top of the list while the default policy is at the bottom of the list.
@companycity.com - default (Responsible for sending mail to this organization) This domain is the domain that the local SBS server manages. Emails do not go out using this addressing.
For a while, I was having issues where the mail.companyname.com domain was listing at the bottom of each of the emails that came back as NDR's to domains like comcast, aol, and others.
I checked in the SMTP Virtual Server Properties, then the advanced button and found that instead of companycity.com, companyname.com was being used. companyname.com is a LOCAL domain like I mentioned. It does not resolve DNS wise to any external one to one NAT'd address where as mail.companycity.com does. So, domains that do reverse lookups where failing those messages.
We altered the setting to be mail.companycity.com and that worked for that issue.
The email domain :companygroup.com is hosted on a Exchange 2003 server in Chicago.
It is 3rd party hosted exchange.
We added a recipient policy to our SBS Exchange box to allow users to send emails out as if they were sending from @companygroup.com just like the users on the hosted exchange solution. The problem is, when we send emails to these users from the @companycity.com domain, they come back with the following error:
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
Does having a recipient policy set for @companygroup.com here in our office in a different city on a different server cause issues in this solution?
Do I need to enter a DNS entry for the mail.companygroup.com server in Chicago so that if the Exchange box can't do a directory look up for a user in the Chicago office locally it will forward mail there?
Basically, I need to be able to email people in our chicago office.
Since they host the companygroup.com domain, and I have companygroup.com as a recipient policy setting that has all outbound mail tagged with that domain, and it can't find them locally on the SBS server, it is failing when we try to send.
Any help would be appreciated!