>Since it's against the RFC, we not going to be making that kind of >change to the Exim code. We're following the guidelines and so are 99.9% >of the other SMTP speakers out there. STARTTLS is an Extended SMTP verb >and as such is restricted to programs talking ESMTP. Computers aren't as >smart as us and as a result we need to give them clear and well defined >rules of engagement. Screwing with the just means Skynet is one day >closer :P
>I'd suggest the best path would be get the client that's misbehaving to >fix it's behaviour. >Past that, start hacking code and roll your own Exim. Since I haven't found clear indication in the RFCs whether this is a strict requirement I wasn't sure if there is a way to do this with exim. I found in RFC 1869, SMTP Service Extensions: "A client SMTP supporting SMTP service extensions should start an SMTP session by issuing the EHLO command instead of the HELO command." "should start a session" is not required. So I'm not sure if this behaviour is against the RFCs. Nevermind, I will try to get the peer host to issue a EHLO. Thanks for your help. -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
