[Bug 159205] New: manage sieve: AUTHENTICATE failed

[Thomas Dreßler]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=159205         
           Summary: manage sieve: AUTHENTICATE failed
           Product: kmail
           Version: unspecified
          Platform: Debian stable
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs kde org
        ReportedBy: thomas.dressler 1und1 de


Version:            (using KDE 3.5.9)
Installed from:    Debian stable Packages
OS:                Linux

hi!

kmail/kio have problems with AUTHENTICATE:
(1) during the authenticate-command the server can send his responses as quoted-string or literal. the client have problems with quoted-strings.
(2) the client ignore the capability-response and send an AUTHENTICATE "LOGIN" also if the server don't support it.
(3) the client don't connect to servers wich capability-response includes somthing kike this:
"IMPlemENTATION" "Example1 ManageSieved v001"
the capability-name is case-insensitive.

draft-martin-managesieve-08.txt:
1.8:
Server capabilities are sent by the server upon a client connection.
Clients may request the capabilities at a later time by issuing the
CAPABILITY command described later. The capabilities consist of a
series of lines each with one or two strings. The first string is
the name of the capability, which is case-insensitive. The second
optional string is the value associated with that capability.
Order of capabilities is arbitrary, but each capability name can
appear at most once.

2.1:
...
The authentication protocol exchange consists of a series of server
challenges and client responses that are specific to the selected
authentication mechanism.  A server challenge consists of a string
(quoted or literal) followed by a CRLF. The contents of the string
is a base-64 encoding [BASE64] of the SASL data. A client response
consists of a string (quoted or literal) with the base-64 encoding
of the SASL data followed by a CRLF. If the client wishes to cancel
the authentication exchange, it issues a string containing a single
"*". If the server receives such a response, it MUST reject the
AUTHENTICATE command by sending an NO reply.
...