Peter Bowen <pzbowen(_at_)gmail(_dot_)com> wrote:
I've been working on implementing a framework for building SMTP
servers in ruby (https://github.com/pzb/groat-smtpd). One of the
issues I've run into several times is interoperability of the LOGIN
mechanism with various clients. The latest problem is certain
Microsoft SMTP implementations that send an initial client response,
and have major issues when it is not accepted. Is there any reliable
specification for the LOGIN mechanism and/or how it is used with SMTP?
My understanding of LOGIN comes from
http://exim.org/exim-html-current/doc/html/spec_html/ch34.html#SECID173
Exim's authentication configuration is rather runic but it should be
fairly clear.
Exim's plaintext authenticator allows clients to use LOGIN as if it were
PLAIN with an empty authorization identity, or to send the username as the
initial response and password as a second response, or to send no initial
response and separate username and password responses.
I have never seen a client that depends on seeing AUTH=LOGIN in the EHLO
service extensions list, nor have I heard of any interop problems caused
by Exim not advertising AUTH=LOGIN.
Tony.
--
f.anthony.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in
Rockall and Malin, veering west or northwest 4 or 5, then backing southwest 5
or 6 later. Rough or very rough. Occasional rain. Moderate or good,
occasionally poor.