[kimap] [Bug 449184] Connection fails because the CAPABILITY command is sent before the server greeting arrived

[Fabian Vogt]

https://bugs.kde.org/show_bug.cgi?id=449184

Fabian Vogt <fabian at ritter-vogt.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://invent.kde.org/pim/
                   |                            |kimap/commit/dbcedd5aaab1a4
                   |                            |e691966d1e37de1a0b413ca605
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Fabian Vogt <fabian at ritter-vogt.de> ---
Git commit dbcedd5aaab1a4e691966d1e37de1a0b413ca605 by Fabian Vogt.
Committed on 27/01/2022 at 13:23.
Pushed by fvogt into branch 'release/21.12'.

Handle pure SSL/TLS negotation in Session instead of LoginJob

Previously, LoginJob started the SSL negotiation and immediately sent the
CAPABILITY command once it completed, without waiting for the server greeting
first. Some servers don't like this any close the connection with
* BYE out-of-sync data before server greeting

Avoid this by starting the encryption in Session directly, which then starts
LoginJob after the server greeting arrived. Adjust LoginJob for this by
treating an already encrypted connection like a successful negotation, and
avoid handling the encryptionNegotiationResult signal before the job was
started.

M  +7    -5    src/loginjob.cpp
M  +1    -1    src/session.cpp

https://invent.kde.org/pim/kimap/commit/dbcedd5aaab1a4e691966d1e37de1a0b413ca605

-- 
You are receiving this mail because:
You are the assignee for the bug.