Q
Problem solve Get help with specific problems with your technologies, process and projects.

MS Exchange Transport errors

Since April 3, I've been getting the following MS ExchangeTransport Event ID 7010 error in the application log of our Exchange 2k3 server with Exchange 2k3. I can't seem to resolve the problem.

This is an SMTP protocol log for virtual server ID 1, connection #1640. The client at "xxx.xxx.xxx.xxx." sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first." The full command sent was "xexch50 2256 2". This will probably cause the connection to fail.

I've looked at the MS link, and have tried everything suggested; including setting the NIC manually rather than automatically. All the patches are up to date, and mail seems to be working fine. However I cannot use the cmdprmt telnet test even within the LAN. The only machine it works from is the server itself. The number of servers trying to connect is limited that I seem to get the error on. It's making me nervous though. This is an SMTP protocol log for virtual server ID 1, connection #1503. The client at "201.1.124.60" sent a "rcpt" command, and the SMTP server responded with "550 5.7.1 Unable to relay for echo@chuansheng.com." The full command sent was "rcpt TO: echo@chuansheng.com." This will probably cause the connection to fail. I interpret this as an attempt to relay mail thru our server. The SMTP log seems to indicate that the connection simply drops. I've tried to simply get rid of the error by turning the MSExhangeTransport logging level to minimum but I 'm still getting them.

Since April 3, I've been getting the following MS ExchangeTransport Event ID 7010 error in the application log of our Exchange 2k3 server with Exchange 2k3. I can't seem to resolve the problem.

This is an SMTP protocol log for virtual server ID 1, connection #1640. The client at "xxx.xxx.xxx.xxx." sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first." The full command sent was "xexch50 2256 2". This will probably cause the connection to fail.

I've looked at the MS link, and have tried everything suggested; including setting the NIC manually rather than automatically. All the patches are up to date, and mail seems to be working fine. However I cannot use the cmdprmt telnet test even within the LAN. The only machine it works from is the server itself. The number of servers trying to connect is limited that I seem to get the error on. It's making me nervous though.

This is an SMTP protocol log for virtual server ID 1, connection #1503. The client at "201.1.124.60" sent a "rcpt" command, and the SMTP server responded with "550 5.7.1 Unable to relay for echo@chuansheng.com." The full command sent was "rcpt TO: echo@chuansheng.com." This will probably cause the connection to fail.

I interpret this as an attempt to relay mail thru our server. The SMTP log seems to indicate that the connection simply drops. I've tried to simply get rid of the error by turning the MSExhangeTransport logging level to minimum but I 'm still getting them.

If the remote host is not a part of your Exchange org or a known mail host (perhaps a partner?) that you want to exchange mail with, you don't need to worry about this.

The remote host is trying to using the XEXCH50 ESMTP verb which requires authentication. If you need to allow that, I'd recommend you setup a separate SMTP virtual server for the partner (at each end) and configure it to authenticate.

Dig Deeper on Exchange Server setup and troubleshooting

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchServerVirtualization

SearchCloudComputing

SearchSQLServer

SearchEnterpriseDesktop

SearchVirtualDesktop

Close