Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mail delivery from internet problem 1

Status
Not open for further replies.

ctjohnson

MIS
Oct 9, 2001
73
US
I have Exchange 2k configured in a mixed mode AD domain. I'm able to send messages from exchange user to exchange user, and from exchange user to the internet.

We're in the process of migrating from the server, and we'd like our old mail server to forward messages to the new exchange server. Once I set forwarding on the old mail server and send a message, it cannot be delivered to the exchange server and I get the following error in the exchange event viewer:

Message delivery to the remote domain 'chrisj' failed for the following reason: Unable to bind to the destination server in DNS.

The message is also returned to me from my mail server with this error:

Unable to deliver message to the following recipients, due to being unable to
connect successfully to the destination mail server.

chris@ns-exchange.ourdomain.com

The dns name ns-exchange.ourdomain.com is configured in our dns server, and attempts to send the mail directly to the IP of the machine fail as well.

Any suggestions would be appreciated!
 
Where does your MX record point? To the Exch 2000 server or the 5.5 server?

At this point I'm just guessing but you may need to configure the 5.5 server (I don't have one so I can't help you specifically) so that it doesn't accept mail for that domain and only forwards it.

It might help to add the 2000 server in the 5.5's host file too.

I'm still unclear as to what your setup is, so if these suggestion don't help, try adding more detail.
 
Couple of things:

The old server isn't a 5.5 server, but a legacy email server running on a mac (eudora internet email server)

The MX record points to that server.

The basic idea is that the message is gets sent and arrives at the old mail server, which then forwards it to the exchange2k server. That's happening, but for some reason the exchange server is rejecting the message with the error I posted earlier.

We're not moving all users at once, so both servers need to be up. We've had no problem forwarding mail to other accounts from the old server (hotmail, etc) so I'm sure the problem is with the configuration of the exchange server. The old mail server has no hosts file, it uses our internal dns that has a record for the exchange server.

Hope that helps!

 
One more thought...When I send/receive internal email, and send external email from the exchange server, it has the return address of user@domain.com, not user@exchangeserver.domain.com. Could the issue be the machine is rejecting mail because it's addressed to exchangeserver.domain.com, when the exchange server thinks its responsible for mail for just 'domain.com?'

Does that make any sense?!?

Thanks for any help...
 
Your Recipient Policies determine what e-mail addresses the users will get. And it has to have the one your sending with and the one you get mail on.

So if you want both domain.com and exchange.domain.com add them to the Default Policy or whichever policy stamps the users. Dan
Microsoft Exchange Support @ Microsoft
 
Recipient policies are found under Recipients-Recipient Policies under System Manager. Double click Default Policy and then click E-Mail Addresses. Click New and add exchange.domain.com as an smtp address.
 
Hey-
I found the recipent policy, and the only two entries in it are an X400 address, and a default smtp address of 'exchangeserver.ourdomain.com'

Internet mail sent to user@exchangeserver.ourdomain.com is still rejected.

The message in the event log still says "Delivery to remote domain 'exchangeserver.ourdomain.com' has failed.

In AD Users and Computers, the email addresses are listed as 'user@exchangeserver.ourdomain.com....


What am I missing!?
 
Thanks for the help guys, I think I solved my problem. I tinkered a bit more, stopped and started the virtual smtp server, and things are now great

thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top