default admin enforced sieve script independent of user script

[brong]

From: costinel@gmail.com Bugzilla-Id: 3721 Version: 2.5.x (next) Owner: Bron Gondwana

[brong]

From:

Hi, I'm not sure if, or for how long is the dev team aware of this requested feature. I initially wrote to cyrus-devel mailing list where it has been criticized that there is no bug reported, so here it is.

I'm copy pasting the discussion below.

I would appreciate your point of view regarding the subject. Many thanks.

Date: Mon, 23 Jul 2012 23:26:53 +0300 Delivered-To: mailinglists35@gmail.com Message-ID: <CABjXrGFiD7A5-uR5g2K53eHTO+-eALNUdf4Co9Nybm7TP=bp5A@mail.gmail.com> Subject: official dev team position regarding multiple times requested feature (global sieve) From: mailing list subscriber <mailinglists35@gmail.com> To: cyrus-devel@lists.andrew.cmu.edu

Hi,

There are many situations where users are hardly able to figure out what to do if a shortcut icon has dissapeared from their desktop. Among their email needs, two features stand out: ability to view the possible spam emails into a separate folder and ability to setup their own "out of office" messages.

The first one has multiple solutions but each involve additional work from the sysadmin: either scripting or writing documentation to instruct users enable the feature on their own. The second one is handled either by client-side user script editing or a web interface. For a tech-savy user, combining the two is not a big challenge, however our typical joe is going to eventually quit reading instructions shortly at beginning and blame the IT for poor support.

On the other side, there is the management who is unable to understand why the out of office and spam filtering must cost dollars per user (= ms exchange) just to have these features usable by all employees.

The poor IT guy sits between these two forces and then pursues developers of free software for this and that feature.

With above figure in mind, I'm looking at the history of request for ability to have a forced, default, site-wide sieve script that the user or any other sieve client is unable to alter (I'll just pick most relevant):

2004, with reference to 2001: http://goo.gl/Gbo0k

2006: A submitted patch http://www.irbs.net/internet/info-cyrus/0612/0231.html

2007: A very good synthesis: http://goo.gl/Lo33b

2010: sieve include implemented in v.2.3.0, still fails to meet above requirements

With all due respect, what is the development's team position regarding this feature and how do the development team see a solution that meets both requirements?

Thank you.

[brong]

From:

> 2004, with reference to 2001: > http://goo.gl/Gbo0k

digging further, the 2001 message mentions another patch without link, found it here: http://www.mail-archive.com/info-cyrus@lists.andrew.cmu.edu/msg04406.html

[brong]

From: Bron Gondwana

Per the discussion on the mailing list, this is not P1, and it's not slated for inclusion in 2.5.

[brong]

From:

http://lists.andrew.cmu.edu/pipermail/cyrus-devel/2012-October/002691.html

On Thu, Sep 20, 2012 at 3:26 PM, Bron Gondwana <brong at fastmail.fm> wrote: > Roughly: > > a) nobody else wants to do it. > b) if you write a patch (or get someone to) and it doesn't break other > stuff or cause massive maintenance headaches or backwards compatibility > problems, we'll include it. > c) you can do whatever you want with your own copy of course. > > Bron ( or as they say in the parlance: patches welcome )

Hi, Does this patch qualify for b) ? http://lists.andrew.cmu.edu/pipermail/cyrus-devel/2006-December/000227.html Thanks.

[marclaporte]

Semi-related: https://github.com/thsmi/sieve/issues/258