search for: sieve_before

Hi All, I cannot get the sieve_before to work. I have dovecot & sieve installed on Debian 7 as follows /etc/dovecot/conf.d/90-sieve.conf : plugin { # The path to the user's main active script. If ManageSieve is used, this the # location of the symbolic link controlled by ManageSieve. sieve = ~/.dovecot.sieve # The def...

On 03/21/2017 09:06 AM, chaouche yacine wrote: > Hi Ger, > > sieve_before should be a path to sieve script file, not to a directory. > in your configuration, you set sieve_before to /var/lib/dovecot/sieve/before which is a directory. I don't get that reading: https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration Either file or directory. If a file, it search...

...o 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 execute. I am doing the following: a) getting avelsieve to write my redirect script (ie. logging on as user, completing private script wizard, and activating it) b) compiling .dovecot.sieve with sievec c) copying the resultant .dovecot....

...y own rules in Roundcube's file or it gets really confused. I tried adding an include to the generated file, but Roundcube politely removes it for me the next time I use the rule editor. (Squirrelmail doesn't seem to be any better in this regard.) I thought I could do something like sieve_before = ~/sieve/custom.sieve but that doesn't seem to work. I couldn't even see any evidence in the log that it attempted to look at that file. Apparently sieve_before isn't meant to work on a per-user basis. If I do a global sieve_before, can I have it "include :personal"? If...

...gt;> To:Ger Hooton Scoil Chro? ?osa Blarney [ghooton at scins.ie ], >>> dovecot at dovecot.org Date:Tue, 21 Mar 2017 13:06:14 +0000 (UTC) >>> ------------------------------------------------- >>> >>> >>>> Hi Ger, >>>> >>>> sieve_before should be a path to sieve script file, not to a directory. >>>> in your configuration, you set sieve_before to >>>> /var/lib/dovecot/sieve/before which is a directory. >>>> >>>> what you need to do is figure out which sieve script you'd like &...

On 03/21/2017 11:32 AM, chaouche yacine wrote: >> On Tuesday, March 21, 2017 3:03 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: >> On 03/21/2017 09:06 AM, chaouche yacine wrote: >>> Hi Ger, >>> >>> sieve_before should be a path to sieve script file, not to a directory. >>> in your configuration, you set sieve_before to /var/lib/dovecot/sieve/before which is a directory. >> I don't get that reading: >> https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration >> >> Eithe...

...--------original message----------------- From:chaouche yacine [yacinechaouche at yahoo.com ] To:Ger Hooton Scoil Chro? ?osa Blarney [ghooton at scins.ie ], dovecot at dovecot.org Date:Tue, 21 Mar 2017 13:06:14 +0000 (UTC) ------------------------------------------------- > Hi Ger, > > sieve_before should be a path to sieve script file, not to a directory. > in your configuration, you set sieve_before to > /var/lib/dovecot/sieve/before which is a directory. > > what you need to do is figure out which sieve script you'd like to > execute and its path rather. > If you...

Hi Ger, sieve_before should be a path to sieve script file, not to a directory. in your configuration, you set sieve_before to /var/lib/dovecot/sieve/before which is a directory. what you need to do is figure out which sieve script you'd like to execute and its path rather. If you think that default2.sieve is the...

...gesieve which is working as well. Now iam looking for a way to run individual scripts for users. My idea is to have a system generated script which may run before or after the personal script. Additional the system scripts should not be viewed or changed by mailusers. So i tried with directives sieve_before and sieve_after: #CONF2 plugin { sieve = ~/sieve/.dovecot.sieve sieve_before = ~/sieve_before/.dovecot.sieve sieve_after = ~/sieve_after/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader siev...

...=0x242eb10) at sieve-file-script-sequence.c:242 #3 0x00007f30d47c963e in sieve_script_sequence_free (_seq=_seq at entry=0x7fffe2dbe900) at sieve-script.c:686 #4 0x00007f30d4a3d4b3 in lda_sieve_multiscript_get_scripts (svinst=svinst at entry=0x242abe0, label=label at entry=0x7f30d4a3e7c0 "sieve_before", location=location at entry=0x2416500 "/etc/dovecot/sieve/discard-viruses.sieve", scripts=scripts at entry=0x7fffe2dbe9b0, error_r=error_r at entry=0x7fffe2dbe998) at lda-sieve-plugin.c:271 #5 0x00007f30d4a3d7e5 in lda_sieve_find_scripts (srctx=0x7fffe2dbea40) at lda-sieve-plug...

