Michael J. Tubby B.Sc. G8TIC [mike.tubby@???] wrote:
> It looks like a "broken" MTA to me, here's a standard SMTP HELO:
>
> [mike@gate mike]$ telnet mail.letec.co.uk 25
> Trying 194.129.189.164...
> Connected to mail.letec.co.uk.
> Escape character is '^]'.
> 220 fndexch001.foundation Mail essentials server (2.422) ready for ESMTP
> transfer
> helo gate.thorcom.com
> 250 Hello> GATE.THORCOM.COM You are from : 212.172.148.2
>
>
> here's an EHLO followed by a MAIL command:
>
> [mike@gate mike]$ telnet mail.letec.co.uk 25
> Trying 194.129.189.164...
> Connected to mail.letec.co.uk.
> Escape character is '^]'.
> 220 fndexch001.foundation Mail essentials server (2.422) ready for ESMTP
> transfer
> EHLO gate.thorcom.com
> 502
> mail from: mike@???
[...]
Wait a minute, 502 means the command is not implemented, so you cannot just
carry on if the server gives you a 502 to your ehlo. RFC 1869 states:
If the server SMTP recognizes, but does not implement, the
EHLO command, it will return code 502.
[...]
In the case of any error response, the client SMTP should
issue either the HELO or QUIT command
Or am I missing the point here?
-- Kilian
