similar to: Exposing global (default) sieve script through Managesieve

With all the mess that my email has become, it makes sense for me to try to make use of Sieve, but I'm having quite the time finding out how to make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to be compiled with it. I can access managesieve, and I have set up dovecot.conf with lda. I do not get a NO response when I PUTSCRIPI, but LISTSCRIPTS produces no result, so I

I do have two questions related to the managesieve setup in dovecot 1) I did setup a global sieve filter, that is invoked if a user has no other sieve filter. If a user installs a sieve filter and activates it (PUTSCRIPT, SETACTIVE) then the sieve filter gets compiled (.sievec) and deliver does use it. If I want to deactivate the filter (SETACTIVE "") only the symlink (to the .sieve

hi all edit via vi editor to change dovecot.sieve and enotify works fine.but when I telnet 4190 port via managesieve to edit it with the same code,the managesieve said "NO "Error in MANAGESIEVE command CHECKSCRIPT: "", find many topic in wiki and maillist but not solved. need you help!thanks!!dovecot version 2.2.15,pigonhole version 0.4.4 here are more infos

Is there some simple textual frontend to the ManageSieve protocol somewhat easier to use than gnutls-cli? I.e. something to use like managesieve -u ef putscript myscript < /tmp/myscript Password: managesieve -u ef setactive myscript Password: simply doing the TLS authentication and length computation for me.

Hello! I'm trying for a lot of time to make managesieve working with dovecot 1.1.17 and virtual users on openSuSE 11.1. I think I'm doing some misconfiguration, but I can't figure it out. Perhaps it's something with the paths to the sieve scripts? In dovecot.conf I find in the comments: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ protocol

Hi Stephan, > Normally, Dovecot permission errors are more helpful than that. So, > this > error message in itself is a bit of a bug: I'm glad to h've been able to help with this beta-test ;-) > About the cause of this error: keep in mind that the whole directory > path needs read/execute permission, not only the leaf directory. Have checked. They are... > You

Hello there, I have been using pysieved and avelsieve and it has been working great. I decided to do test with the ManageSieve patch and got this problem: Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using active sieve script path: ~/.dovecot.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using sieve script storage directory: ~/.sieve Nov 27

Hi, new to Dovecot, forgive me if I'm missing something basic... I'm trying to figure out if there's a way to use a couple of custom rules alongside ManageSieve. Most of the time I like the ManageSieve interface in Roundcube, but there's one rule that I can't get it to do the way I want (it's a notify rule, and I don't like the way Roundcube constructs the notify). I

Hi! I've got a segfault in managesieve while using: sieve_extensions = -vacation -reject -spamtest -virustest -enotify -redirect The problem seems to lie in "-redirect". Reason for excluding "redirect" from sieve is my users should not use sieve to forward or redirect mails but use an external method (web-script to set LDAP attribute) which checks several things like

Hello, I'm testing dovecot replication alongside pigeonhole and liking it. Dovecot v2.2.13 Pigeonhole v0.4.3 If I create or edit a sieve script on one server (via managesieve, using the thunderbird plugin as it happens) then it does get replicated to the other - great! However, if I set a script to be active (SETACTIVE) on one side then this is not being replicated across to the other

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, well, I'm sort of sure that this was raised in the past, but I do not find the patch / answer of it: I'm running dovecot v1.0.15 from hg (5567:568687e4df02) with managesieve patch v9.2 (there is one change between this and v9.3 except in regards of AUTH so this should not matter.) and dovecot-sieve v1.0.3. When an user issues just

Hello, I'm using dovecot 2.2.10 and roundcube (with managesieve enabled). Sieve filtering works well, as long the rule is written into ~/.dovecot.sieve (which is a link to ~/sieve/managesieve.sieve) When adding a new filter set (in roundcube) the script is written to ~/sieve/newfilterset.sieve. This script will not be executed. How can I solve this? I set sieve_dir = ~/sieve This should work,

Hi, I am trying to get sieve working on a new OpenSuse leap 42.2 install. On my 'old' OpenSuse 13.2 machine it worked fine. The problem is that Managesieve can't access the script store and won't let me create any script. It says permission denied on ~/sieve directory. See log below. I 've activated debug logging, but that doesn't give any clues to me. Also, I've

I am using Dovecot 2.0.15 on Arch. I have cloned the hg repo and compiled the plugin using the following options: ./configure --with-dovecot=/usr/lib/dovecot --with-pigeonhole=/usr/include/dovecot/sieve/ The relevant section of my dovecot.conf looks like: plugin { sieve = ~/.dovecot.sieve sieve_global_path = /home/vmail/globalsieverc sieve_dir = ~/ sieve_plugins = sieve_pipe #

Hi again everyone, So I've finally got sieve integration happening on my? REHL Postfix/Dovecot server, with private user scripts happily running when users create them. (we user SquirrelMail, so the avelsieve plugin runs the sieve integration). Now I'd like to utilise additional per-user scripts (probably via sieve_before), but I've not been able to get my additional scripts to

Also, please provide an example scenario; i.e., for one problematic delivery provide: - The values of the variables substituted in the dovecot-lda command line; i.e., provide that command line. - The incoming e-mail message. Regards, Stephan. Op 19-10-2016 om 12:43 schreef Matthew Broadhead: > dovecot is configured by sentora control panel to a certain extent. if > you want those

hello folks hello Timo hello all the guru I met a few times the problem or an email that passes through a sieve script is silently discard after delivery but never returned to the inbox all testimonials are welcome -- ?http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7 ?gpg --keyserver pgp.mit.edu --recv-key 092164A7 -------------- next part -------------- A non-text attachment

Op 2/5/2017 om 8:53 PM schreef dovelist: > Hi, > > I am trying to get sieve working on a new OpenSuse leap 42.2 install. > On my 'old' OpenSuse 13.2 machine it worked fine. > > The problem is that Managesieve can't access the script store and > won't let me create any script. It says permission denied on ~/sieve > directory. See log below. I 've

Could you send your configuration (output from `dovecot -n`)? Also, please provide an example scenario; i.e., for one problematic delivery provide: - The values of the variables substituted below. - The incoming e-mail message. - The Sieve script (or at least that vacation command). Regards, Stephan. Op 19-10-2016 om 11:42 schreef Matthew Broadhead: > hi, does anyone have any ideas

Am 14.05.2020 um 00:22 schrieb Benny Pedersen: > On 2020-05-14 00:14, Anton Blau wrote: > >> What can I do to get connect from Roundcube to dovecot-managemsieve? > > if roundcube is installed on same server as dovecot then disable ssl > in roundcube managesive plugin as same way for imap and submission/smtps > > Thank you for your very fast answer. There are two virtual