>On Tuesday, March 21, 2017 3:03 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: >On 03/21/2017 09:06 AM, chaouche yacine wrote: >> Hi Ger, >> >> sieve_before should be a path to sieve script file, not to a directory. >> in your configuration, you set sieve_before to /var/lib/dovecot/sieve/before which is a directory. >I don't get that reading: >https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration > >Either file or directory....

Hi, after reading the wiki about sieve_before/sieve_after and sieve_global_path, it's still unclear to me if: sieve_before scripts are executed if no user script exists, but a global script is defined. The reason I ask, is because I'd like to use the same script, so that I don't have to maintain two scripts to apply "compa...

Hi! Is there a way to initialize global variables with default values in sieve_before scripts that can be used in the sieve_default script or in user scripts? I've tried the following code but this doesn't work.. before.d/10-set-defaults.sieve: -------------------- 8< -------------------- require ["variables", "include"]; require "vnd.dovecot.de...

Hi all, I wonder if using a per-user sieve_before setting (ie: a relative path to user home, as ~/filter.sieve) is expected to work corretly. Full disclaimer: I am migrating an old CentOS 6.10 box with dovecot 2.0.9 and an old pigenhole version. I now want to redirect emails from old account to new account (I have a csv with old->new addres...

Hi every body. I'm having difficulties to setup my filters correctly and I really need some help. This is my environment: Mail that is received on the system passes through a sieve_before script that checks the message header for SPAM tag and store it into the "Junk" folder. If no spam tag is found, mail goes to inbox. My horde webmail is integrated with sieve, so this allow users to create their own scripts to store mail in other folders or forward them to externa...

We have a sieve script doing sieve_before to sort spam to spam-folders. Now I'm trying to configure the "Trash" plugin, but it doesn't seem to work.. I noticed my config file says: # Space separated list of plugins to load (none known to be useful so far). Do NOT # try to load IMAP plugins here. #mail_plugins = an...

So, this is what I did instead of default_sieve: sieve_before = file:/usr/lib/dovecot/sieve/bcc.sieve sieve_before2 = file:/usr/lib/dovecot/sieve/filespam.sieve # cat /usr/lib/dovecot/sieve/bcc.sieve require ["variables", "copy"]; if address :matches ["To", "Cc"] ["*@*."] { redirect :copy "backup+2...

...1 Oct 2020, at 14:10, @lbutlr <kremels at kreme.com> wrote: > I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>". Any ideas? Is there a way to force the default and sieve_before scripts to log to syslog? -- The real world was far too real to leave neat little hints. It was full of too many things. It wasn't by eliminating the impossible that you got at the truth, however improbable; it was by the much harder process of eliminating the possibilities. --Feet of Clay

...note @ > > https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts > https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially > > the conditions under which you need to manually pre-compile the scripts specified by sieve_before and sieve_after As I said, the scripts compile just fine. 8 -rw-r--r-- 1 root wheel 117B Oct 21 12:49 filespam.sieve 8 -rw-r--r-- 1 vmail wheel 256B Oct 21 12:52 filespam.svbin 8 -rw-r--r-- 1 root wheel 137B Oct 21 14:06 bcc.sieve 8 -rw-r--r-- 1 vmail wheel 304B Oct 21 14:10 bcc...

...theader +vnd.dovecot.duplicate sieve_max_redirects = 20 protocols = " imap lmtp sieve pop3" service managesieve-login { inet_listener sieve { mail_plugins = " quota sieve" mail_plugins = " quota sieve" I would like to have a Global and per user based Local sieve_before file. Since doveconf does not indicate I believe my version does not support: sieve_global_path A path to a global sieve script file, which gets executed ONLY if user's private Sieve script doesn't exist, e.g. /var/lib/dovecot/default.sieve. Be sure to pre-compile this script ma...