docker
/
docker-mailserver
mirror of https://github.com/tomav/docker-mailserver.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Configuring Sieve filters (markdown)

This commit is contained in:
00angus 2016-04-29 10:17:18 +02:00
parent 101a404171
commit ad735ac557
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/content/advanced/mail-sieve.md
View File

@ -4,6 +4,8 @@
To specify a user-defined Sieve filter place a `.dovecot.sieve` file into a virtual user's mail folder e.g. `/var/mail/domain.com/user1/.dovecot.sieve`. If this file exists dovecot will apply the filtering rules.
It's even possible to install a user provided Sieve filter at startup during users setup: simply include a Sieve file in the `config `path for each user login that need a filter. The file name provided should be in the form **\<user_login\>.dovecot.sieve**, so for example for `user1@domain.tld` you should provide a Sieve file named `config/user1@domain.tld.dovecot.sieve`.
An example of a sieve filter that moves mails to a folder `INBOX/spam` depending on the sender address:
```
@ -18,4 +20,13 @@ if address :contains ["From"] "spam@spam.com" {
***Note:*** that folders have to exist beforehand if sieve should move them.
For more examples or a detailed description of the Sieve language have a look at [the official site](http://sieve.info/examplescripts).
Another example of a sieve filter that forward mails to a different address:
```
require ["copy"];
redirect :copy "user2@otherdomain.tld";
```
For more examples or a detailed description of the Sieve language have a look at [the official site](http://sieve.info/examplescripts). Other resources are available on the internet where you can find several [examples](https://support.tigertech.net/sieve#sieve-example-rules-jmp).