You need to know which socketerror it is. If you enable verbose logging on the connector, the error number is one of the fields.
From: [email protected] [mailto:[email protected]] On Behalf Of James Hill Sent: Thursday, December 18, 2014 7:55 PM To: [email protected] Subject: [Exchange] Exchange 2013 application relay issue I'm currently investigating an issue for a client with Exchange 2013. They have a single Exchange 2013 SP1 server running in a 2012 R2 VM on 2012 R2 Hyper-V Host. I have configured a receive connector (Apprelay) that allows their LOB app (a payroll program) to send out emails. >From time to time the LOB app crashes while attempting to send out emails via >the Apprelay connector. After restarting the LOB app it still isn't able to >send emails. However, restarting the Exchange Transport service temporarily >resolves the issue. When it fails the SMTP log on the exchange server shows a socket error:- 250 2.1.5 Recipient OK DATA 354 Start mail input; end with <CRLF>.<CRLF> Remote(SocketError) I'm not sure where to look for the cause from here. Network layer? Suggestions please? James.
