| 30 | By writing your own sieve scripts you can have a lot more control over what happens and program actions that are not available via the Roundcube plugin. Writing your own script requires advanced knowledge, including the ability to either [wiki:faq/files/sftp use Secure FTP] or [wiki:faq/security/secure-shell ssh]. |
| 31 | |
| 32 | A sieve script is simply a text file that is saved in the .sieve directory in your home directory. The file can have any name or extension you like, however, the convention is to use the .sieve extension for each file. You can have many scripts in your .sieve directory, but only one can be active at a given time. To make a script active, create a symlink in your home directory called .dovecot.sieve that points to the file in your .sieve directory that you want to be active. |
| 33 | |
| 34 | For background info on the sieve language, including a simple example file, checkout the [WikiPedia:Sieve_%28mail_filtering_language%29 Wikipedia Page on Sieve]. There is a good collection of resources on the [http://sieve.info/ sieve web site] as well. |
| 35 | |
| 36 | For tutorials, there is one [http://kb.vircom.com/Kbase/default.asp?id=1333 available from vircom.com] and another [https://www.tty1.net/blog/2011/sieve-tutorial_en.html available via tty1.net]. |
| 37 | |
| 38 | And for a complete reference, see [https://thsmi.github.io/sieve-reference/en/index.html thsmi's site]. |
| 39 | |
| 40 | Lastly, if you are running linux on your desktop client, you can install the [https://github.com/philpennock/sieve-connect sieve-connect] program which will help you upload your sieve scripts and make them active without requiring sftp/ssh access. There are a [http://sieve.info/clients more sieve clients] you can check out that run on a variety of platforms, however, your mileage may vary. |