Exchange 2003 email routing problem
Exchange 2003 email routing problem
Author
Discussion

Borris-Bear

Original Poster:

818 posts

276 months

Monday 6th August 2007
quotequote all
I have an Exchange 2003 server which currently (for historical reasons) servers only internal mail and have externally hosted POP3 accounts for external mail. Both these servers use the same addresses name@company.com DNS resolves to the external mail servers and the internal server is purely for sending emails within the UK office.

I am in the process of bringing all mail to the exchange server however in the meantime i am using POPBeamer to grab the emails from the POP server and put them in the relevant email inboxes on the Exchange server. This means that i can set users to use only the exchange server one by one, once everyone is switched over i can change the DNS MX records to point to my server here.
The problem arises beacuse we have a few foreign offices who also use the POP server for their emails if someone from the office here (who has been switched to use the exchange server) tries to send an email to one of these you get an undeliverable message as the mailbox doesnt exist. If i were to set up these users on the server then any messages would just sit on their inbox here and never get to the POP server where they will get their messages from.

Is there a way of forcing exchange to route these few addresses externally?

theboss

7,570 posts

250 months

Monday 6th August 2007
quotequote all
You would normally tell Exchange it is 'non authoritative' for the SMTP domain, you do this in the recipient policy which defines that domain. You can then create an additional SMPT connector for the domain which forwards emails to unresolved recipients (i.e. those people without Exchange mailboxes) to your public mail server. However you can't do this to the primary SMTP domain, can you confirm if your mycompany.com SMTP domain is marked as primary (in bold) in the recipient policy?

If so then another possibility - albeit less elegant - would be to simply put your externally-facing mail server in the 'forward unresolved messages to this host' field in your default SMTP virtual servers properties.

CUE99T

1,021 posts

239 months

Monday 6th August 2007
quotequote all
Why don't you just use the POP3 connector for exchange and then it will work seamlessly. All mail will be stored in the DB's properly and evetually you can use a smarthost when you move away from the POP3 proivder.

Seems alot of extra work for stuff that already exists.

What version of exchange is it you are using.

Borris-Bear

Original Poster:

818 posts

276 months

Monday 6th August 2007
quotequote all
Yes it is marked as primary in the recipient policy

The only problem with doing it the other way is that it will route all traffic (except internal) through the external smtp server rather than sending itself using DNS. Plus the external smtp server requires a username and pasword which cant be added in the "forward all mail with unresolved recipients" field.

Ideally i sort of need to flag these individual accounts to forward on their mail to the external mailbox. Could i set up some sort of contact that points to the external server and then set up a mailbox these few users and under delivery options use "forward to" and use this contact address?
Though the contact would still be @company.com and would try and forward internally?

malman

2,258 posts

290 months

Monday 6th August 2007
quotequote all
do your external recipient have an alias for their mail box e.g.

mailbox@ispdomain.com and mailbox@yourdomain.com

If they do or can have then setup an exchange contact for each alias (the not your domain alias)
setup a mailbox for each external user on your exchange system (they become a local recipient for your internal users) then set a forward on the exchange box to the alias contact created earlier and select whether to keep a copy or not.

The Griffalo

72,863 posts

270 months

Tuesday 7th August 2007
quotequote all
Borris-Bear said:
Yes it is marked as primary in the recipient policy

The only problem with doing it the other way is that it will route all traffic (except internal) through the external smtp server rather than sending itself using DNS. Plus the external smtp server requires a username and pasword which cant be added in the "forward all mail with unresolved recipients" field.

Ideally i sort of need to flag these individual accounts to forward on their mail to the external mailbox. Could i set up some sort of contact that points to the external server and then set up a mailbox these few users and under delivery options use "forward to" and use this contact address?
Though the contact would still be @company.com and would try and forward internally?
http://support.microsoft.com/kb/555187/en-us