Outlooks EHLO does not follow the RFCs can it be changed?

[John W]

When Outlook connects to a mail server it does not send
out the correct EHLO in that it does not have a FQDN. Here
is the results from a transaction between Outlook and a
mail server.

EHLO LIGHTSPEED
MAIL FROM: <[email protected]>
RCPT TO: <[email protected]>
DATA - 41 lines, 1559 bytes.
QUIT

As you can see the EHLO is missing the domain. It should
be as follows.

EHLO LIGHTSPEED.somedomain.com
MAIL FROM: <[email protected]>
RCPT TO: <[email protected]>
DATA - 41 lines, 1559 bytes.
QUIT

Since Outlook is not following the RFCs some mail system
will refuse the mail for not using a FQDN. Other mail
clients work correctly why can't Outlook?

Is this just another case of MS not following the RFCs or
is there someway to get outlook to issue the correct
HELO/EHLO?

 

[Diane Poremsky [MVP]]

MUAs shouldn't have to pass a FQDN to the MSA, the MSA adds it when it
passes it to the MTA. MUAs really don't need to send EHLO either, since they
don't use protocol extensions, but they do. A proper EHLO *is* important
when two SMTP servers are talking and many MTAs will rightly refuse to
accept mail without a FQDN but the MSA that accepts mail from a MUA must
ensure that all domains are FQ before relaying it to the MTA (2476).


--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Author, Google and Other Search Engines (Visual QuickStart Guide)



Join OneNote Tips mailing list: http://www.onenote-tips.net/

Vote for your favorite Outlook and Exchange utilities in the
Slipstick Ratings Raffle at http://www.slipstick.com/contest/