Exchange logging of delayed messages

Question

We are having the known issue of delayed outbound messages (last error: 400 4.4.7 message delayed), whereas the suggested ways to fix it are to edit the host file on cas/ht servers or to turn on external DNS and then add smtp addresses as needed. 
Of course we can telnet to these same addreses and successfully send messages, so it makes it look like our DNS is broken, but our DNS appears to be working fine.  We are trying to investigate this further to confirm the DNS is indeed working as it should
so I checked to make sure logging was turned on in the cas/ht servers and the outbound connector is set to verbose logging.  I have also looked at some of the tools in the EMC toolbox to trace problem child messages.  Out of all of this, including
looking at logs, all I can see is the message goes out and/or it didn't get delivered, depending on what tool or log I am looking at.  I don't see anything else to indicate why it is having a problem with the message, thereby delaying it.  I don't
want to edit the host file as that is a hokey to manage this, and not the best option, and I was told by my supervisors that before we turn on external DNS we really need to find out why this is happening (and I really don't want to have to add smtp addresses
and domains as additonal housekeeping, this really shouldn't be necessary).  Does anyone have any ideas as to what I can do with the logging or tools to fill in the gaps?  As I said, all I get is that it failed to deliver, and well, I knew that going
in.  Thanks for any suggestions.  : )

Answer 1

We are having the known issue of delayed outbound messages (last error: 400 4.4.7 message delayed), whereas the suggested ways to fix it are to edit the host file on cas/ht servers or to turn on external DNS and then add smtp addresses as needed. 
Of course we can telnet to these same addreses and successfully send messages, so it makes it look like our DNS is broken, but our DNS appears to be working fine.  We are trying to investigate this further to confirm the DNS is indeed working as it should
so I checked to make sure logging was turned on in the cas/ht servers and the outbound connector is set to verbose logging.  I have also looked at some of the tools in the EMC toolbox to trace problem child messages.  Out of all of this, including
looking at logs, all I can see is the message goes out and/or it didn't get delivered, depending on what tool or log I am looking at.  I don't see anything else to indicate why it is having a problem with the message, thereby delaying it.  I don't
want to edit the host file as that is a hokey to manage this, and not the best option, and I was told by my supervisors that before we turn on external DNS we really need to find out why this is happening (and I really don't want to have to add smtp addresses
and domains as additonal housekeeping, this really shouldn't be necessary).  Does anyone have any ideas as to what I can do with the logging or tools to fill in the gaps?  As I said, all I get is that it failed to deliver, and well, I knew that going
in.  Thanks for any suggestions.  : )
SMTP Protocol logging is the place to start:
http://technet.microsoft.com/en-us/library/bb124531(v=exchg.141).aspx
I don't see why anyone would suggest configuring a host file in this instance.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.