[Kolab-devel] doc/faq faq.dat,1.12,1.13 by martin at doto.intevation.de

[root at intevation.de]

Update of /kolabrepository/doc/faq
In directory doto:/tmp/cvs-serv14221

Modified Files:
	faq.dat 
Log Message:
Martin K. Added an entry about server side scripting as suggested by George
Staikos <staikos at kde.org>


Index: faq.dat
===================================================================
RCS file: /kolabrepository/doc/faq/faq.dat,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- faq.dat	14 Feb 2003 18:44:13 -0000	1.12
+++ faq.dat	6 Jul 2003 19:24:06 -0000	1.13
@@ -193,3 +193,46 @@
 	    <li> Use latency hiding techniques
 
 	</ul>
+
+<c>Kolab Server
+<q> How to use filtering of emails on the server side
+<a>
+
+	Filtering on the server side is currently not supported with neither
+        the web gui nor the KDE Kolab client. For filtering on the server you
+        must use the <a href="http://www.ietf.org/rfc/rfc3028.txt">RFC 3028</a>
+        conform sieve scripting language. Please be aware
+        of the potential pitfall with mailboxnames.
+        <p>
+
+        If you want to get sieve working please consider the following hints:
+
+	<ul>
+           <li> /kolab/var/imapd/log/lmtpd.log is your friend
+
+           <li> In order to use fileinto, you need to know that the mailboxes
+                are specified as follows:
+                <p>
+
+                fileinto "user/username at some^host^name/path/to/folder";
+                <p>
+
+                "user" is literal, "user at some^host^name" needs to be replaced, as does the 
+                path/to/folder of course. In orde to get an idea about the
+                usernames and paths please check /kolab/var/imapd/spool/user on
+                the Kolab server.
+
+           <li> Example script:<br/>
+
+		require ["fileinto"];<br/>
+                if header :contains ["List-Id"] ["<kroupware.mail.kde.org>"] {<br/>
+                  fileinto "user/staikos at kde^org/KDE/Kroupware";<br/>
+                }<br/>
+
+           <li> Don't forget that you must "put" the script with the sieve client and then 
+                activate it.
+
+           <li> please be careful not to break forwarding and vacation handling
+                as offered by Kolab which both also use sieve to get their tasks done.
+        </ul>
+