To update things, after the spin around the firewall, the emails wind up stuck in a current session on server1 for delivery from server2 but there they time out. Emails the other direction, from server1 to server2, are delivered in a timely fashion. Brain hurts... must have beer...
________________________________ From: Bill Songstad (WCUL) [mailto:[EMAIL PROTECTED] Sent: Thu 4/10/2008 2:38 PM To: MS-Exchange Admin Issues Subject: routing problem I'm having a bit of a puzzler. I think it has to with DNS but I can't seem to pin it down. I added a second exchange 2000 server to a domain and moved one user (user2) to the second server (server2). User2 can send external mail fine. And can send mail to himself fine. But, when user2 sends email to any user on server1 the email is routed out through the firewall proxy and then back in. The domain network setup is like this: public.com mx 30 =aaa.bbb.ccc.ddd (external interface of the firewall) Private.net exchange servers: server1.private.net server2.private.net Recipient policies have mail to [EMAIL PROTECTED] and [EMAIL PROTECTED] with [EMAIL PROTECTED] being the default. DNS server=server1.private.net and forwards externally to the firewall. But it has a zone internally for private.net with hosts and mx records mx 10 server1.private.net mx 20 server2.private.net When user2 sends an email to a user on server1, an outbound queue appears on server2 labeled "server1.private.net (outbound)" but the email only arrives after spending several minutes swirling around on the firewalls smtp proxy. There are no connectors or smart hosts configured on either box. Does anybody have any thoughts on why the servers are sending the mail outbound rather than routing them directly to the other server? I swear my head's about to pop. Bill Songstad ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
