| Summary: | Manage Sieve: problems with Capability-Response afer STARTTLS | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Thomas Dreßler <thomas.dressler> |
| Component: | sieve | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | andrew.crouthamel, krah.tm |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
I can confirm this bug too. Using telnet it works like a charm, kio sieve slave fails like described above. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! I'll try to test that asap - moved away using kmail / ksieve long time ago because it did not work and there was no Exchange Web Services (EWS) support in kmail for a long time in contrast to e.g. evolution. I'll try to setup a VM with kmail + kio-sieve and test it - luckily my sieve server side is still there :D Would the versions from Kubuntu 18.10 be sufficient to test with? That would be great, thanks. I've tested it with current Kubuntu 18.10 using Kontact 5.8.3 and KDE Frameworks 5.50.0. Sieve does work - i can see my script on the server, so this is fixed, at least for me :). kio-sieve package used was this: https://ubuntu.pkgs.org/18.10/ubuntu-universe-amd64/kio-sieve_18.04.3-0ubuntu2_amd64.deb.html Thanks for the update! |
Version: (using KDE 3.5.9KDE 3.5.6KDE 1.2KDE 1.2) Installed from: Debian stable PackagesDebian stable PackagesDebian testing/unstable PackagesDebian stable Packages OS: Linux hi! manage sieve server must send after "TLS negotiation" an capability-response. if he do it, the client (kmail/kio) have problems with following commands (AUTHENTICATE). draft-martin-managesieve-08.txt: 2.2. STARTTLS Command Support for STARTTLS command in servers is optional. Its availability is advertised with "STARTTLS" capability as described in section 1.8. The STARTTLS command requests commencement of a TLS negotiation. The negotiation begins immediately after the CRLF in the OK response. After a client issues a STARTTLS command, it MUST NOT issue further commands until a server response is seen and the TLS negotiation is complete. The STARTTLS command is only valid in non-authenticated state. The server remains in non-authenticated state, even if client credentials are supplied during the TLS negotiation. The SASL [SASL] EXTERNAL mechanism MAY be used to authenticate once TLS client credentials are successfully exchanged, but servers supporting the STARTTLS command are not required to support the EXTERNAL mechanism. After the TLS layer is established, the server MUST re-issue the capability results, followed by an OK response. This is necessary to protect against man-in-the-middle attacks which alter the capabilities list prior to STARTTLS. This capability result MUST NOT include the STARTTLS capability. The client MUST discard cached capability information and replace it with the new information. The server MAY advertise different capabilities after STARTTLS. Example: C: StartTls S: oK <TLS negotiation, further commands are under TLS layer> S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "SASL" "PLAIN DIGEST-MD5 GSSAPI" S: "SIEVE" "fileinto vacation" S: ok