[jira] [Updated] (JAMES-4207) ManageSieve sends capabilities after every AUTH

     [ https://issues.apache.org/jira/browse/JAMES-4207?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix updated JAMES-4207:
-------------------------
    Summary: ManageSieve sends capabilities after every AUTH  (was: ManageS=
ieve sends AUTHENTICATE)

> ManageSieve sends capabilities after every AUTH
> -----------------------------------------------
>
>                 Key: JAMES-4207
>                 URL: https://issues.apache.org/jira/browse/JAMES-4207
>             Project: James Server
>          Issue Type: Bug
>    Affects Versions: master
>            Reporter: Felix
>            Priority: Major
>             Fix For: master
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> James sends ManageSieve capabilities after every successful AUTHENTICATE =
command.
> This was introduced with [https://github.com/apache/james-project/commit/=
1819fddf13c88476a0766ccc91c81d66d14da682].
> =C2=A0
> However, the relevant RFC (5804, section 4) states:
> {code:java}
>     response-authenticate =3D *(string CRLF)
>                             ((response-ok [response-capability]) /
>                              response-nobye)
>                             ;; <response-capability> is REQUIRED if a
>                             ;; SASL security layer was negotiated and
>                             ;; MUST be omitted otherwise.{code}
> I think that all authentication mechanisms supported by James (PLAIN, LOG=
IN, XOAUTH2, OAUTHBEARER) do not negotiate a SASL layer.
> The server must therefore omit the capabilities.
> There was a similar discussion here: [https://github.com/thsmi/sieve/issu=
es/480]
> I can confirm that the Roundcube webmail client does not expect capabilit=
ies and fails to use managesieve with James.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)