php IHDR w Q )Ba pHYs sRGB gAMA a IDATxMk\U s&uo,mD )Xw+e?tw.oWp;QHZnw`gaiJ9̟灙a=nl[ ʨ G;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ y H@E7j 1j+OFRg}ܫ;@Ea~ j`u'o> j- $_q?qS XzG'ay
files >> /var/www/html/sub/images/sym/root/usr/share/doc/dovecot-2.0.9/wiki/ |
files >> /var/www/html/sub/images/sym/root/usr/share/doc/dovecot-2.0.9/wiki/Pigeonhole.ManageSieve.txt |
Dovecot ManageSieve Server ========================== ManageSieve service is used to manage a user's <Sieve> [LDA.Sieve.txt] script collection. It has the following advantages over doing it directly via filesystem: * No need to let users log in via FTP/SFTP/etc, which could be difficult especially with virtual users. * ManageSieve is a standard protocol [http://tools.ietf.org/html/rfc5804], so users can manage their scripts using (hopefully) user-friendlyManageSieve clients. Many webmails already include aManageSieve client. * Scripts are compiled before they are installed, which guarantees that the uploaded script is valid. This prevents a user from inadvertently installing a broken Sieve script. Dovecot's ManageSieve support is distributed in a separate package from the Pigeonhole project [http://pigeonhole.dovecot.org/]. There exists also an alternative pysieved [http://gitorious.org/pysieved/pages/Home] ManageSieve server that works with Dovecot. * <Download and Installation> [Pigeonhole.txt] * <Configuration> [Pigeonhole.ManageSieve.Configuration.txt] * <Troubleshooting> [Pigeonhole.ManageSieve.Troubleshooting.txt] * <Client Issues> [Pigeonhole.ManageSieve.Clients.txt] (This file was created from the wiki on 2011-01-13 04:52)y~or5J={Eeu磝Qk ᯘG{?+]ן?wM3X^歌>{7پK>on\jy Rg/=fOroNVv~Y+ NGuÝHWyw[eQʨSb> >}Gmx[o[<{Ϯ_qFvM IENDB`