[
https://issues.apache.org/jira/browse/IMAP-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer resolved IMAP-304.
--------------------------------
Resolution: Fixed
done :)
> Add support for LOGINDISABLED and AUTH=PLAIN
> --------------------------------------------
>
> Key: IMAP-304
> URL: https://issues.apache.org/jira/browse/IMAP-304
> Project: JAMES Imap
> Issue Type: Bug
> Affects Versions: 0.2-M1
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.2
>
>
> We need to add support for LOGINDISABLED and AUTH=PLAIN to be 100% rfc3501
> conform:
> From the rfc:
> 7.2.1. CAPABILITY Response
> Contents: capability listing
> The CAPABILITY response occurs as a result of a CAPABILITY
> command. The capability listing contains a space-separated
> listing of capability names that the server supports. The
> capability listing MUST include the atom "IMAP4rev1".
> In addition, client and server implementations MUST implement the
> STARTTLS, LOGINDISABLED, and AUTH=PLAIN (described in [IMAP-TLS])
> capabilities. See the Security Considerations section for
> important information.
> A capability name which begins with "AUTH=" indicates that the
> server supports that particular authentication mechanism.
> The LOGINDISABLED capability indicates that the LOGIN command is
> disabled, and that the server will respond with a tagged NO
> response to any attempt to use the LOGIN command even if the user
> name and password are valid. An IMAP client MUST NOT issue the
> LOGIN command if the server advertises the LOGINDISABLED
> capability.
> ....
> ....
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
