subject:"\[kmail2\] \[Bug 328246\] Manage Sieve scripts feature broken"

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2017-01-18 Thread Denis Kurz

https://bugs.kde.org/show_bug.cgi?id=328246 Denis Kurz changed: What|Removed |Added Latest Commit|http://commits.kde.org/libk |https://phabricator.kde.org

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2017-01-18 Thread Tom Mittelstädt

https://bugs.kde.org/show_bug.cgi?id=328246 --- Comment #18 from Tom Mittelstädt --- it is still broken in 5.2.3 -- You are receiving this mail because: You are watching all bug changes.

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2017-01-18 Thread Denis Kurz

https://bugs.kde.org/show_bug.cgi?id=328246 Denis Kurz changed: What|Removed |Added Version|4.12 pre|5.1.3 CC|

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2016-07-14 Thread David Faure via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=328246 --- Comment #16 from David Faure --- I can't possibly know that :) If you see "KTcpSocket::showSslErrors" in the *kmail* debug output, then it's likely that this patch fixes it. -- You are receiving this mail because: You are watching

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2016-07-14 Thread Tom Mittelstädt via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=328246 --- Comment #15 from Tom Mittelstädt --- Does this also fixes the issues with dovecot (2.2.10)? at the moment (kmail2 5.1.3) I have the sames issues as in #1. A workaround is to restart kmail completely and right afterwards

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2016-07-14 Thread David Faure via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=328246 --- Comment #14 from David Faure --- Fix available at https://phabricator.kde.org/D2167 -- You are receiving this mail because: You are watching all bug changes.

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

2016-07-14 Thread David Faure via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=328246 --- Comment #13 from David Faure --- OK the actual issue is elsewhere. Things are happening out of order, sometimes (race condition). KManageSieve::SessionThread::doStartSsl: 0x3aa7f00 SessionThread::doStartSsl()