Exchange not sending/receiving emails from

I have an exchange 2003 (no spam filtering) running on windows 2003 SBS.

It can't send/receive emails from  How can I troubleshoot it?  I get the below "delayed" message but it eventually gives up and get an NDR.


-------- Original Message --------
Subject:       Warning: message 1OxjpD-0002bQ-Be delayed 48 hours
Date:       Wed, 22 Sep 2010 13:18:31 -0400
From:       Mail Delivery System <>
To:       xxx

This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its recipients after more than 48 hours on the queue on

The message identifier is:     1OxjpD-0002bQ-Be
The date of the message is:    Mon, 20 Sep 2010 10:06:41 -0700
The subject of the message is: Re: Tuesday's Meeting

The address to which the message has not yet been delivered is:

No action is required on your part. Delivery attempts will continue for some time, and this warning may be repeated at intervals if the message remains undelivered. Eventually the mail delivery software will give up, and when that happens, the message will be returned to you.
Who is Participating?
Alan HardistyConnect With a Mentor Co-OwnerCommented:
Please change the IP Address associated with to IP in your External Domains DNS records.   That is ALL you should need to do.
assuming this is your server ? can you confirm that the server can reach AOL's email servers on port 25 (do a telnet).

15      60 min      SMTP Test      Blacklist Check
15      60 min      SMTP Test      Blacklist Check
15      60 min      SMTP Test      Blacklist Check
15      60 min      SMTP Test      Blacklist Check

any of the above... try using the name first, let us know if that is reachable on port 25, and check the IP too.
I assume you have a static IP assigned to your exchange server?
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Alan HardistyCo-OwnerCommented:
AOL usually reject you if you are badly configured or blacklisted.

In your case, you are badly configured.

Your MX record is:

Your 1 MX record is:

0 [TTL=14400] IP= [TTL=14400] [US]

and your mail server is responding as:

OK: All of your mailservers have their host name in the greeting: ESMTP Exim 4.69 #1 Wed, 17 Nov 2010 02:53:10 -0500 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. <br />

Your Reverse DNS record is:

OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. Note that this information is cached, so if you changed it recently, it will not be reflected here (see the 'Reverse DNS Tool' for the current data). The reverse DNS entries are: [TTL=86400]

That in itself is good, but what is not good is that resolves as follows:


Non-authoritative answer:
DNS request timed out.
    timeout was 2 seconds.

For you to be configured properly, needs to resolve back to IP Address  Change that and should accept your emails (you may have to contact them to get removed from their blacklist).
fstincAuthor Commented:
I ran the telenet command from the email server and it returned this:
command used: Telnet > open > 25 ESMTP Internet Inbound
220-AOL and its affiliated companies do not
220-authorize the use of its proprietary computers and computer
220-networks to accept, transmit, or distribute unsolicited bulk
220-e-mail sent from the internet.
220-Effective immediately:
220-AOL may no longer accept connections from IP addresses
220 which no do not have reverse-DNS (PTR records) assigned.
421 4.4.2 Error: timeout exceeded

Connection to host lost.
220-AOL may no longer accept connections from IP addresses
220 which no do not have reverse-DNS (PTR records) assigned.
421 4.4.2 Error: timeout exceeded

thats the problem then, you need to ensure that your MX record name and IP are in sync.
your mx record is

you should probably for management sake have it as (instead of just )pointing at and then ensure the reverse DNS record for is as long as they match you are good.

your IP isnt on any blacklists so your all good once the above is changed.
Alan HardistyCo-OwnerCommented:
@Woolnoir - have you read my earlier post http:#a34152994 ?

Reverse DNS is configured correctly.  The issue is that resolves to a different IP Address to the fixed IP Address that is being used.
> @Woolnoir - have you read my earlier post http:#a34152994 ?

My apologies i didnt, I read from the posters last post downwards i.e http:#a34153274
Either way , the fault has been identified and should be pretty easy to correct.
Alan HardistyCo-OwnerCommented:
No probs - it can be useful to re-scan the thread before posting.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.