Software

Ask something
Discussion Locked

SMTP 503 Send hello first

0 helpful
4 replies

by Member 22772440

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My Environment: WIN2K Server - Running Exchange 2K

Recently I have had a very important client come to me and inform me that he is unable to send email to employees within my company. He is the only individual who has ever reported this problem. His problems are sporadic; sometimes he gets though and sometimes he doesn't. When he sends email he receives the following SMTP error:

Reporting-MTA: dns; ns1.rrpartners.com
Received-From-MTA: DNS; [192.168.9.112]
Arrival-Date: Tue, 18 Dec 2001 16:16:07 -0800

Final-Recipient: RFC822; user@riechesbaird.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 503 5.5.2 Send hello first
Last-Attempt-Date: Tue, 18 Dec 2001 16:16:10 -0800

Diagnostic-Code: SMTP 503 5.5.2 Send hello first

I would sincerely appreciate any possible recommendations for resolution to this matter. I have exhausted all of my resources to solve this problem. I have found little information on this specific error code.

Happy Holidays,

Trevor

4 replies

by brasslet

Normally this problem means the receiving system isn't really RFC compliant re: ESMTP but Exchange definitely is. My guess is still that your client's mail server has some 'issues' and that problem isn't yours (likely the client's system has problems with other mail servers as well, not just yours).

Here's something you can try that might alleviate the situation. Disable ESMTP on your Exchange server by editing the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIMC\Parameters. Add the DisableOutboundESMTP subkey, data type REG_DWORD and a value of 0x1. Then, stop and restart the Internet Mail Service. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q194132 for more info.

Diabling ESMTP won't cause you any grief, really. By doing this, systems that poorly implement ESMTP won't get confused. Hope this helps.

by brasslet

Whoops, the registry fix from above is for Exchange 5.5. For Exchange 2000, here's a cut and paste from the KnowledgeBase article from above:

In Exchange 2000, create an SMTP connector, and then configure the SMTP connector to use HELO instead ofEHLO in the advanced options:

Start System Manager; click Start , point to Programs , point to Microsoft Exchange , and then click System Manager .

Locate Connectors .

Right-click the SMTP connector, click Properties , and then click the Advanced tab.

To send the HELO start message and use standard SMTP and not extended SMTP, click Send HELO instead of EHLO

by Member 22772440

Thank you for your input on this and I sincerely appreciate your advise on this matter. I did however try this method prior to my Techrepublic submission and unfortunately, it did not solve my problem. I hate to write this off as one of those technology anomalies. I know there must be a valid reason why this is occurring. If you can think of anything else, please forward it my way.

Once again thank you.

This discussion is closed to new replies.