asked on

Exchange Server 2003 - Could not deliver the message - Error 4.4.7

I have two servers with similar issues, usually sending new or replying to new emails.

They both get the following error:

Your message did not reach some or all of the intended recipients.
Subject: RE: Questions & July appt.
Sent: 6/10/2010 2:26 PM
The following recipient(s) cannot be reached:
???@aol.com on 6/12/2010 2:28 PM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<steelecpas.com #4.4.7>

Several are @aol addresses, but some are @irs.gov, etc.

I have checked dnsstuff, spamhaus, and road runner sties and have the following info for two sample sites (See details further down.

I have read similar posts, but am not sure where to start from here.

=====

Details

SERVER1
From dnsstuff.com
IP Information - 216.163.203.1
IP address: 216.163.203.1
Reverse DNS: exchange.redco1.com.
Reverse DNS authenticity: [Verified]
ASN: 46479
ASN Name: MOUST-PRIMARY-ASN
IP range connectivity: 2
Registrar (per ASN): ARIN
Country (per IP registrar): US [United States]
Country Currency: USD [United States Dollars]
Country IP Range: 216.163.192.0 to 216.163.255.255
Country fraud profile: Normal
City (per outside source): Unknown
Country (per outside source): -- []
Private (internal) IP? No
IP address registrar: whois.arin.net
Known Proxy? No
Link for WHOIS: 216.163.203.1

Road Runner Block Query Results For 216.163.203.1
Current Road Runner Block Report for IP address: 216.163.203.1
Date of Report: Mon Jun 14 17:12:37 EDT 2010

________________________________________
DNS Reverse (i.e., PTR record) Lookup : exchange.redco1.com

Cloudmark Sender Intelligence : Not blocked by this list
Spamhaus (ZEN) : Not blocked by this list
Return Path Sender Score Reputation Score : No Sender Score Reputation Score for this IP
MAPS RBL-Plus : Not blocked by this list
Road Runner Internal Name-Based Block : Not blocked by this list
Road Runner Internal IP Address-Based Block : Not blocked by this list
Return Path Reputation Network Blacklist : Not blocked by this list
No historical record of Road Runner Internal IP Address-Based block of 216.163.203.1
Contact Road Runner Postmaster Support For Assistance

==========

SERVER2
From dnsstuff.com
IP Information - 216.210.185.254
IP address: 216.210.185.254
Reverse DNS: exchange.steelecpas.com.
Reverse DNS authenticity: [Verified]
ASN: 7395
ASN Name: INTEGRATELECOM
IP range connectivity: 3
Registrar (per ASN): ARIN
Country (per IP registrar): US [United States]
Country Currency: USD [United States Dollars]
Country IP Range: 216.210.128.0 to 216.210.255.255
Country fraud profile: Normal
City (per outside source): Unknown
Country (per outside source): -- []
Private (internal) IP? No
IP address registrar: whois.arin.net
Known Proxy? No
Link for WHOIS: 216.210.185.254

Road Runner Block Query Results For 216.210.185.254
Current Road Runner Block Report for IP address: 216.210.185.254
Date of Report: Mon Jun 14 17:13:33 EDT 2010

________________________________________
DNS Reverse (i.e., PTR record) Lookup : exchange.steelecpas.com

Cloudmark Sender Intelligence : Not blocked by this list
Spamhaus (ZEN) : Not blocked by this list
Return Path Sender Score Reputation Score : No Sender Score Reputation Score for this IP
MAPS RBL-Plus : Not blocked by this list
Road Runner Internal Name-Based Block : Not blocked by this list
Road Runner Internal IP Address-Based Block : Not blocked by this list
Return Path Reputation Network Blacklist : Not blocked by this list
No historical record of Road Runner Internal IP Address-Based block of 216.210.185.254
Contact Road Runner Postmaster Support For Assistance

ASKER CERTIFIED SOLUTION

ElinKei

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Alisanne

ASKER

As it turns out, the DSL modem was replaced just prior to getting these messages at one site (So ill be checking the other), and the tech not only didn't plug the modem back in the UPS, but he didn't turn off NAT in the modem, so even though the server was on a static IP, the IP address seen by the public was that of the ISP and there was no reverse DNS lookup for our server registered for that IP address. Problem appears to be resolve at location 1.

I will be investigating location 2 shortly.

ElinKei

Glad to see you got a handle on it.

Alisanne

ASKER

At both locations, the the modem was the culpret!
Thank you!