On 13/10/2010 08:43, Stephan Bosch wrote:
Op 12-10-2010 5:47, Jerrale G schreef:
We have used the great managesieve you have merged together, with
sieve, to create pigeonhole. However, when a user creates a custom
script through a GUI of ours, the default, as we expected, would be
ignored.
On 14/10/10 10:32, Ed W wrote:
On 13/10/2010 08:43, Stephan Bosch wrote:
Op 12-10-2010 5:47, Jerrale G schreef:
We have used the great managesieve you have merged together, with
sieve, to create pigeonhole. However, when a user creates a custom
script through a GUI of ours, the default, as
On 14/10/2010 09:48, Tom Hendrikx wrote:
# Everytime you remove this line, god kills a kitten
include :global global-spam.sieve;
My suggestion was to do the reverse of this, ie have the global script
include the local script - does that work also? The use case there
would be if you didn't
On 14/10/10 10:58, Ed W wrote:
On 14/10/2010 09:48, Tom Hendrikx wrote:
# Everytime you remove this line, god kills a kitten
include :global global-spam.sieve;
My suggestion was to do the reverse of this, ie have the global script
include the local script - does that work also?
Including
Op 12-10-2010 5:47, Jerrale G schreef:
We have used the great managesieve you have merged together, with
sieve, to create pigeonhole. However, when a user creates a custom
script through a GUI of ours, the default, as we expected, would be
ignored. Maybe you could add a
On 12.10.2010 06:47, Jerrale G wrote:
Maybe you could add a retain_sieve_global=yes|no setting OR be
more complex by having the sieve_global_dir copied to the users
sieve_dir on first managesieve script save, if another setting to do
this was set to yes. This way the administrators can create
On 10/12/2010 2:55 AM, Eray Aslan wrote:
On 12.10.2010 06:47, Jerrale G wrote:
Maybe you could add a retain_sieve_global=yes|no setting OR be
more complex by having the sieve_global_dir copied to the users
sieve_dir on first managesieve script save, if another setting to do
this was set to
On 10/12/2010 11:16 AM, Jerrale G wrote:
On 10/12/2010 2:55 AM, Eray Aslan wrote:
On 12.10.2010 06:47, Jerrale G wrote:
Maybe you could add a retain_sieve_global=yes|no setting OR be
more complex by having the sieve_global_dir copied to the users
sieve_dir on first managesieve script save,
On 12.10.2010 18:16, Jerrale G wrote:
We have a lot of users liking both you
It's not me but Stephan Bosch you are looking for. Sorry for the
misunderstanding.
Pigeonhole would be even nicer with a skelton directory specified to
copy a user's scripts from it, to their sieve_dir folder, on
On 10/12/2010 1:07 PM, Eray Aslan wrote:
On 12.10.2010 18:16, Jerrale G wrote:
We have a lot of users liking both you
It's not me but Stephan Bosch you are looking for. Sorry for the
misunderstanding.
Pigeonhole would be even nicer with a skelton directory specified to
copy a user's
We have used the great managesieve you have merged together, with
sieve, to create pigeonhole. However, when a user creates a custom
script through a GUI of ours, the default, as we expected, would be
ignored. Maybe you could add a retain_sieve_global=yes|no setting OR be
more complex by
11 matches
Mail list logo
