2 Email Domains are stuck in the Exchange Queue aol.com & comcast.net all other emails go out.

I have searched the subjects listed here and elsewhere, tried different things, but to no avail.

All emails go out of exchange except to those going to aol.com or comcast.net.  This started occuing 2 weeks ago when our isp changed our static ip address.  I know both aol & comcast require reverse-dns.  My isp told me that the static ip address is set to reverse-dns.

Our email hosting (not hosted by our isp) has not changed.  Our isp stated that it is probably an email hosting issue.  Correct me if I'm wrong, but I thought Exchange sent the emails out directly and did not go through my email provider (that we use for pop3)

I have run telnet to both aol & comcast (using the ip listed in the event log) and I was able to connect from the SBS server.  AOL gave me a message on reverse-DNS and then just waited for me with a blinking cursor.  Comcast gave me the following message:

554 IMTA09.emeryville.ca.mail.comcast.net comcast 24.38.171.189 Comcast requires
 that all mail servers must have a PTR record with a valid Reverse DNS entry.
Currently your mail server does not fill that requirement. For more information,
refer to: http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18784

Connection to host lost.

From the Event-ID here are the warnings:

AOL Issue               Event-ID 4007 for MSExchangeTransport
Message delivery to the host '205.188.156.248' failed while delivering to the remote domain  'aol.com' for the following reason: The connection was dropped due to an SMTP protocol event sink.
 he SMTP verb which caused the error is 'quit'.  The response from the remote server is ''.

Comcast Issue        Event-ID 4006 for MSExchangeTransport
Message delivery to the host '76.96.30.116' failed while delivering to the remote domain  'comcast.net' for the following reason: An SMTP protocol error occurred.

I don't know if this is related, but I receive a DNS warning Event-ID 7062 though with different domains listed as well as symantec liveupdate.

The DNS server encountered a packet addressed to itself on IP address 192.168.1.254. The packet is for the DNS name "pop.emailsrvr.com.". The packet will be discarded. This condition usually indicates a configuration error.
 
Check the following areas for possible self-send configuration errors:
  1) Forwarders list. (DNS servers should not forward to themselves).
  2) Master lists of secondary zones.
  3) Notify lists of primary zones.
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless subzone is also on this server.
  5) Root hints.

If you have any solutions, take it easy on me with the terminology and procedures, I am not an expert at this.

Peace,
lpii
lpiiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DrDave242Commented:
The error you get from your telnet sessions to AOL and Comcast both refer to reverse DNS, so it sounds like that's the problem.  Your ISP seems to be mistaken about having it configured properly.  Unfortunately, they're the ones who have to fix it, since they own the public IP address(es) you use, so you'll have to contact them again.  Give them the same information you posted here, particularly the errors you got from the telnet sessions to AOL and Comcast's mail servers.  If you get in touch with someone knowledgeable about this sort of thing, that should be enough information for them to fix it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TG TranIT guyCommented:
Go to dnsstuff.com and check your rDNS to see if the ISP has done its job.
0
DrDave242Commented:
Also, that DNS error in your logs is probably related to misconfigured forwarders or root hints.  Since this is an SBS server, the first thing you should do is run the "Configure E-mail and Internet Connection" wizard from the Server Management console and make sure everything in there is set correctly.  This will configure your DNS forwarders.

Next, open the DNS console on the server (Start > Administrative Tools > DNS).  In the console, right-click on your server and select Properties.  In the properties window, click the Root Hints tab.  You should see 13 servers listed, named a.root-servers.net, b.root-servers.net, etc.  Your own server should not be listed here.  If it is, remove it.  If the list is empty or incomplete, the easiest way to populate it is to click the "Copy from server" button and supply the IP address of an ISP DNS server.  This may only populate the server names and not their IP addresses.  If this occurs, wait a few minutes and check again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.