Exchange 2000 and resolving DNS

[DavidSnell]

I have a particular problem with certain ISP's bouncing back emails sent from my office. Here's the scenario:

Exchange 2000 on a Windows 2000 server.
Email is sent and received via SMTP through our remotely hosted website.
Our ISP is Adelphia.net and we only use them for internet access NOT email or hosting.

We recently changed to them (Adelphia) based on price and bandwidth and prior to the change had no email sending problems. Now we cannot sent email to AOL or AT&T (rr.com) and probably 12 lesser ISP's.

As far as I can figure, these ISP's are doing a reverse IP lookup which does not resolve correctly so the emails are being refused. Here are the messages from them:

AOL: The following recipient(s) could not be reached sosandsos@aol.com. Could not deliver the message in the time limit specified. Please retry or contact your administrator. <servername.websitename.com #4.4.7>

AT&T: The following recipient(s) could not be reached:

soandso@berkshire.rr.com on 9/5/2003 12:58 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<servername.websitename.com #5.7.1 smtp;550 5.7.1 Mail Refused - albyny.adelphia.net_Residential_Range

In the brackets <> above, servername = Internal Windows 2000 File Server and websitename.com = our remotely hosted website URL.

We use Exchange for managing email which is sent/received via SMTP from the remotely hosted email server at Datapipe. I am at a loss as to how to adjust Exchange 2000 to resolve properly. Is this the problem or is it something else?

I really need some insight with this. We are having to go to the remote mail server via the Internet to send mail due to these problems.

Anyone have any ideas?

 

[xmsre]

albyny.adelphia.net_Residential_Range


You don't have a reverse lookup entry [PTR record] in the reverse zone hosted by adelphia. Call them and talk to them about it.

John
MOSMWNMTK

 

[DavidSnell]

Unfortunately - after 2+ hours on the phone with Adelphia and having the support call &quot;ramped up&quot; to higher levels of support 3 times, the final answer was &quot;we don't support Exchange Server or any servers for that matter, sorry&quot;

I've been looking around within Exchange Server. What does &quot;smarthost&quot; do and could this possibly be a work around?

 

[xmsre]

You use a sharthost when sharing a namespace. You have inbound go to exchange, then forward unresolved to a &quot;smarthost&quot;; whinex, gnotes, whatever.


Try one of the Exchange friendly ISPs listed on Andy's site:

http://www.swinc.com/resource/exch_isp.htm

John
MOSMWNMTK

 

[DavidSnell]

Changing ISP's is not a valid alternative. We currently have a 3MB Down/384K Up connection with Adelphia for $79 per month. Cheap and Fast.

I need to find a solution within Exchange Server or a work around I can provide to Adelphia.