On Nov 6, 2007 5:46 PM, Toschi Pietro <Pietro.Toschi@xxxxxxxxxx> wrote: > > Hi all. > > While playing with smartsieve I've encountered an unknown imapd.conf > option named sieve_admins. Looking at the docs (cyrus 2.3.10) didn't > help. Looking at imapopts.c didn't either. > It is used to list those users that are allowed to authenticate as > themselves but get authorized as other users while performing SIEVE > management actions (and only that kind of actions, they do not admin > mailboxes for example). Very useful and apparently perfectly working. options in imapd.conf are used by multiple cyrus daemon. They can be named <service>_<option_name> where <service> is one of the cyrus daemon Then if you have admins: foo imap_admins: bar sieve will use the global option with value "foo" and imapd will use the more specific to itself "bar" > > My question is: how this option is used by cyrus? What cyrus component > loads and evaluates it apart from smartsieve web app? > > Indeed: googleing I've found another undocumented imapd.conf option: > imap_admins. Any info about that? > > Thanks > > Pietro > ---- > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Alain Spineux aspineux gmail com May the sources be with you ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
