Sophie

Sophie

distrib > Mageia > 6 > armv7hl > media > core-updates-src > by-pkgid > 0796f3a4146744711e43968234de3795 > files > 50

squirrelmail-1.4.22-15.1.mga6.src.rpm

diff -up avelsieve/config/config_sample.php.avelport avelsieve/config/config_sample.php
--- avelsieve/config/config_sample.php.avelport	2016-06-15 09:15:54.000000000 +0200
+++ avelsieve/config/config_sample.php	2016-06-15 09:17:48.000000000 +0200
@@ -48,10 +48,10 @@ $avelsieve_backend = 'ManageSieve';
 /* =================== ManageSieve Backend Options ======================== */
 /* ======================================================================== */
 
-/* Port where timsieved listens on the Cyrus IMAP server. Default is 2000. */
+/* Port where timsieved listens on the Cyrus IMAP server. Default is 4190. */
 
 global $sieveport;
-$sieveport = 2000;
+$sieveport = 4190;
 
 /**
  * @var string Space separated list of preferred SASL mechanisms for the
diff -up avelsieve/doc/README.avelport avelsieve/doc/README
--- avelsieve/doc/README.avelport	2016-06-15 09:16:51.000000000 +0200
+++ avelsieve/doc/README	2016-06-15 09:17:12.000000000 +0200
@@ -12,7 +12,7 @@
    storage of the Sieve scripts. Currently, three backends are available:
     1. ManageSieve: This is the transport protocol for uploading, editing,
        deleting and verifying Sieve scripts on a mail server. A daemon
-       usually listens to port 2000, where clients such as avelsieve can
+       usually listens to port 4190, where clients such as avelsieve can
        connect and manage the scripts.
        Examples of server implementations that support ManageSieve:
           + [6]Cyrus IMAPd running timsieved
diff -up avelsieve/doc/README.html.avelport avelsieve/doc/README.html
--- avelsieve/doc/README.html.avelport	2009-05-29 10:24:15.000000000 +0200
+++ avelsieve/doc/README.html	2016-06-15 09:17:03.000000000 +0200
@@ -17,7 +17,7 @@ storage of the Sieve scripts. Currently,
 <ol>
         <li><strong>ManageSieve</strong>: This is the transport protocol for
         uploading, editing, deleting and verifying Sieve scripts on a mail
-        server. A daemon usually listens to port 2000, where clients such as
+        server. A daemon usually listens to port 4190, where clients such as
         avelsieve can connect and manage the scripts.<br/>
         Examples of server implementations that support ManageSieve:
         <ul>
diff -up avelsieve/include/managesieve.lib.php.avelport avelsieve/include/managesieve.lib.php
--- avelsieve/include/managesieve.lib.php.avelport	2016-06-15 09:30:59.000000000 +0200
+++ avelsieve/include/managesieve.lib.php	2016-06-15 09:31:10.000000000 +0200
@@ -291,7 +291,7 @@ class sieve {
    * a SIEVE daemon, such as timsieved, is listening.
    *
    * @param $port string Numeric port to connect to. SIEVE daemons usually
-   * listen to port 2000.
+   * listen to port 4190.
    *
    * @param $user string is the  user identity for which the SIEVE scripts
    * will be managed (also know as authcid).