Re: automated delivery of sieve scripts for new users
On Thu, 2005-02-03 at 12:24 +0200, Christos Soulios wrote: > Craig White wrote: > > > > I believe that you are correct on the patch level but interestingly > > enough, it doesn't complain if I include any of the following directives > > in /etc/imapd.conf > > > > autocreate_sieve_script: /etc/default_sieve_script > > autocreate_sieve_compiledscript: /etc/default_sieve_script.bc > > generate_compiled_sieve_script: 1 > > > > Cyrus would not complain neither if it supported these options, nor if > it did not supported them. > > > > I don't think I've tried all of the combinations of them yet but they > > don't appear to work. > > > > The above configuration is correct as long as the files are valid sieve > scripts and readable by cyrus. Moreover, the patch is executed only when > there is no user mailbox and the user logs into the system. And not when > you create the mailbox using cyradm or other administering tool. > > > and in /usr/share/doc/cyrus-imapd-2.2.10/README.autosievefolder > > there is no mention of those items. > > > > Autosieve folder patch is a different patch from autocreate inbox/sieve. > It implements the creation of a folder upon file_into command from a > sieve script. Perhaps you should read the README.autocreate file for > more information in these options or read the following links : > > http://email.uoa.gr/projects/cyrus/autocreate > http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2 > > > > I appreciate your offer of the packages and note that apparently > > fedora-3 is using some derivative of your packages since I recall seeing > > the name on some file they distribute. > > > > I am going to try to stick with that which is distributed by fedora > > package for automated updates, etc. and so that really leaves me option > > 2 - which isn't so terrible since I have the bytecoded script in hand > > and I will script new users anyway. > > > > I believe that Simon's patches are very stable and always uptodate > against security and bug fixes. So I am sure, you should try them. thanks - I am certain that fedora is using Simon's patches...just not this one...yet. I put in a bugzilla @ redhat (fedora) - we'll see. For my house, it's meaningless. I already have 3 kids and I don't plan on having any more, certainly not enough to make autosieve a priority. At one of my clients though, it is significant and if fedora/RHEL doesn't update, I'll use Simon's so thanks for the heads up. I love this message base - got a lot of extremely accurate answers. Thanks everyone 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: automated delivery of sieve scripts for new users
Craig White wrote: I believe that you are correct on the patch level but interestingly enough, it doesn't complain if I include any of the following directives in /etc/imapd.conf autocreate_sieve_script: /etc/default_sieve_script autocreate_sieve_compiledscript: /etc/default_sieve_script.bc generate_compiled_sieve_script: 1 Cyrus would not complain neither if it supported these options, nor if it did not supported them. I don't think I've tried all of the combinations of them yet but they don't appear to work. The above configuration is correct as long as the files are valid sieve scripts and readable by cyrus. Moreover, the patch is executed only when there is no user mailbox and the user logs into the system. And not when you create the mailbox using cyradm or other administering tool. and in /usr/share/doc/cyrus-imapd-2.2.10/README.autosievefolder there is no mention of those items. Autosieve folder patch is a different patch from autocreate inbox/sieve. It implements the creation of a folder upon file_into command from a sieve script. Perhaps you should read the README.autocreate file for more information in these options or read the following links : http://email.uoa.gr/projects/cyrus/autocreate http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2 I appreciate your offer of the packages and note that apparently fedora-3 is using some derivative of your packages since I recall seeing the name on some file they distribute. I am going to try to stick with that which is distributed by fedora package for automated updates, etc. and so that really leaves me option 2 - which isn't so terrible since I have the bytecoded script in hand and I will script new users anyway. I believe that Simon's patches are very stable and always uptodate against security and bug fixes. So I am sure, you should try them. I might put in a bugzilla entry into fedora though... Regards, Christos --- 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: automated delivery of sieve scripts for new users
On Wed, 2005-02-02 at 22:33 +0100, Simon Matter wrote: > > On Wed, 2005-02-02 at 12:54 -0600, John Wade wrote: > >> Craig White wrote: > >> > >> > 1 - Is there a way to automatically set a sieve script to new users > >> > created on a system? > >> > >> I believe this is a part of the latest autocreate patch from the > >> University of Athens. > >> http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.10/cyrus-imapd-2.2.10-autocreate-0.9.1.diff > > > > hmm...looking at the diff, I wondered if that was already in my imapd > > configuration... > > No, IIRC it includes an older patch without the autocreate_sieve_script > feature. Take my rpms which include it: > http://www.invoca.ch/pub/packages/cyrus-imapd/ I believe that you are correct on the patch level but interestingly enough, it doesn't complain if I include any of the following directives in /etc/imapd.conf autocreate_sieve_script: /etc/default_sieve_script autocreate_sieve_compiledscript: /etc/default_sieve_script.bc generate_compiled_sieve_script: 1 I don't think I've tried all of the combinations of them yet but they don't appear to work. and in /usr/share/doc/cyrus-imapd-2.2.10/README.autosievefolder there is no mention of those items. I appreciate your offer of the packages and note that apparently fedora-3 is using some derivative of your packages since I recall seeing the name on some file they distribute. I am going to try to stick with that which is distributed by fedora package for automated updates, etc. and so that really leaves me option 2 - which isn't so terrible since I have the bytecoded script in hand and I will script new users anyway. I might put in a bugzilla entry into fedora though... Thanks 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: automated delivery of sieve scripts for new users
> On Wed, 2005-02-02 at 12:54 -0600, John Wade wrote: >> Craig White wrote: >> >> > 1 - Is there a way to automatically set a sieve script to new users >> > created on a system? >> >> I believe this is a part of the latest autocreate patch from the >> University of Athens. >> http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.10/cyrus-imapd-2.2.10-autocreate-0.9.1.diff > > hmm...looking at the diff, I wondered if that was already in my imapd > configuration... No, IIRC it includes an older patch without the autocreate_sieve_script feature. Take my rpms which include it: http://www.invoca.ch/pub/packages/cyrus-imapd/ Simon > # rpm -qa|grep cyrus-imap > cyrus-imapd-2.2.10-3.fc3 > cyrus-imapd-devel-2.2.10-3.fc3 > cyrus-imapd-utils-2.2.10-3.fc3 > cyrus-imapd-nntp-2.2.10-3.fc3 > cyrus-imapd-murder-2.2.10-3.fc3 > > so far so good > added to imapd.conf > autocreate_sieve_script: /etc/default_sieve_script > > restarted - cyrus-imapd > no complaints - syslog seems happy > > telnet localhost imap and logged in as jennifer > ls -l /var/spool/imap/j/user/jennifer/INBOX and other > autocreateinboxfolders are there...(nice feature by the way) > ls -l /var/lib/imap/sieve/ - no j no jennifer ;-( > > OK - so I would have to patch source and re-install I guess... ;-( > I may be too lazy to do this and resort to #2 below as it appears that I > have to do some scripting anyway... > >> > 2 - Is there a way to insert sieve scripts without having to type a >> > password at the console (for automation)? >> >> Athough it kind of goes against the Cyrus blackbox mentality, you should >> be able to just do the following in a script as the cyrus user. >> >> 1. Create the user's sieve directory >> 2. Copy your script into the directory with a .script extension. >> 3. Use sievec to compile the script (i.e. /usr/lib/cyrus-imapd/sievec >> .script .bc) >> 4. Symbolically link the script to make it active: ln -s >> default.bc >> >> We have certainly done these steps during conversions. (Note binary >> compilation is only required with the latest versions of Cyrus.) >> >> Hope this helps, > > Indeed it has helped - it cut to the quick. > > Thanks > > 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 > > --- 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: automated delivery of sieve scripts for new users
On Wed, 2005-02-02 at 12:54 -0600, John Wade wrote: > Craig White wrote: > > > 1 - Is there a way to automatically set a sieve script to new users > > created on a system? > > I believe this is a part of the latest autocreate patch from the > University of Athens. > http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.10/cyrus-imapd-2.2.10-autocreate-0.9.1.diff hmm...looking at the diff, I wondered if that was already in my imapd configuration... # rpm -qa|grep cyrus-imap cyrus-imapd-2.2.10-3.fc3 cyrus-imapd-devel-2.2.10-3.fc3 cyrus-imapd-utils-2.2.10-3.fc3 cyrus-imapd-nntp-2.2.10-3.fc3 cyrus-imapd-murder-2.2.10-3.fc3 so far so good added to imapd.conf autocreate_sieve_script: /etc/default_sieve_script restarted - cyrus-imapd no complaints - syslog seems happy telnet localhost imap and logged in as jennifer ls -l /var/spool/imap/j/user/jennifer/INBOX and other autocreateinboxfolders are there...(nice feature by the way) ls -l /var/lib/imap/sieve/ - no j no jennifer ;-( OK - so I would have to patch source and re-install I guess... ;-( I may be too lazy to do this and resort to #2 below as it appears that I have to do some scripting anyway... > > 2 - Is there a way to insert sieve scripts without having to type a > > password at the console (for automation)? > > Athough it kind of goes against the Cyrus blackbox mentality, you should > be able to just do the following in a script as the cyrus user. > > 1. Create the user's sieve directory > 2. Copy your script into the directory with a .script extension. > 3. Use sievec to compile the script (i.e. /usr/lib/cyrus-imapd/sievec > .script .bc) > 4. Symbolically link the script to make it active: ln -s > default.bc > > We have certainly done these steps during conversions. (Note binary > compilation is only required with the latest versions of Cyrus.) > > Hope this helps, Indeed it has helped - it cut to the quick. Thanks 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: automated delivery of sieve scripts for new users
Craig White wrote: > 1 - Is there a way to automatically set a sieve script to new users > created on a system? I believe this is a part of the latest autocreate patch from the University of Athens. http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.10/cyrus-imapd-2.2.10-autocreate-0.9.1.diff > 2 - Is there a way to insert sieve scripts without having to type a > password at the console (for automation)? Athough it kind of goes against the Cyrus blackbox mentality, you should be able to just do the following in a script as the cyrus user. 1. Create the user's sieve directory 2. Copy your script into the directory with a .script extension. 3. Use sievec to compile the script (i.e. /usr/lib/cyrus-imapd/sievec .script .bc) 4. Symbolically link the script to make it active: ln -s default.bc We have certainly done these steps during conversions. (Note binary compilation is only required with the latest versions of Cyrus.) Hope this helps, John Wade --- 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
automated delivery of sieve scripts for new users
1 - Is there a way to automatically set a sieve script to new users created on a system? 2 - Is there a way to insert sieve scripts without having to type a password at the console (for automation)? Similar but different questions - I think you get the point. Can you point me to URL's ? I didn't see much in the docs about this (in fact - sieve has been a slippery beast) 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
