Thanks Mark. I made the modification you suggested in
the Recipient Policy. It certainly looks like the right
Now I am getting the following error from my external
mail server when I try to send email to my test
account (flyingfox=ext mail server, keeper=firewall):
Sep 3 13:55:56 flyingfox.snowshore.com sendmail:
[ID 801593 mail.info] NOQU
EUE: keeper.snowshore.com [126.96.36.199] did not issue
connection to MTA
Any help you can provide would be appreciated.
>Have you modified your Recipient Policy to include
>told the policy that Exchange is responsible for handling
mail delivered to
>Here is an article that explains how to host multiple
domains on Exchange
>2000 and it includes some information about the Recipient
>Hope this helps
>Pentech Office Solutions Inc
>www.exchangetrainer.com and www.4mcts.com
>Visit www.msexchange.org for practical information on
>--- Please respond to this newsgroup and not directly via
>> Hi folks,
>> I have an existing mail domain "snowshore.com".
>> Email bound for this domain presently goes to an
>> external to firewall mail server "mail.snowshore.com"
>> (Solaris 8/sendmail). Employees get their email via POP
>> and IMAP through the firewall.
>> I am planning to deploy an E2K server internal to the
>> pass through the "mail.snowshore.com" external mail
>> server and get forwarded to the internal E2K
>> server (zoe.office.snowshore.com) on the internal LAN.
>> My present situation is that I have the forwarding
>> keeper is our firewall. Keeper receives the traffic on
>> port 25 and immediately rdr's it to the E2K server
>> BUT, Zoe has no idea about the keeper.snowshore.com
>> email domain. How do I make the E2K server knwo that
>> it can answer for other domains other than
>> test account so I know that piece is in place.
>> I think my problem is on the E2K server.