• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2012
  • Last Modified:

Exchange Error 550 4.4.7 QUEUE.Expired; message expired

Scenario:

We are able to send email to all OTHER external domains, with no issue.
"Company A" is one of our clients.  We are unable to send emails to "Company A"
"Company B", another one of our clients, can successfully send email to "Company A"
"Company C", a client of "Company A" is unable to send emails to "Company A"
There are at least 3 known domains that can not send email to "Company A", all other domains work fine.  

When we attempt to send to "Company A", our exchange 2007 server eventually kicks back the following error: #550 4.4.7 QUEUE.Expired; message expired ##

Troubleshooting steps:
Using telnet to connect to the MX address of Company A, on port 25:

My Mail Server & Office ISP (Time Warner) - FAIL
My Office computer & ISP (Time Warner) - FAIL
My Home computer & ISP (AT&T U-Verse) - FAIL
From my phone (Android, on Work Wi-Fi (TW)) - FAIL
From my phone (Android, on Verizon) - SUCCESS
"Company D" (Adams Wells) - SUCCESS
"Company E" (Cincinnati Bell) - SUCCESS

On all of the above, I am able to correctly resolve the DNS of their MX entry.

MXtoolbox.com's diagnostics can successfully connect to "Company A".

I'm running out of ideas on where to look to try an isolate this issue.  As I said, there are other companies who are also unable to send to Company A, so it's not necessarily something wrong on my exchange server.

I've tried to provide as much technical information as possible.

Thank you for your time, and suggestions.
0
tholman
Asked:
tholman
  • 6
  • 4
1 Solution
 
Alan HardistyCo-OwnerCommented:
If you can either post the domain name of company A or email me the info then I can look at their configuration and see if I can find any issues.

I can obscure the details if you post it or you can find my email address in my profile.

Alan
0
 
Alan HardistyCo-OwnerCommented:
Thank you for your email - running some checks now.

Alan
0
 
Alan HardistyCo-OwnerCommented:
Well - I have no idea what sort of system they have receiving their mail but they don't have a standard response to an EHLO command:

220 www.domain.com
ehlo mail.mydomain.co.uk
250 OK
mail from: <me@mydomain.co.uk>
250 OK

The more usual session would go like this:

220 mail.mycustomerdomain.co.uk Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at  Mon, 21 Mar 2011 21:09:52 +0000
ehlo mail.mydomain.co.uk
250-mail.mycustomerdomain.co.uk Hello [87.194.xxx.xxx]
250-TURN
250-SIZE 52428800
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-LINK2STATE
250-XEXCH50
250 OK
mail from: <me@mydomain.co.uk>
250 2.1.0 me@mydomain.co.uk....Sender OK

I would imagine they have something that is restricting the verbs used in the communication flow and this is know to cause mail-flow problems between some mail servers and others.

You might need to setup an SEND Connector for this particular domain and point the connector to your ISP for them to try and deliver the messages.

I feel that the problem is at the recipient end as they are non-standard and may well be shooting themselves in the foot by trying to over-secure their systems in the way they have.

Alan
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
tholmanAuthor Commented:
Alan,

Thank you for your effort and response.

I believe that they have an Exchange server.  I'm not certain what flavor.

Could you provide some advise, or research links for me to follow up with to advise them?

Thanks,
-T
0
 
Alan HardistyCo-OwnerCommented:
If they have an Exchange Server - it is hiding behind something.  Do you know what is receiving their emails because is certainly isn't an Exchange server?

That might give me a clue and might help resolve the issue.

Thanks

Alan
0
 
tholmanAuthor Commented:
I will attempt to obtain that information, and will post it as soon as I have it.

Thanks,
-T
0
 
Alan HardistyCo-OwnerCommented:
Thanks - fingers crossed they let you know.

Alan
0
 
tholmanAuthor Commented:
Ok, I managed to pry a little bit more information out of their IT department.

They are running Spam Sleuth Enterprise at their edge.  This then passes on to a Mercury Mail server.

He said they are also running PeerBlock 1.1 on their Spam Server.

I have no experience with Spam Sleuth, or PeerBlock, so I'm doing some reading on those now.  

They also told me, that from their end, it seems anyone with this problem uses exchange.  Though I highly doubt all exchange servers have this problem.  

Thanks for the continued assistance,
- T
0
 
Alan HardistyCo-OwnerCommented:
Well - that doesn't surprise me and guess what I am going to say?

Problem is at their end!!

They need to work with their Anti-Spam provider so that their software can work with an Industry Standard Exchange Server.

The support pages for Spam Sleuth reference Exchange 5.5 and 2000!  Hmmm - looks like a great - up-to-date product!
0
 
tholmanAuthor Commented:
Indeed.  As I began to prod them with questions regarding their configuration of PeerGuardian (my prime suspect), they informed me they are moving to a hosted email solution this weekend, so the issue should go away.

Thank you for all of your assistance Alan.

- T
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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