The "Manage Sieve Scripts" doesn't manage to download any Sieve scripts. Reproducible: Always Steps to Reproduce: 1. open Settings -> Manage Sieve Scripts 2. wait for it to load the scripts Actual Results: There is a spinner showing up on all mail accounts, indicating that it actually does something, but the result is empty. Expected Results: My Sieve scripts (which I have edited before with KMail2) should appear in the list so they can be edited. Haven't used this feature in quite a while so I don't know when it broke. It was definitely working a year ago or so. Now, trying with 4.12 beta it's not working any more.
Do you have debug version ? (you have a menu entry to debug sieve in tools menu in kmail Or do you test your server on thunderbird for example ?
(In reply to comment #1) > Do you have debug version ? (you have a menu entry to debug sieve in tools > menu in kmail No, I don't have that. > > Or do you test your server on thunderbird for example ? I have tested the server with roundcube. I can sucessfully edit the sieve filter there.
rouncube is a test valid. I need to know if you can edit it in a application. Use same settings etc. Look at your port etc. Perhaps that your port is not ok
So ?
w
wait for info
Yes, I've installed thunderbird and the Sieve plugin and that worked fine too. However, in the meantime I've upgraded my KDE installation (Kontact Version 4.12 rc1) and turns out it works again. No idea what it didn't connect with the betas.
Ok so bug is fixed. It's good to close bug too when user can't reproduce it. Regards.
Still present in kmail2 5.1.3 sieve scripts are only discovered if kmail is freshly startet exactly one time. If I access the dialog a second time kmail tries forever to get the script list. it works again after a kmail-restart Same if the syntax check detects an error. the whole sieve management part becomes unresponsive and does simply nothing until kmail is restarted
Ok I see the bug. I investigate it
Git commit aa295b6cf15ee67a980b2858ccad6e6e8e769585 by Montel Laurent. Committed on 02/05/2016 at 07:13. Pushed by mlaurent into branch 'Applications/16.04'. Fix Bug 328246 - Manage Sieve scripts feature broken FIXED-IN: 5.2.1 M +1 -0 src/kmanagesieve/sessionthread.cpp http://commits.kde.org/libksieve/aa295b6cf15ee67a980b2858ccad6e6e8e769585
This patch was reverted, it broke other servers, reopening. Looking at this code, I found another issue though, maybe it fixes this? https://phabricator.kde.org/D2163
OK the actual issue is elsewhere. Things are happening out of order, sometimes (race condition). KManageSieve::SessionThread::doStartSsl: 0x3aa7f00 SessionThread::doStartSsl() KManageSieve::SessionThread::doSendData: 0x3aa7f00 C: "LISTSCRIPTS" [....] KManageSieve::SessionThread::doSendData: 0x3aa7f00 C: "AUTHENTICATE \"PLAIN\" [...]\"" KManageSieve::SessionThread::slotDataReceived: 0x3aa7f00 S: "NO \"Authenticate first\"" This LISTSCRIPTS should only happen after authenticate, not before. I sometimes see a race condition the other way around, m_state in Session is not yet PostTls so all responses are unhandled, and only then sslDone() is called.
Fix available at https://phabricator.kde.org/D2167
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 the manage sieve functionality works once.
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.
(In reply to David Faure from comment #14) > Fix available at https://phabricator.kde.org/D2167 I'm not quite sure, but this patch seems to have landed some time ago. Can this bug be closed FIXED?
it is still broken in 5.2.3
In the meantime, I managed to extract the information from phabricator*: The earliest stable version the above patch was 16.08.0 (5.3.0), so it's no surprise that it isn't fixed in 5.2.3. So there's a good chance that the bug was actually fixed. I adjusted the version-fixed-in and latest-commit info. Also, thank you for reporting back, and so fast. If it's still broken in post-5.3.0 versions, please tell me so and I'll reopen. * fyi: the phabricator page lists all tags that include the patch, and 16.08.0 is listed there, among others