Hello,
should exim support receiving a STARTTLS *before* receiving an EHLO?
openssl s_client -connect ssl.schlittermann.de:25 -starttls smtp
ends with error:
T 212.80.235.130:25 -> 10.10.10.6:1411 [AP]
220 pu.schlittermann.de ESMTP Exim 4.60 Tue, 07 Feb 2006 11:39:48 +0100..
T 10.10.10.6:1411 -> 212.80.235.130:25 [AP]
STARTTLS..
T 212.80.235.130:25 -> 10.10.10.6:1411 [AP]
503 STARTTLS command used when not advertised..
T 212.80.235.130:25 -> 10.10.10.6:1411 [AP]
501 NULL characters are not allowed in SMTP commands..
since exim expects EHLO first. Other SMTP servers don't. (Try mail.web.de.)
Is this (exims) behaviour just a missing feature oder standard/RFC
compliance? (a short look into RFC2487 just showed me an example with
connect -> EHLO -> STARTTLS, but no hint if this is required.)
Best regards from Dresden
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann HS12-RIPE -----------------------------------------
gnupg encrypted messages are welcome - key ID: 48D0359B ---------------
gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B -
