This event can also occur if the SMTP service is not started on the front end of a FE/BE configuration as I found out after 10 minutes of trying to figure out what was wrong with my Exchange 2003 server. If you are installing service packs and other Microsoft updates, always double check your services after the install.
This event can have multiple causes, each of them being described in Microsoft article ME919091
This issue may occur when Sybari Antigen Version 7.5.1138 is running on the Exchange Server 2003 server. See ME922256
This event can be generated when e-mails are being sent without linefeeds at the end of the message and the message is relayed through SMTP on IIS 6/Exchange 2003. Our internal software was creating messages that did not have <cr/lf> at the end of each message.
With full logging on SMTP, YAHOO was the only site that indicated what the problem was with this entry:
2005-07-21 05:00:05 126.96.36.199 OutboundConnectionResponse SMTPSVC1 SRV-EMAIL1 - 25 - - 451+Timeout+waiting+for+end+of+DATA.+Be+sure+your+client+is+not+sending+bare+linefeeds. 0 0 87 0 120313 SMTP - - - -.
My temporary solution was to create a batch file that appends a <cr/lf> to each message stuck in the queue on the Exchange server. An update to our software will be released shortly that fixes the problem.
See the links to “Bare Linefeeds in SMTP Messages” and “LFs in SMTP” for additional information on this issue.
As per Microsoft: "This Warning event is logged when Exchange cannot deliver a message to a remote host. The event description should specify the reason for the failure". See MSEX2K3DB
for information on this event.