Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

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

Posted on 2014-10-29
4
Medium Priority
?
309 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 14

Accepted Solution

by:
Andy M earned 2000 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 14

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

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

572 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