global sieve folder ... ?

[Zachariah Mully]

On Wed, 2006-08-16 at 00:04 -0300, Marc G. Fournier wrote:
> On Tue, 15 Aug 2006, Ken Murchison wrote:
> 
> > Marc G. Fournier wrote:
> >> 
> >> This is the first time I've ever seen this ... when I put a filter in for 
> >> an account that happens to be listed in the 'admins' section of imapd.conf, 
> >> it is putting the filter into a global directory, instead of the admin 
> >> sieve directory ...
> >> 
> >> I've been doing this for years, where the 'admin' account is a catchall 
> >> mailbox, created by defualt with new domains, and for those clients that 
> >> just want to forward all email to another address, they just create a 
> >> filter on that account, instead of creating other mailboxes ...
> >> 
> >> Why is it all of sudden starting to create this global directory, and how 
> >> do I make it stop? :)
> >
> > Admins aren't supposed to be regular users, meaning they aren't supposed to 
> > have INBOXes or sieve scripts.  It has said this in the docs for a quite 
> > while (perhaps as far back as v1.6?).
> >
> > Cyrus 2.3 and recent 2.2 releases allow sieve scripts to be placed on shared 
> > mailboxes.  This is done by authenticating to timsieved as an admin, which 
> > then places scripts in the global/ namespace.
> 
> Great, now I have to change my whole mail system *sniffle*
> 
> This is going to be fun :(

Umh, why? Can't you simply name another user (perhaps 'mailadmin' or
something like that) as the administrator in the cyrus config? Why are
you giving clients admin rights?

Z