I'm new to Exchange 2000 and Win 2000, although I have good experience with NT4 and Exchange 5.5. I'm working on a contract with a win2k machine running Exchange 2000 in a pure, basic SMTP setup that coexists with a Linux sendmail server. First, the Win2k machine was installed with a bogus domain name, and that has been a chore to work around. Second, the machine is using DHCP, although it receives the same IP address every time. Third, the Exchange and win2k components are in light use, although they could be reinstalled or heavily reconfigured if absolutely necessary. E2k SP1 has been applied. A brief explanation of SMTP mail flow : inbound mail for domain x.com arrives at Linux sendmail. Linux sendmail forwards mail via aliases bound for some x.com recipients to Exchange server. Exchange server accepts mail and delivers messages for x.com recipient, unless x.com recipient does not exist, which is returned to Linux sendmail. Exchange sends all outbound messages to Linux sendmail, unless outbound message is a defined local x.com recipient, which is delivered.
The problem: Outbound messages destined for non x.com recipients are sent immediately (using Linux sendmail), and have no problems. Outbound messages destined for locally defined x.com recipients are sent immediately and have no problems. Outbound messages destined for x.com recipients not defined locally (using Linux sendmail) remain in the queue, retrying on the specified interval, but never sending. Exchange shows the SMTP connection to be active. No error messages appear in event viewer. Freezing/unfreezing message has no effect. Disabling/enabling connection has no effect. Restarting SMTP service will force some messages to be sent, but not all.
Some side questions - should I require the machine to have a static IP address? Should I have the win2k Active Directory domain changed to be a real, routable domain internally?