OuttaCyTE
asked on
mail stuck in edge transport queue
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 IntraOrgConnectionProtocol
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)"
and
"The DNS query for 'SmtpRelayWithinAdSiteToEd
The Queue's Last Error column says "451 4.4.0 DNS query failed. The error was SMTPSEND.DNS.NonExistentDo
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.
-g
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 IntraOrgConnectionProtocol
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)"
and
"The DNS query for 'SmtpRelayWithinAdSiteToEd
The Queue's Last Error column says "451 4.4.0 DNS query failed. The error was SMTPSEND.DNS.NonExistentDo
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.
-g
Last Comment
ASKER
using nslookup, set type=mx, I can resolve external domain addresses from both machines. I can do this for all servers listed in both the DNS of the network adapter and External DNS Lookups (they are the same, btw). 4.2.2.2 & 8.8.8.8
which authentication tab on which server are you asking about?
I rebuilt the edge subscription last night just to make sure there wasn't something fouled up there
How do you see what it's trying to lookup that it says is failing? I have no logging at all for SMTPSEND and where does the InterOrgConnectionProtocol
which authentication tab on which server are you asking about?
I rebuilt the edge subscription last night just to make sure there wasn't something fouled up there
How do you see what it's trying to lookup that it says is failing? I have no logging at all for SMTPSEND and where does the InterOrgConnectionProtocol
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
It works, and it was not obvious to this Exchange Duffer...
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
have you check the MX records, have you checked them using the DNS settings of the edge servers
it could just be an issue on the connectors on the authentication tab what are the settings?
its possible you need to change be clicking select “Exchange Server Authentication” and on the Permission Groups tab select “Exchange Servers”.
where is the next hop - is it to an external smart host?