Felix Auringer created JAMES-4232:
-------------------------------------
Summary: James sends invalid SMTP AUTH ehlo line
Key: JAMES-4232
URL: https://issues.apache.org/jira/browse/JAMES-4232
Project: James Server
Issue Type: Bug
Components: SMTPServer
Reporter: Felix Auringer
Assignee: Felix Auringer
>From the mailing list:
I noticed that James sends its authentication mechanisms for SMTP twice, once
with a space and once with an equal sign:
220 Hello from <my domain>
ehlo example.internal
250-<my domain> Hello example.internal [84.186.194.95])
250-AUTH OAUTHBEARER XOAUTH2
250-AUTH=OAUTHBEARER XOAUTH2
250-PIPELINING
250-ENHANCEDSTATUSCODES
250 8BITMIME
```
As far as I understand, this is not compliant with the RFC
([https://www.rfc-editor.org/info/rfc5321/#section-4.1.1.1]):
ehlo-ok-rsp = ( "250" SP Domain [ SP ehlo-greet ] CRLF )
/ ( "250-" Domain [ SP ehlo-greet ] CRLF
*( "250-" ehlo-line CRLF )
"250" SP ehlo-line CRLF )
ehlo-line = ehlo-keyword *( SP ehlo-param )
The only character allowed to follow directly after the ehlo keyword (AUTH) is
a space.
I am also not entirely sure whether sending the same ehlo keyword twice is
allowed.
We use one client that can not handle the line with the equal sign:
[https://github.com/simonrob/email-oauth2-proxy/blob/6599460ef7ea99a0ca9515d2457d1666cccb965a/emailproxy.py#L2334]
(admittedly, this is an unusual one).
But other large email servers like Google or Microsoft only announce their
authentication mechanisms once and without the equal sign.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
