[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1857
  • Last Modified:

Mail stuck in Exchange 2010 Queue

In trying to send mail to AOL & COMCAST clients, there messages are stuck in the mail queue.

I do not have a problem sending to any other clients.  
I do not have a problem in receiving email from anyone.

I just paid $259 .00 to Microsoft Tech Support regarding us not being able to send to AOL clients.  Microsoft says the problem is on the AOL end.

Here is the result of a Telnet session:

From our Exchange Server to AOL Server:
2012-08-22T16:23:20.157Z,Default,08CF49B05FCB83DC,1,192.168.1.253:48192,64.12.90.97:25,+,,

From AOL Server to our Exchange Server:
2012-08-22T16:23:20.640Z,Default,08CF49B05FCB83DC,2,192.168.1.253:48192,64.12.90.97:25,<,421 mtain-mc05.r1000.mx.aol.com Service unavailable - try again later,

The error message presented on our Exchange queue says:
451 4.4.0 – Primary target IP address responded with “421 mtain-mc05.r1000.mx.aol.com Service unavailable - try again later”.  Attempted failover to alternate host, but that did not succeed.  Either there are no alternate hosts, or delivery failed to all alternate hosts.

Your help is greatly appreciated.
0
LessonsLearned
Asked:
LessonsLearned
1 Solution
 
xDUCKxCommented:
I get the same thing on all of them except mail-02.mx.aol.com.  They might be having an issue.  How long has this been going on?  I'd suggest waiting or giving AOL a call if it's been more then a day or two.
0
 
R--RCommented:
Check if your IP is black listed.
Check reverse DNS entry of your domain.
Check if your outgoing public IP and incomming public IP are same.
0
 
yoyoma788Commented:
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
vSolutionsITCommented:
Perform diagnostics of your server on mxtoolbox.com and let us know the results.
set logging level to high for msexchange transport and check if it reports any errors/warnings.
0
 
Exchange_GeekCommented:
I'd agree with R-R, AOL - Comcast - Earthlink hate domains who do not have PTR Records, however those NDR would be of 5.5.0 series Ref: MS Article

Likewise, if you need to check AOL is working or not, perform a telnet test against their present MX Records one-by-one and verify results.

aol.com MX preference = 15, mail exchanger = mailin-02.mx.aol.com
aol.com MX preference = 15, mail exchanger = mailin-03.mx.aol.com
aol.com MX preference = 15, mail exchanger = mailin-04.mx.aol.com
aol.com MX preference = 15, mail exchanger = mailin-01.mx.aol.com

Worst case scenario, you'll need to create a send connector and direct emails to one of these MX Records, for your email to get going.

Issue definitely is on their end.

Regards,
Exchange_Geek
0
 
LessonsLearnedAuthor Commented:
When I try to telnet into all 4 servers, i get the error:

421 mailin-01.mx.aol.com Service unavailable - try again later
421 mailin-02.mx.aol.com Service unavailable - try again later
421 mailin-03.mx.aol.com Service unavailable - try again later
421 mailin-04.mx.aol.com Service unavailable - try again later
0
 
LessonsLearnedAuthor Commented:
In the Exchange queue, the error is:

451 4.4.0 Primary IP address responded with: "421 mtain0mp02.r1000.mx.aol.com Service unavailable - try again later". Attempted failover to alternate host, but that did not succeed.  Either there are no alternate hots, or delivery failted to all alternate hosts.
0
 
Exchange_GeekCommented:
so, here is the proof that this is not you're issue.

AOL
Contact the IT of AOL.com and lodge a complain.

Regards,
Exchange_Geek
0
 
LessonsLearnedAuthor Commented:
I will contact AOL and report the problem.  When they get back to me, I will post it here.

Thanks for your help!
0
 
Exchange_GeekCommented:
That's the way to go my friend.

Regards,
Exchange_Geek
0
 
LessonsLearnedAuthor Commented:
To:  Exchange_Geek:

I don't know if this makes a difference: Our Exchange Server sends/receives e-mail from either of our three domain names:

estate-plan.com (mxtoolbox:  Reverse DNS matches SMTP Banner)
mmpph.com (mxtoolbox:  Reverse DNS does not match SMTP Banner)
erisa-law.com (mxtoolbox:  Reverse DNS does not match SMTP Banner)

However, we only have a problem with AOL & COMCAST accounts.
0
 
Exchange_GeekCommented:
Have you checked your outgoing IP against all possible Blacklist RBL? Just ensuring that you aren't blacklisted? Someone did comment on this very thread about it - these guys AOL and Comcast I swear hate when folks are on blacklist, so ensure that you aren't before you take up the case to their IT.

Regards,
Exchange_Geek
0
 
LessonsLearnedAuthor Commented:
I checked the website: http://www.blacklistalert.org/ 
No, I am not blacklisted anywhere.
0
 
Exchange_GeekCommented:
Perfect, then you are not at fault my friend.

Regards,
Exchange_Geek
0
 
LessonsLearnedAuthor Commented:
I will let you know when AOL responds back to me.  

Also, congratulations on your marriage to the love of your life.

Jim
0
 
Exchange_GeekCommented:
Thnx :)

Regards,
Exchange_Geek
0
 
MC-ISTCommented:
Any word on this?  We're having the exact same problem.  We've also contacted AOL.  We haven't heard anything yet.
0
 
LessonsLearnedAuthor Commented:
(Note:  Microsoft tech support had examined my Exchange Server.  No problem was found.  Microsoft tech support was correct in stating it was an AOL problem.  Microsoft refunded the $259.

The problem was indeed resolved my AOL (but they did not tell me how they did it).  I changed nothing on my end.  The solution is that you have to submit a support request (which is free) to AOL:  http://postmaster.info.aol.com/SupportRequest.php

You can only submit one request every 24 hours.  So that is what I did.  AOL finally got back to me in 7 days.

Here is the e-mail I received from AOL:

Hello,

Your issue has been resolved.  Please allow two business days for delivery to improve.  If you are still receiving errors after two business days, please submit a new support request at http://postmaster.aol.com/cgi-bin/plugh/other_issues_form.pl.

If you are the administrator of the IP submitted in this request, please consider getting a feedback loop on your IP. More information here: http://postmaster.aol.com/Postmaster.FeedbackLoop.html.

Thank You,
AOL Postmaster.
0
 
LessonsLearnedAuthor Commented:
How I knew the problem was resolved by AOL, is that I set up a free AOL webmail account.  

I sent an e-mail message from my AOL webmail account to my office account.  

The e-mail arrived successfully in my Outlook Inbox.  

I clicked "reply" and added the words "got it" in the subject line, then sent the message.  I checked my AOL Inbox, the "got it" message arrived successfully within 5 minutes or so.
0
 
LessonsLearnedAuthor Commented:
Thank you very much.  A lot of troubleshooting.  But now we know AOL was the problem, not Microsoft Exchange.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now