martin: doc/architecture server.sgml,1.8,1.9

cvs at intevation.de cvs at intevation.de
Fri Apr 2 00:23:44 CEST 2004


Author: martin

Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv30241

Modified Files:
	server.sgml 
Log Message:
Martin K.: Added reasoning for choosing a quarantine directory


Index: server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/server.sgml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- server.sgml	1 Apr 2004 17:07:28 -0000	1.8
+++ server.sgml	1 Apr 2004 22:23:41 -0000	1.9
@@ -1,4 +1,4 @@
-<chapter><title> Kolab Server Components </title>
+											<chapter><title> Kolab Server Components </title>
 <para>Whatever configuration data can be held inside the LDAP directory will be stored there.
 Still, there is the need for individual configuration files of services that are
 run on the Kolab server:</para>
@@ -181,7 +181,13 @@
 amavis when it starts. 
 </para>
 <para>
-Maintaining theses directories and especially the quarantine is the job of a systemadministrator (root).
+Maintaining theses directories and especially the quarantine is the job of a systemadministrator (root). It is possible to give another adminstration user without root priviledges 
+access to the quarantine though it is no good idea to forward malicious messages to some email account. 
+</para>
+<para>
+The later would pose a security thread to whomever who processes the messages from the quarantine with an email client. Even though currently the vast majority of malicious messages 
+is targeted towards vulnerabilities in Windows products (mainly MS Outlook and MS Internet Explorer) there is a real risk of viruses and other malware taking advantage of security 
+flaws in Linux or webbased applications.
 </para>
 
 <programlisting>





More information about the commits mailing list