Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

mail stuck in edge transport queue

Avatar of OuttaCyTE
OuttaCyTE asked on
6 Comments1 Solution4500 ViewsLast Modified:
I have a bunch of emails stuck in the edgesync - corp to internet queue and they have been there since friday.

These need to go out before they go NDR, but I can't seem to budge them.

both the hub server and the edge server have connectivity to the interent and I can ping and nslookup -q=mx on the targeted domains with out fail on both machines.

I see no errors in the event logs.

I get zero output at all (zip, nada, nothing) in the SMTPSEND log area.  I believe I have that turned on just fine.  I've even turned on the IntraOrgConnectionProtocolLoggingLevel to verbose.

I get a connection log and it has some entries that I can't decipher, much less act upon.
"Non-existent domain reported by x.x.x.x" (th ip was correct and it does respond to queries)"
"The DNS query for 'SmtpRelayWithinAdSiteToEdge':'edgesync - corp to internet':'<guid looking thing>' failed with error : InfoDomainNonexistent"

The Queue's Last Error column says "451 4.4.0 DNS query failed.  The error was SMTPSEND.DNS.NonExistentDomain; nonexistent domain"

First off, what address was it trying to resolve?  I've looked at the emails one at a time, and tested connectivity to the recipient and it all tests good.

Anybody got any ideas?  I've been struggling with this for hours now since I discovered the problem.

Avatar of OuttaCyTE

Our community of experts have been thoroughly vetted for their expertise and industry experience.

This problem has been solved!
Unlock 1 Answer and 6 Comments.
See Answers