Okay
We're currently deploying a new Exchange 2000 server. It will be sitting behind
a linux based firewall, with our domain being handled by our website hosting
company. The box is nated, and has the internal address of 192.168.1.5
Currently we are unable to make incoming remote mail, say from hotmail,
go to local users, isntead it just queues up.
Our domain is (for example) communityhelp.com, with router.communityhelp.com being
the external ip of our network. The linux router portworwards all traffic to tcp and udp
25 to 192.168.1.5 (Our exchange server) and allows all traffic out from the exchange server
at this point. The linux box is also running a caching dns server, and this is the external dns server exchange is pointed to lookat.
I've configured a virtual smtp server to masquared as router.communityhelp.com, established a recepient smtp reciepent policy for @communityhelp.com, verified that the exchange box can properly determine mx's with nslookup (Via both tcp and udp). And I've setup a communityhelp.com smtp connector.
We've been battling with this thing for several days now and any assistance will be greatly appreciated.
One of my concerns is that it's something to do with the NAT, since obviously when the machine itself tries to reach border.communityfutures.org it cannot becouse it is natted behind that address.