Bug 312923 - Server side errors not visualized when managing sieve scripts
Summary: Server side errors not visualized when managing sieve scripts
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: sieve (show other bugs)
Version: 4.9.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-09 06:56 UTC by Christian Reiner
Modified: 2013-01-09 15:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.10


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Reiner 2013-01-09 06:56:58 UTC
I just found out about the reason a problem I faced for several weeks: 
When managing my personal sieve scripts using kmail2s interface I always got a "Error unknown" whatever I tried. Managing the scripts had worked before, actually I setup the scripts using kmail2s interface. I failed to find out what the actual problem is. 
Today I finally used 'sieveshell' to give it another try and was presented a clear and easy to understand error, when trying to upload a modified script: "you are only allowed to setup 5 scripts."

Wow. Ok, that is something that actually helps!
1.) I know what the problem is
2.) is was a question of seconds to fix the problem
3.) I was able to manage my scripts again
So my question is: why does kmail2 not display that error message? Why the "Error unknown"?

Reproducible: Always

Steps to Reproduce:
1. Use a cyrus imap account and maintain sieve scripts, more than are actually allowed on the server
2. Try to make _any_ modifications to the existing sieve scripts using kmail2s script manager
3. Shake your head at the great error message you get
Actual Results:  
I get a meaningless error message: "Error unknown" for whatever modification I try, except activating a script or another. 

Expected Results:  
I would expect to get the error message the server generates. This is what error messages are there for. It actually sometimes helps users to give them the error message.
Comment 1 Laurent Montel 2013-01-09 08:10:25 UTC
not good.
But sieve doesn't report error here... and I don't have server which has this error...
Comment 2 Christian Reiner 2013-01-09 08:14:10 UTC
The number of scripts a user can maintain in his personal area is controlled by the configuration option 'sieve_maxscripts' in file /etc/imapd.conf. This is if you use the cyrus implementation. Maybe your server has a higher limit you don't reach?
Comment 3 Laurent Montel 2013-01-09 15:25:57 UTC
Git commit 2d178ae5d11f87b3722420282bc65f89c79d39d9 by Montel Laurent.
Committed on 09/01/2013 at 16:24.
Pushed by mlaurent into branch 'KDE/4.10'.

Fix Bug 312923 - Server side errors not visualized when managing sieve

scripts

Thanks Christian Reiner to help me it.
FIXED-IN: 4.10

M  +2    -1    libksieve/kmanagesieve/sievejob.cpp

http://commits.kde.org/kdepim/2d178ae5d11f87b3722420282bc65f89c79d39d9