<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 23/04/10 04:59 AM, Christian Rößler wrote:
<blockquote cite="mid:4BD1618E.6040503@FuH-E.de" type="cite">
<pre wrap="">Richard Bos schrieb:
</pre>
<blockquote type="cite">
<pre wrap="">Op donderdag 22 april 2010 17:05:49 schreef Christian Rößler:
</pre>
<blockquote type="cite">
<pre wrap="">Christian Tardif schrieb:
</pre>
<blockquote type="cite">
<pre wrap="">I was wondering if there was any way to create a global filter rule so
every user in the system would make use of it implicitely? What I would
want is a way to force every mail tagged as SPAM (via the headers) go in
the Junk folder of the coresponding user without having to go in each
user account and set it. Also, a global rule would ensure that they
wouldn't be able to revome the rule by themselves.
</pre>
</blockquote>
<pre wrap="">Heh, is it this time of the year again? snicker SCNR, but the global
sieve-script question is likely to come each two months.
Well, let me citate myself
</pre>
</blockquote>
<pre wrap="">Why not make it a wiki page <a class="moz-txt-link-freetext" href="http://wiki.kolab.org">http://wiki.kolab.org</a> in that case?
</pre>
</blockquote>
<pre wrap="">
yes, you are right - I have done so: in
<a class="moz-txt-link-rfc2396E" href="https://wiki.kolab.org/index.php/Filtering_Emails_on_the_Server"><https://wiki.kolab.org/index.php/Filtering_Emails_on_the_Server></a> I have
created a subsection
<a class="moz-txt-link-rfc2396E" href="https://wiki.kolab.org/index.php/Filtering_Emails_on_the_Server#How_to_provide_global_default_filters"><https://wiki.kolab.org/index.php/Filtering_Emails_on_the_Server#How_to_provide_global_default_filters></a>.
</pre>
</blockquote>
<br>
In fact, it's not a useable setup for most of Horde interface users.
And they are many.<br>
<br>
As soon as one of them will modify its sieve script (let's say one goes
on vacations...), this will erase manual include entry... and the
general filter will be gone.<br>
<br>
At least, if autocreateinboxfolders, autosubscribeinboxfolders,
autocreate_sieve_script, and generate_compile_sieve_script were
working, then we would have something really useful. I was quite used
to that when I was using Cyrus-Imap alone. I was creating the user
entry and, at first login, folders and scripts were created
automatically. And, in these many years I worked with this setup, I
never had one user which deleted his auto-created script. It's really
sad that this does not work with Kolab, as this is overloading user
creation time, as everything must be done manually.<br>
<div class="moz-signature">-- <br>
<style type="text/css" media="screen">
#container {
position: relative;
}
#top {
position: relative;
}
#logo {
position: relative;
float: left;
}
#infos {
position: relative;
float: left;
}
#bottom {
position: relative;
width: 100%;
clear: both;
}
</style>
<div id="top"> </div>
<div id="bottom">Christian...<br>
</div>
</div>
</body>
</html>