similar to: sieve_after scripts with virtual domains

Op 3/22/2018 om 3:30 PM schreef Mr Nicolas Belan: > Hello the list, > > I am trying to achieve filter processing using sieve, but i am not > sure I can do what I want. > > I want to let the user decide to use my filtering script (sieve_after) > or not. > According to the documentation, i am trying to stop processing in user > sieve script, but processing continue. >

Per Jessen wrote: > Per Jessen wrote: > >> Michael Kliewe wrote: >> >>> Hi Per, >>> >>> On 25.08.2015 11:40, Per Jessen wrote: >>>> sieve and managesieve are both working fine, have been for years. >>>> Now I want to add a sieve_after script: >>>> >>>> /etc/dovecot/conf.d/90-sieve.conf :

Michael Kliewe wrote: > Hi Per, > > On 25.08.2015 11:40, Per Jessen wrote: >> sieve and managesieve are both working fine, have been for years. Now >> I want to add a sieve_after script: >> >> /etc/dovecot/conf.d/90-sieve.conf : >> >> plugin { >> sieve = ~/.dovecot.sieve >> sieve_dir = ~/sieve >> sieve_before = >>

sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script: /etc/dovecot/conf.d/90-sieve.conf : plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + } I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any

Per Jessen wrote: > Michael Kliewe wrote: > >> Hi Per, >> >> On 25.08.2015 11:40, Per Jessen wrote: >>> sieve and managesieve are both working fine, have been for years. >>> Now I want to add a sieve_after script: >>> >>> /etc/dovecot/conf.d/90-sieve.conf : >>> >>> plugin { >>> sieve = ~/.dovecot.sieve

Hi Per, On 25.08.2015 11:40, Per Jessen wrote: > sieve and managesieve are both working fine, have been for years. Now I > want to add a sieve_after script: > > /etc/dovecot/conf.d/90-sieve.conf : > > plugin { > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > sieve_before = > sieve_after = ~/sieve/personal.sieve > sieve_subaddress_sep = + > } >

Per Jessen skrev den 2015-08-25 15:49: >>>>> plugin { >>>>> sieve = ~/.dovecot.sieve >>>>> sieve_dir = ~/sieve >>>>> sieve_before = >>>>> sieve_after = ~/sieve/personal.sieve >>>>> sieve_subaddress_sep = + >>>>> } sieve is the personal, and sieve_after is the global, you have

Hello the list, I am trying to achieve filter processing using sieve, but i am not sure I can do what I want. I want to let the user decide to use my filtering script (sieve_after) or not.According to the documentation, i am trying to stop processing in user sieve script, but processing continue. I am using dovecot 2.2 (CentOS). My sieve configuration is:plugin { ? sieve =

Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script

Hi, sieve_default shoud be good, but roundcube set an empty sieve script if a user removed its script.So, until the user creates its first script, it is working, but never called after. That's why I choose to use sieve_after. Regards,Nicolas Le vendredi 23 mars 2018 ? 09:03:16 UTC+1, Alex JOST <jost+lists at dimejo.at> a ?crit : Am 22.03.2018 um 15:30 schrieb Mr Nicolas

hi, i can't compile managesieve-0.11.11 on Solaris 10 against Sieve 0.1.17 and Dovecot 1.2.13: [...] gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -o managesieve-login client.o client-authenticate.o managesieve-capability.o managesieve-proxy.o cmd-noop.o

Am 22.03.2018 um 15:30 schrieb Mr Nicolas Belan: > Hello the list, > > I am trying to achieve filter processing using sieve, but i am not sure I can do what I want. > I want to let the user decide to use my filtering script (sieve_after) or not.According to the documentation, i am trying to stop processing in user sieve script, but processing continue. sieve_default might be the

Hello List, I am using dovecot: ii dovecot-antispam 2.0+20130822-2 amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-1 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-1 amd64 secure POP3/IMAP server - IMAP daemon ii

On 2/12/2015 2:12 AM, Florin Portase wrote: > > On 2015-02-12 01:01, Stephan Bosch wrote: > >> On 2/11/2015 10:37 PM, Portase Florin wrote: >>> On 2/11/2015 8:41 PM, Stephan Bosch wrote: >>>> On 2/11/2015 7:34 PM, Florin Portase wrote: >>>>> Hello guys, >>>>> >>>>> I'm having troubles making

Quoting Robert Schetterer <rs at sys4.de>: > Am 12.09.2016 um 15:07 schrieb Andre Luiz Paiz: >> Hi everybody. 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

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 "company policy" or "global features". It

On 2/11/2015 10:37 PM, Portase Florin wrote: > On 2/11/2015 8:41 PM, Stephan Bosch wrote: >> On 2/11/2015 7:34 PM, Florin Portase wrote: >>> Hello guys, >>> >>> I'm having troubles making "script_after" to exec sieve scripts:: >>> >> Keep in mind that the sieve_after script is only executed when the >> "keep" action

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