SMTP and Exchange from Outlook

[globalstrata]

We want to configure the exchange server to send messages out accordingly to what it is found by DNS. For some reason while configuring this, one of our engineers has selected something in the Exchange Server that causes for any Outlook client connected to the Exchange server not to be able to send messages out using any other account but the Exchange Server (IE: want to use my Yahoo to send a message to Joe@home.com instead of using exchange Exchange) The result is that exchange tries to send the message, I think through Yahoo but gets bounced back because of lack of authentication. The message gotten back is:

Joe on 10/9/2002 12:35 PM
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator.

Any thoughts ...

 

[dmanlam]

we get that same message for two of our remote employees. we all have external email accounts serviced by an ISP who manages our domain: abccompany.com (so, my email would be drew@abccompany.com). We use Exchange behind our firewall for internal purposes like, calendar sharing, IM, email within the company, etc....the outside world, in other words, cannot get to our Exchange server (it's on our private network). Each user has an "Internet Email" service confg'd in their Outlook to retrieve/send email sent to their domain email accounts (drew@abccompany.com).

Problem:
We set up our internal domain/DNS with the same name as our internet-known domain/DNS (abccompany.com). When we try to send email to our two remote users, we get that same error message. I think our internal DNS tries to take over or something and interferes with resolution by our external DNS servers (from our ISP). I've tried everything. I was told that we "should have" named our internal domain/DNS something different than our internet-known DNS domain...something like a sub-domain: internal.abccompany.com -- woops. Is this true? Anyone else have some advice, suggestions, wacky ways to circumvent such a problem?

THANKS! THANKS! THANKS!
-Drew

 

[globalstrata]

Our Internal name is different that our external name, so our problem is a bit different.

About your questions. The problem is actually coming from the Exchange server itself. The reason for this is that the routing checks to see if the domain is being "hosted" in the server, and if it is, then it does not sends out. I think you can configure Exchange to use a different Domain without actually using the domain name that your Active Directory uses. This way, your internal name is different. Then, you can use the Exchange MMC and go to the Recipiens\Recipiens Policies and change the default policy to give @internaldomain.com instead for all your mailboxes and that would take care of your problem.

Hope this helps,

Gladys