search for: sieve_global_path

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 fe...

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 set upload their own sieve script using managesieve. However, when configured like this, the user experience isn't quite perfect. When users open the mana...

...;fileinto"; fileinto "spamtest"; Then I configured my dovecot.conf file (via dovecot-postfix.conf it really points to) by setting: protocol lda { ... mail_plugins = cmusieve mail_plugin_dir = /usr/lib/dovecot/modules/lda ... } and: plugin { sieve_global_path = /etc/dovecot/sieve-global.d/spam.sieve } I manually compiled /etc/dovecot/sieve-global.d/spam.sieve so there also exists /etc/dovecot/sieve-global.d/spam.sievec in the same directory. Then I restarted both Dovecot and Postfix. Mail is being delivered, but still only to the same place it always...

...chown -R vmail:mail /home/sieve But in 90-sieve.conf there is the comment: # A path to a global sieve script file, which gets executed ONLY # if user's private Sieve script doesn't exist. Be sure to # pre-compile this script manually using the sievec command line # tool. #sieve_global_path = /var/lib/dovecot/sieve/default.sieve Do I run sievec on this script? And I found the following comment on a blog, about 3 years old: 2: Having a user-defined sieve script will cancel out the global script for redirecting spam. In the dovecot.conf, get rid of the sieve_global_path and sieve_g...

...t: yes subscriptions: yes namespace: type: shared separator: / prefix: shared/%%u/ location: maildir:%%Lh/Maildir:INDEX=%Lh/Maildir/shared/%%Lu list: children lda: postmaster_address: root mail_plugins: sieve quota autocreate expire auth_socket_path: /var/run/dovecot/auth-master sieve_global_path: /var/vmail/sieve/dovecot.sieve log_path: /var/log/sieve.log auth default: mechanisms: plain login default_realm: mydomain.net user: vmail username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_+@ passdb: driver: pam passdb: driver: sql args: /et...

We have used the great managesieve you have merged together, with sieve, to create pigeonhole. However, when a user creates a custom script through a GUI of ours, the default, as we expected, would be ignored. Maybe you could add a retain_sieve_global=yes|no setting OR be more complex by having the sieve_global_dir copied to the users sieve_dir on first managesieve script save, if another

...Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=cram-md5 /etc/dovecot/passwd driver = passwd-file } plugin { sieve = /vmail/%d/%n/.dovecot.sieve sieve_dir = /vmail/%d/%n/sieve sieve_global_path = /vmail/dovecot/sieve/default.sieve } protocols = imap lmtp sieve service auth { executable = /usr/lib/dovecot/auth unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener ima...

...> > But in 90-sieve.conf there is the comment: > > # A path to a global sieve script file, which gets executed ONLY > # if user's private Sieve script doesn't exist. Be sure to > # pre-compile this script manually using the sievec command line > # tool. > #sieve_global_path = /var/lib/dovecot/sieve/default.sieve > > Do I run sievec on this script? Yes. > And I found the following comment on a blog, about 3 years old: > > 2: Having a user-defined sieve script will cancel out the global > script for redirecting spam. > In the dovecot.conf, get rid...

...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 globalscripts ? thanks rajesh

...guys, is there any way to configure Dovecot to process the default sieve script and, after that, a user specific script? I have a default script to sort spam into a spam folder but if a user specific script is present, the default script is ignored. sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve Regards Patrick

...e_max_line_length = 65536 #managesieve_logout_format = bytes ( in=%i : out=%o ) #managesieve_implementation_string = Cyrus timsieved v2.2.13 } protocol lda { mail_plugins = sieve quota sieve=~/.dovecot.sieve sieve_extentions = +include sieve_dir=~/sieve sieve_before = /home/%u/sieve/redirect.svbin sieve_global_path = /etc/globalsieverc.svbin [/code]

...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 # This directory contains the scripts that are available. sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe } When I restart Dovecot I get the following error: ian:dovecot/ $ sudo rc.d restart dovecot...

...driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: /home/vmail/sieve/%n.sieve sieve_global_path: /home/vmail/globalsieverc --------------------------------------------------------

I'm configuring some Sieve scripts for virtual users. I'd like to keep the Sieve scripts somewhere "sensible". Currently, all the mail goes into /var/mail/vhosts/<domain>/<mailbox> So I thought a good place for the sieve script might be in there as well, for example: /var/mail/vhosts/example.com/username/sieve Is there any reason *not* to store the sieve scripts

...: > I am using dovecot: > ... > ii dovecot-sieve 1:2.2.10-1 amd64 > secure POP3/IMAP server - Sieve filters support > ... > doveconf -n | grep -i sieve > Since doveconf does not indicate I believe my version does not support: > > sieve_global_path I see mentions of this configuration variable in 7 year old dovecot posts, so it's been around a long time. You should do doveconf -a | grep sieve_global_path since "-n" won't list unchanged (defaulted) configuration values. Joseph Tam <jtam.home at gmail.com>

...il1 tree elsewhere ? like say /vmail/vmail1 is it as simple as shutting Dovecot/Postfix, move tree, edit conf and re start ? or am I missing something ..? or is the a better way of doing this ? # grep 'var/vmail' *.conf dovecot.conf: sieve_global_dir = /var/vmail/sieve dovecot.conf: sieve_global_path = /var/vmail/sieve/dovecot.sieve dovecot.conf:# location = maildir:/var/vmail/public/:CONTROL=~/Maildir/public:INDEX=~/Maildir/public # cd ../postfix # grep 'var/vmail' *.cf main.cf:virtual_mailbox_base = /var/vmail # dovecot --version 2.3.11.3 (502c39af9)

Hi According to Dovecot documentation (): # If there is no user-specific Sieve-script, global Sieve script is # executed if set. (v1.0.1 and older used "global_script_path") #sieve_global_path = Then, if one user has its own script, the global script won't be executed? I would like to execute first the global script (for moving SPAM to the Junk folder), and then the user scripts is they exists. Any idea? Thanks in advance.

...ipt 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?

...pop3_uidl_format = %08Xu%08Xv mail_max_userip_connections = 50 mail_plugins = zlib } protocol lda { postmaster_address = postmaster at monsternett.no mail_plugins = sieve zlib mail_plugin_dir = /usr/lib/dovecot/modules/lda sieve_global_dir = /etc/dovecot/sieve/ sieve_global_path = /etc/dovecot/sieve/default.sieve } plugin { zlib_save_level = 6 zlib_save = gz fts = squat sieve = ~/dovecot.sieve sieve_dir = ~/ } -- Helge Milde, 69701808 www.monsternett.no

...tfix group = postfix } } } protocol lda { log_path = /srv/mail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster at leetcode.net mail_plugins = cmusieve sieve_global_path = /srv/mail/sieverc plugin { sieve = /srv/mail/%u/sieverc } } ### end dovecot.conf ### dovecot.log deliver(jreese at leetcode.net): Jan 24 14:30:40 Info: Loading modules from directory: /usr/lib/dovecot/modules/lda deliver(jreese at leetcode.net): Jan 24 14:3...