Stuck in Exchange Queue - One Domain

[MoobyCow]

I have an issues where mail is delayed when being sent to just one domain. There are no errors, no undeliverables and the DNS resolves just fine. I have even hard coded the MX records into DNS just to be sure, it doesn't help.

The messages will normally sit for most of the day and then send. It is not possible to force a connect or unfreeze the messages, because they never get to the point where the state is "retry".

The message state says "queued" and stays like that for hours.

It normally happens when there is an attachment on a message, but we send attachments to all other domains just fine.

 

[WhoKilledKenny]

Too me it doesn't sound like your issue. Sounds like the email server is having the problem and you Exchange server is working the way it should. Messages stay in the queue to attempt delivery at a later time.

To verify if you can connect and communicate with other mail servers, try to telnet to port 25.

Example:
telnet domianName.com 25
You should see something similar to:
220 DomainName welcomes you...

 

[WhoKilledKenny]

Sounds like the email server is having...

Clarification: The email server of the domain you are sending mail to. Not your email server.

 

[MoobyCow]

Thanks for the response.

I can telnet and send email just fine to this domain.

The messages DO NOT get queued to send at a later time. That would change the status to "Retry". The status of the messages stays as "queued" forever.

 

[WhoKilledKenny]

Have you contacted the Mail Admin of the domain in question to see if they have a policy with regards to the attachments you are sending?

 

[MoobyCow]

Yup. They have no policy that would reject our mail (it does eventually go through).

I would guess it is a DNS issue of some kind, but I can't find any problems with how it is resolving. (And DNS would normally fail and set the messages to "retry").

 

[N0ktar]

Defenitely sounds like a DNS issue to me. (Open ESM > Servers > servername > smtp > properties > Delivery Tab > Advanced > Configure DNS) and check the settings, you could also run DCDIAG or NETDIAG tools, see if all tests pass.
Test name resolution for that domain, enable message tracking if necessary and inspect the logs.(

http://www.amset.info/exchange/message-tracking.asp)

Good luck!

 

[WhoKilledKenny]

Sounds like your DNS servers are fine, since you are able to send to other domains. I understand what NOktar is saying, but usually you would not have anything configured under the Delivery Tab if you internal DNS servers resolve names on the Internet (Using root hints or a forwarder). And if you were able to Telnet via the domainName, that tells me DNS is resolving the name. You mentioned that you created an MX record; I would remove it if it still exists, possible it may be misconfigured. I see no reason, in this case, in hosting an MX record for the external Domain.

What is the domain name you are attempting to send email to?

Are you using any type of black list or have you been black listed?
Check here:

http://whois.domaintools.com/yourdomain.com

Check Server data area for black list status.