stalwartlabs
[enhancement]: Manage untrusted sieve from web client
Which feature or improvement would you like to request?
I'd like to see this feature: just like admins can manage global and trusted sieve scripts from the web client, users could do the same from the self-service portal to manage their own ("untrusted") scripts. An interface like Roundcube's Managesieve plugin would make it easier for all users, since it's user-friendly and also has the option to directly write the scripts.
Is your feature request related to a problem?
Managing sieve in a user-friendly way it's a PITA, e.g. Roundcube's solution is pretty good but I don't want to install a whole webmail just for this. There are more (third-party) alternatives, but if Stalwart could include one untrusted scripts, that would be awesome.
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
I second this, i cannot find a working sieve client that lets me connect this is major pain in my bumbum
@ruohki maybe have a look here http://sieve.info/
None of which work for me using a Windows pc without intensive fiddling.
Same here - when I try the managesieve CLI tool it claims to connect but I never get a prompt. There aren't any native OSX apps and the Thunderbird extension stopped working years ago.
Even a trivial form in the web UI that lets a user add a single, untrusted script would be a big improvement.
Fyi, there's sieve-connect which is a great CLI client for ManageSieve. You can view/edit/upload/check your sieve scripts to your server. But first, stalwartlabs/stalwart#548 needs to be solved.
@Megver83 thanks for the pointer.
Sieve-connect can at least connect, but right now it has some zany behaviour. Uploads claiming to fail, then the list command flaps between returning either no scripts or several prior "failed" uploads. I see @mdecimus has already committed a fix (thanks!) - will try this again when it gets into a release.
For 0.83+ the bug is fixed and sieve-connect now works. Bit clunky but then how often do you need to edit your ruleset.
How did you get any client to connect? On my setup, managesieve server only support OAUTHBEARER authentication method, and none of the client I've tried support this authentication method.
I wonder why all of the other protocols support plain login but ManageSieve doesn't ?
@X-Ryl669 just sieve-connect -u <myusername> --notlsverify. That's on Debian with sieve-connect 0.90. The --notlsverify is because it defaults to connecting to localhost and the cert won't match.