Solved

E-mail gets stuck in the queue with exchange 2003

Posted on 2010-11-29
14
359 Views
Last Modified: 2012-05-10
About 25 percent of email gets stuck in the SMTP queue with exchange 2003.  It has been fine for years and just started.  When you look at the queue there is a message the an SMTP protocol error occurred.  After many hours the message gets sent back to the user saying that it was undeliverable and took too long to deliver.
0
Comment
Question by:captjcret
  • 6
  • 4
  • 2
  • +1
14 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
Comment Utility
This is usually down to incorrect configuration at your end or being blacklisted.

Please check your IP address on http://www.mxtoolbox.com/blacklists.aspx

Also - your FQDN configured on your server on the SMTP Virtual Server has to resolve in External DNS back to the IP Address you are sending from and you also need to make sure Reverse DNS is configured on your Fixed IP Address with an FQDN that also resolves back to the same IP Address.
0
 
LVL 28

Expert Comment

by:sunnyc7
Comment Utility
What error code is that CaptJCRET
is it 5.5.7 / 5.5.1 ?

Please elucidate.

I'd go with Alan's suggestion first and eliminate those options.
0
 

Author Comment

by:captjcret
Comment Utility
From: System Administrator

Sent: Sunday, November 21, 2010 8:34 AM

To: Tina Schoneman

Subject: Undeliverable:Job Openings

Your message did not reach some or all of the intended recipients.

Subject: Job Openings

Sent: 11/19/2010 8:25 AM

The following recipient(s) could not be reached:

user@remotedomain.com on 11/21/2010 8:34 AM

Could not deliver the message in the time limit specified. Please retry or contact your administrator.

<SERVER.domain.local #4.4.7>

0
 

Author Comment

by:captjcret
Comment Utility
They are not blacklisted
0
 
LVL 76

Assisted Solution

by:Alan Hardisty
Alan Hardisty earned 500 total points
Comment Utility
If your FQDN is SERVER.domain.local - then it is not configured correctly.  You need to be able to resolve the FQDN in DNS and .local domain names are internal only domains and CANNOT be resolved.

Please change your FQDN to something like mail.domain.com or whatever your domain name ends with.

It can be change on the SMTP Virtual Server (Properties)> Delivery Tab> Advanced Button.
0
 
LVL 3

Expert Comment

by:msincorp
Comment Utility
It sounds to me that your ISP may have made a configuration change on their side.  I've seen this happen with Centurylink and Brighthouse quite a bit.

What happens is the RDNS is failing from what were previously accepted domains and the mail will sit in the queue until the retry timeout expires.

A call to your ISP might confirm this.  Sometimes it's as easy as a (R)DNS record change (sometimes you have to create a smart host on your ISP's network).

Hope this helps.

msincorp
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:captjcret
Comment Utility
I changed to full qualified domain name from what it was to mail.domain.com where I used thier domain name instead. When I clicked on check DNS it tells me it is not a valid domain
0
 
LVL 76

Assisted Solution

by:Alan Hardisty
Alan Hardisty earned 500 total points
Comment Utility
Do you have a record in DNS for your domain called mail.domain.com - bear in mind that I am only using mail.domain.com as an example - if your domain is Microsoft.com then it should read mail.microsoft.com

Whatever you use - has to resolve in DNS externally otherwise DNS lookup will fail.

If your domain ends .com - you don't have any A records setup - so mail.yourdomain.com will fail until you setup a new A record.  You don't have to use mail - you can use remote / bananas / poodles / Spock - the name is up to you - but you need to make sure you have a corresponding A record.
0
 
LVL 28

Expert Comment

by:sunnyc7
Comment Utility
Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This NDR may also indicate that a message header limit has been reached on a remote server or that some other protocol timeout occurred during communication with the remote server.

Troubleshooting: This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly. You may have to reduce the number of recipients in the header of the message for the host that you are receiving this NDR from. If you resend the message, it is placed in the queue again. If the receiving server is on line, the message is delivered.

TESTS:
a) go to mxtoolbox.com
enter the domain name of the *receiving server*
note down the first MX record listed.

lets say it is mail.domain.com

start > run > cmd
telnet mail.domain.com 25

See if you can get a SMTP 220 header.
If not - call the company and check if they are having any email issues.

thanks
0
 

Author Comment

by:captjcret
Comment Utility
I am getting the SMTP  220 header.  I am noticing that the sites I am having problems with all have something to do with roadrunner.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
Comment Utility
Any feedback to my last comment?
0
 

Accepted Solution

by:
captjcret earned 0 total points
Comment Utility
When I changed the DNS I was unable to send to anybody.  Changed it back to what it was and suddenly the whole thing is working fine!????? Nothing is sticking in the queue anymore.  I don't get it.
0
 

Author Closing Comment

by:captjcret
Comment Utility
Thanks for all your suggestions
0

Featured Post

Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Junk folder 23 108
Exchange 2013 -Load Balancing 5 29
PowerShell one liner to pull server names 3 30
exchange, transaction logs 3 25
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now