On 2009-05-22 martin f krafft <[email protected]> wrote:
> Package: swaks
> Version: 0+20061116.0-3
> Severity: minor
> Tags: upstream
> If the SMTP server announces itself as SMTP (vs. ESMTP), swaks
> should say HELO instead of EHLO. :)
> === Connected to localhost.
> <- 220 piper.oerlikon.madduck.net Python SMTP proxy version 0.2
> -> EHLO piper.oerlikon.madduck.net
> <** 502 Error: command "EHLO" not implemented
> -> HELO piper.oerlikon.madduck.net
> <- 250 piper.oerlikon.madduck.net
> Minor point, since it correctly falls back, but still.
[...]
Good Morning,
is this documented somewhere? Afaict according to rfc2821 the text
part of the inititial 220 message is purely informational, I canmnot
find a thing about parsing this response. However I do find "clients
SHOULD preferentially utilize EHLO rather than HELO.". And one of
the superseded rfcs, 1869, even includes this example:
C: <open connection to server>
S: 220 dbc.mtview.ca.us SMTP service ready
C: EHLO ymir.claremont.edu
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
