I read the RFC and I've not found anything saying there are problems
offering the AUTH keywords in the EHLO response when authentication is not
required.
The "250-AUTH" answers simply says that the server correctly handle a set of
SMTP commands: they doesn't imply that the server really supports user
authentication.
Stefano
> > Such behaviour can be attained just changing four "if
> > (authRequired) {...}" statements to "if (true) {...}" in
> > SMTPServer.doHelo(String) and SMTPServer.doEhlo(String).
> >
> > Does anybody know if doing this simple change would create any
> > problem? Should we make this behaviour optional?
> >
> > Vincenzo
>
> I didn't read the RFC about EHLO "AUTH" extension and its
> behaviour. IMHO this changed behaviour should not break
> anything but I will look into the specification if noone has
> knowledge about this.
>
> Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]