Version: unspecified (using KDE 4.7.4) OS: Linux A have a confgured and working IMAP account, the connection type is unencrypted/plain. The sieve server uses the same configuration. If I activate 'Server support sieve' and 'Reuse host and login configuration' in options in KMail's Setting/Accounts/Incoming/Filtering dialog, I always get the following notification on KMails startup: 'TLS encryption was requested but your Sieve server does not advertise TLS in its capabilities.You can choose to try to initiate TLS negotiations nonetheless, or cancel the operation. Start TLS nonetheless/Cancel' I have never had that notification with the same settings on the same account with Kmail1. Reproducible: Always Steps to Reproduce: Try to connect to a sieve server which needs plain,unencrypted login with unencrypted login settings using the login settings of an IMAP account. Actual Results: 'TLS encryption was requested but your Sieve server does not advertise TLS in its capabilities.You can choose to try to initiate TLS negotiations nonetheless, or cancel the operation. Start TLS nonetheless/Cancel' notification on KMails startup. Expected Results: Connect to the sieve server without any notification.
It's just a notification or you can't access to sieve server ?
Yes, I can access my sieve server, but: the point is that TLS is disabled in my IMAP account login configuration while the notification says 'TLS was requested'. It's nonsense. And it pops up every time I start KMail.
Ok it's notifucation bug. Will look at it soon. Thanks for info. Regards
if you can give me a screenshot it's more easy to search problem. Thanks
Created attachment 68164 [details] screenshot
Ok This messagebox is normal. I can't remove it but I can add a checkbox to disable this dialog for specific account. So you will see it once and if you click on button it will never see after for this account.
Checkbox can be a solution but why to notify the user who hasn't enabled any encryption in its login settings? In my opinion this message box pops up in the wrong place. It should only be pop up if a client configured to use TLS connects to a server that hasn't TLS. In my case there is no TLS configured neither on the client- nor on the server side.
Git commit c5d79f5c4ebb5b2fa12748a2bf87b35843c9c813 by Montel Laurent. Committed on 22/02/2012 at 08:58. Pushed by mlaurent into branch 'master'. Fix Bug 291849 - 'TLS encryption was requested' message with unencryted plain authentication login settings Don't ask all the time if we want to start tls encryption when server can use sieve without it FIXED-IN: 4.8.1 M +2 -2 libksieve/kmanagesieve/session.cpp http://commits.kde.org/kdepim/c5d79f5c4ebb5b2fa12748a2bf87b35843c9c813
Git commit fd41563a5863855ccfbe33297a1f3e74d12479b9 by Montel Laurent. Committed on 22/02/2012 at 08:58. Pushed by mlaurent into branch 'KDE/4.8'. Fix Bug 291849 - 'TLS encryption was requested' message with unencryted plain authentication login settings Don't ask all the time if we want to start tls encryption when server can use sieve without it FIXED-IN: 4.8.1 (cherry picked from commit c5d79f5c4ebb5b2fa12748a2bf87b35843c9c813) M +2 -2 libksieve/kmanagesieve/session.cpp http://commits.kde.org/kdepim/fd41563a5863855ccfbe33297a1f3e74d12479b9
Well, notification is not bugging me anymore but sending and downloading mails has been very slow since I've activated the checkbox. I'm not sure this is related to the original problem but I don't know how to go back to the original state. On the other hand I still don't understand why to start TLS on the client side (and notify about it) if I have NO TLS configured neither on the client nor the server-side? Is there a way to solve this by setting aside using TLS if it's not configured on the client side?