Solved

Error: #550 4.4.7 QUEUE.Expired; message expired ##

Posted on 2014-10-29
4
289 Views
Last Modified: 2014-11-18
I am having an issue with one of my client’s exchange servers. They have one external client that they cannot send any email to but if I get the external client to send a test message, it will be received without any issues. I have confirmed that he is using the same email address as we have. The domain is @iastate.edu

When I send a test message to the external clients email address, it shows up in the outbound exchange queue and never leaves. Eventually, I get the following error;
Error: #550 4.4.7 QUEUE.Expired; message expired ##
If I open the receive log files, I can see that there are no messages showing an attempt to deliver that message.
The folder I was looking in was as follows;
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend

Exchange mail flow troubleshooter doesn’t show anything wrong

What can I do to narrow down where the problem may be?
0
Comment
Question by:johnny181
  • 2
  • 2
4 Comments
 
LVL 13

Accepted Solution

by:
Andy M earned 500 total points
ID: 40410648
To start with I'd check dns. Make sure your email server can resolve the mx record for the client's email server correctly and that your email server can actually contact it.

Queue expiry typically indicates that the sender's server could not contact the recipient server or the recipient server is simply not accepting the connection.

If you can resolve/connect to it try running a telnet from your server to theirs and send an email via that - this gives you an idea of what is happening along each step of the progress. If that works fine it may be something to do with your send connector - set up a separate one as a test and see what happens.
0
 

Author Comment

by:johnny181
ID: 40410678
Ah, that is the funny thing. I went to MX Toolbox and their mail server shows mailin.iastate.edu. When I ping that from the server, I get a response of 129.186.140.10.
0
 
LVL 13

Expert Comment

by:Andy M
ID: 40411088
That appears to be correct - that hostname resolves to that IP on my system as well. If you are getting a ping response on your mail server for that then the connection/dns seems fine. I would try sending an email via telnet through that - may give you an idea of what part the process fails.
0
 

Author Comment

by:johnny181
ID: 40419632
Over the weekend, I went through the DNS on the Windows 2008 server and all appears to be good.
I sent another test a few minutes ago and one thing that I see now in the SMTP log files is the following;
451 4.7.1 Please try again later (TEMPFAIL)
0

Featured Post

Do email signature updates give you a headache?

Do you feel like you are constantly making changes to email signatures? Are the images not formatting how you want them to? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today.

Join & Write a Comment

OfficeMate Freezes on login or does not load after login credentials are input.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

744 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

12 Experts available now in Live!

Get 1:1 Help Now