"Sensible" location for Sieve scripts
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 in the same location as the mail?
Thanks,
Andy
On 6/26/2015 5:48 AM, Andrew Beverley wrote:
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 in the same location as the mail?
This is how I'm doing it. I'm running version 1.2.15. All users are virtual, stored in mysql, this is where mail goes:
mail_location = maildir:/home/vmail/%d/%u/
There are a few config lines that handle sieve scripts:
in the "protocol lda" section: sieve_global_path = /home/vmail/global.sieve
in the "plugin" section: sieve=/home/vmail/sieve/%d/%u/.dovecot.sieve sieve_dir=/home/vmail/sieve/%d/%u/sieve
I am using managesieve. There's a sieve plugin in my squirrelmail install so users can manage their filters.
Thanks, Shawn
On Fri, 2015-06-26 at 09:40 -0600, Shawn Heisey wrote:
On 6/26/2015 5:48 AM, Andrew Beverley wrote:
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 in the same location as the mail?
This is how I'm doing it. I'm running version 1.2.15. All users are virtual, stored in mysql, this is where mail goes:
mail_location = maildir:/home/vmail/%d/%u/
There are a few config lines that handle sieve scripts:
in the "protocol lda" section: sieve_global_path = /home/vmail/global.sieve
in the "plugin" section: sieve=/home/vmail/sieve/%d/%u/.dovecot.sieve sieve_dir=/home/vmail/sieve/%d/%u/sieve
I am using managesieve. There's a sieve plugin in my squirrelmail install so users can manage their filters.
Great, thanks Shawn, really useful.
Andy
On June 26, 2015 7:10:29 PM Andrew Beverley andy@andybev.com wrote:
in the "plugin" section: sieve=/home/vmail/sieve/%d/%u/.dovecot.sieve sieve_dir=/home/vmail/sieve/%d/%u/sieve
change last sieve to .sieve so it does not colledge with other dirs atleast to remember if maildir does not start with a dot, i do this to prevent sive scripts show up in maildirs
above will olso works if $HOME is diff for sieve and maildir, just me that have one $HOME for all virtual users in dovecot
On 6/26/2015 12:25 PM, Benny Pedersen wrote:
On June 26, 2015 7:10:29 PM Andrew Beverley andy@andybev.com wrote:
in the "plugin" section: sieve=/home/vmail/sieve/%d/%u/.dovecot.sieve sieve_dir=/home/vmail/sieve/%d/%u/sieve
change last sieve to .sieve so it does not colledge with other dirs atleast to remember if maildir does not start with a dot, i do this to prevent sive scripts show up in maildirs
above will olso works if $HOME is diff for sieve and maildir, just me that have one $HOME for all virtual users in dovecot
Since I don't have a domain named "sieve" (and never will) that location can never conflict with any user's Maildirs. My mail_location parameter is set to maildir:/home/vmail/%d/%u/ which doesn't overlap at all.
Thanks, Shawn
participants (3)
-
Andrew Beverley
-
Benny Pedersen
-
Shawn Heisey