official dev team position regarding multiple times requested feature (global sieve)

2012-07-23 Thread mailing list subscriber
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"

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-07-23 Thread Adam Tauno Williams
On Mon, 2012-07-23 at 23:26 +0300, mailing list subscriber wrote: > 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): Indee

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-07-24 Thread Jeroen van Meeuwen (Kolab Systems)
On 2012-07-23 22:26, mailing list subscriber wrote: 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? Users will most likely continue to require write access to a script that allows

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-07-24 Thread mailing list subscriber
On Tue, Jul 24, 2012 at 10:59 AM, Jeroen van Meeuwen (Kolab Systems) wrote: > On 2012-07-23 22:26, mailing list subscriber wrote: >> >> 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 requirem

Fwd: official dev team position regarding multiple times requested feature (global sieve)

2012-07-24 Thread mailing list subscriber
dev team position regarding multiple times requested feature (global sieve) To: awill...@opengroupware.us On Mon, Jul 23, 2012 at 11:47 PM, Adam Tauno Williams wrote: > On Mon, 2012-07-23 at 23:26 +0300, mailing list subscriber wrote: >> With above figure in mind, I'm looking at

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-07-30 Thread Jeroen van Meeuwen
On Tuesday, July 24, 2012 11:30:20 AM mailing list subscriber wrote: Dear mailing list subscriber, Apologies for taking as long as I did to get back to this. > On Tue, Jul 24, 2012 at 10:59 AM, Jeroen van Meeuwen (Kolab Systems) > wrote: > > I'm curious to learn what exactly would be the set of

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-07-30 Thread Дилян Палаузов
Hello, as far as I understand, the use case for the requested feature is to have default spam filter rules (action fileinto or reject), that are canceled, when the user's script make a different fileinto/reject. Something like: Execute the :global default script, which contains only fileint

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-08-07 Thread mailing list subscriber
On Mon, Jul 30, 2012 at 2:58 PM, Jeroen van Meeuwen wrote: [...] > > > Let me summarize what is then the idea, if I understand correctly: > - A setting will control what script is mandatory, globally, if any, for > example: > > sieve_mandatory_script: /path/to/sieve/script > yes this script wou

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-08-07 Thread mailing list subscriber
On Mon, Jul 30, 2012 at 7:03 PM, Дилян Палаузов wrote: > Hello, > > as far as I understand, the use case for the requested feature is to have > default spam filter rules (action fileinto or reject), that are canceled, > when the user's script make a different > fileinto/reject. Something like: No

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-09-19 Thread mailing list subscriber
Hi, Any news on this thread? Thanks. On Tue, Aug 7, 2012 at 11:07 AM, mailing list subscriber wrote: > On Mon, Jul 30, 2012 at 2:58 PM, Jeroen van Meeuwen > wrote: > > [...] > >> >> >> Let me summarize what is then the idea, if I understand correctly: >> - A setting will control what script is m

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-09-20 Thread Bron Gondwana
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

Re: official dev team position regarding multiple times requested feature (global sieve)

2012-10-20 Thread mailing list subscriber
On Thu, Sep 20, 2012 at 3:26 PM, Bron Gondwana 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

Re: Fwd: official dev team position regarding multiple times requested feature (global sieve)

2012-07-24 Thread Bron Gondwana
On Tue, Jul 24, 2012, at 10:32 AM, mailing list subscriber wrote: > Unfortunately that feature only addresses PROVISIONING of data, which > is quite unuseful since cyrus mail admins do this with the auto-* > uoa.gr patches (that's another pain that devs refused to include for a > long time) - What