similar to: Default and per-User sieve script

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

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

Hi folks, I'm setting up a dovecot server with managesieve support. I'd like to offer spamfiltering through a Sieve script to my users by default, but still allow them to modify the filtering rules through Managesieve. I found the sieve_global_path configuration option, which seems perfect for what I want. I can configure a default script there, which will work for all users until they

Hello, I am building a new server on CentOS 7 and the global sieve filter can not be loaded. The debug shows: Nov? 9 15:23:09 mail dovecot: lmtp(11182, gao at mydomain.com): Debug: sieve: Pigeonhole version 0.4.2 initializing Nov? 9 15:23:09 mail dovecot: lmtp(11182, gao at mydomain.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global'

I can't get sieve to put virus files in the SPAM folder. dovecot -n # 2.0.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.38.8-32.fc15.i686.PAE i686 Fedora release 15 (Lovelock) auth_debug_passwords = yes info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_access_groups = mail mail_home = /home/vmail/%d/%n mail_location = maildir:~/mail mail_privileged_group = mail

On Fri, May 31, 2019 10:18 am, Ralph Seichter via dovecot wrote: > * Voytek Eymont via dovecot: > Try runing "sievec -u {your_linux_user} /path/to/whatever.sieve" from a > shell and check the resulting error messages. Raplh, thanks so, am I'm missing sql lookup for sieve...? # sievec -u voytek dovecot.sieve sievec(voytek)<9667><>: Error: user voytek: Auth

hello all had some basic questions 1) what is the logic behind the numbering of files in the conf.d folder ... is this to define the sequence of execution of the config files ? 2) Concerning global scripts, is the default.sieve, before i understand that they get executed when the user does not have his private sieve script. are sieve_before, sieve_after and sieve_global_path all

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

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

Using sieve_before, can the script it references include a file from the personal space? I want to set some parameters (by user using the variables extension) there to control what the before script does, so, every user would have the file in their personal include space. If not, is there another way? Can the sieve_before and sieve_global_path be set from userdb extra fields?

since moving/upgrading system I've noticed I no longer get sieve script compiled, there is no dovecot.svbin created in /var/vmail/vmail1/sbt.net.au/voytek at tld.au/sieve what am I missing, how to check ? also, looking at sieve.log, I see a lot of May 31 06:32:50 lda(voytek at sbt.net.au)<1234><c4aVBfI98FzSBAAAyLbbsQ>: Error: sieve: Failed to initialize script execution: Invalid

I am building a new mailserver on Centos7. My sieve is created with: mkdir /home/sieve cat <<EOF>/home/sieve/globalfilter.sieve || exit 1 require "fileinto"; if exists "X-Spam-Flag" { if header :contains "X-Spam-Flag" "NO" { } else { fileinto "Spam"; stop; } } if header :contains "subject"

In Dovecot 1.1.11 cmusieve is apparently integrated in the Ubuntu 9.10 package "dovecot-common" since the files are there. I am wanting to right now just do a very basic test of the setup to see how it runs before doing more sophisticated steps that could obscure any errors or bugs (e.g. unit testing). So I took the following example sieve script from the wiki1 documentation: require

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

On Thu, 9 Nov 2017 21:02:44 -0500 Bill Shirley <bill at KnoxvilleChristian.org> wrote: > Set the sieve_global_dir like this. > /etc/dovecot/conf.d/99-mystuff.conf: > . > . > plugin { > ? sieve???????????????? = ~/Maildir/dovecot.sieve > ? sieve_dir???????????? = ~/Maildir/sieve > ? sieve_global_dir????? = /etc/dovecot/sieve/global/ > ? sieve_before????????? =

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

I cutover to a new server which uses Postfix & Dovecot to handle emails as opposed to Postfix & Courier in the old server. Below is the contents of my global sieve script and dovecot config info. The dovecot-deliver.log does show that the email is being delivered to INBOX.spam but it ends up in the INBOX instead. If I put the exact same rule in the user script, the emails are delivered

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 #

On Fri, 10 Nov 2017 03:41:20 -0500 Bill Shirley <bill at KnoxvilleChristian.org> wrote: > No it isn't shown as a folder.? All folder directories here begin with a dot. > i.e.? .INBOX? .Trash? .Drafts > > Bill No, they don't. me thought that, too. But using the rainloop webmail interface on top of such a config showed the sieve folder in the overview. Sometimes you can

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