Re: How to activate sieve script for users?
On Thu, 2006-03-09 at 12:57 -0500, Joseph Brennan wrote: > > you dont need to known user passwords to set sieve scripts. > > > The more interesting problem is how you will then maintain the > scripts. Most users do not have the technical background to > hand-edit sieve scripts. Instead they use a GUI to do this. > > But I'll grant that someone who could write .procmailrc recipes > should be able to handle sieve. > > The GUI clients are write-only. That is, they can translate > their own ruleset into sieve script, but they cannot translate > back from sieve script. So you use the GUI, it stores its > ruleset, and puts a sieve version to the server. When you > want to update, the GUI reads its ruleset to show you what > you have, and if you change something, it again puts a sieve > version to the server. > > What we're doing here is implementing the web-based Ingo > interface, and disallowing any other. This gets us at least > the portability that the Ingo page can be accessed from anywhere, > so that a user can update sieve rules from anywhere. (Actually > the user is updating Ingo rulesets that are put to the server > as sieve rules.) The down side is that some things you can > really do with sieve itself are not available. as Chuck would say...patches are welcome all in all, Ingo/Sieve is a pretty dynamite combination for end users to actually be able to maintain their sieve scripts. Craig Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: How to activate sieve script for users?
you dont need to known user passwords to set sieve scripts. The more interesting problem is how you will then maintain the scripts. Most users do not have the technical background to hand-edit sieve scripts. Instead they use a GUI to do this. But I'll grant that someone who could write .procmailrc recipes should be able to handle sieve. The GUI clients are write-only. That is, they can translate their own ruleset into sieve script, but they cannot translate back from sieve script. So you use the GUI, it stores its ruleset, and puts a sieve version to the server. When you want to update, the GUI reads its ruleset to show you what you have, and if you change something, it again puts a sieve version to the server. What we're doing here is implementing the web-based Ingo interface, and disallowing any other. This gets us at least the portability that the Ingo page can be accessed from anywhere, so that a user can update sieve rules from anywhere. (Actually the user is updating Ingo rulesets that are put to the server as sieve rules.) The down side is that some things you can really do with sieve itself are not available. Joseph Brennan Columbia University Information Technology Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: How to activate sieve script for users?
Hi, you dont need to known user passwords to set sieve scripts. Become the cyrus user if you can. For each user : - determine the directory for sieve scripts of the user (in imapd.conf, see sievedir hashimapspool fulldirhash) - mkdir -p the dir if not exist - copy your script for the user in that dir (eg: s0.script) - sievec s0.script s0.bc - ln -s s0.bc defaultbc - (if root) set ownership of the entire sieve hierarchy to the cyrus user Kai Wang a écrit : Greetings. We are migrating from uw-imap to cyrus. I have converted our users' procmailrc files to sieve scripts. I have root access and know the user cyrus' password. But I don't know users' password. Can anybody tell me how to activate for them? Thanks in advance Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: How to activate sieve script for users?
Kai Wang wrote: Greetings. We are migrating from uw-imap to cyrus. I have converted our users' procmailrc files to sieve scripts. I have root access and know the user cyrus' password. But I don't know users' password. Can anybody tell me how to activate for them? sieveshell --authname=cyrus --user= Give the cyrus admin's password when prompted and you will be alloew to proxy as -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: How to activate sieve script for users?
On Wed, 8 Mar 2006, Kai Wang wrote: Greetings. We are migrating from uw-imap to cyrus. I have converted our users' procmailrc files to sieve scripts. I have root access and know the user cyrus' password. But I don't know users' password. Can anybody tell me how to activate for them? I have a perl script for deactivating users' sieve scripts which you could modify to handle activation. I've written a bunch of automated stuff for managing sieve scripts, but it is all bundled in our user self-service web pages so I can't really distribute it (nor would it be very useful in that form). You can use this code as a base for simple sieve script processes. http://oregonstate.edu/~morgan/cyrus/public/deactivate_user_sieve.pl also http://oregonstate.edu/~morgan/cyrus/public/list_user_sieve.pl The perl module documentation for this stuff is pretty sparse (that's being kind), but you can figure out how it works by looking at the sieveshell program (which is just a perl script). Feel free to ask me questions too. Andy Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: How to activate sieve script for users?
On Thursday 09 March 2006 10:21, Kai Wang wrote: > We are migrating from uw-imap to cyrus. I have converted our users' > procmailrc files to sieve scripts. I have root access and know the user > cyrus' password. But I don't know users' password. Can anybody tell me > how to activate for them? AFAIK you can't :( I've tried to using "sieveshell --user=foo --authname=root mail" but it doesn't let me authenticate :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpXPovGcwgu8.pgp Description: PGP signature Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
How to activate sieve script for users?
Greetings. We are migrating from uw-imap to cyrus. I have converted our users' procmailrc files to sieve scripts. I have root access and know the user cyrus' password. But I don't know users' password. Can anybody tell me how to activate for them? Thanks in advance -- Kai Wang System Services Information Technologies, University of Calgary, 2500 University Drive, N.W., Calgary, Alberta, Canada T2N 1N4 Phone (403) 220-2423, Fax (403) 282-9361 Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
