Re: Timed Actions in Sieve
On Tue, Nov 13, 2007 at 11:24:48AM +, Ian G Batten wrote: > We've been having a chat about how useful it would be to have timed > actions in sieve: so that a vacation message could be set up for a > duration which would automatically revert, so that a forwarding could > be set up for the duration of a short-term project, etc, etc. The > naive way is to add support to the sieve interface of choice (the > squirrelmail plugin in our case) to handle deferred actions, but I > can think of all sorts of security problems with that. Another would > be a means to auto-generate regexps to match on Date: headers, but > that's really tacky. The full solution would be to have the current > time available in sieve scripts, to then match on. Has anyone else > thought about this area? We've had occasional complaints from people who set up a vacation message and then forgot to remove it later. They would like to be able to put a time limit on such things, so that they would stop working when that limit expires. More generally, I suppose they could specify start and stop times, so that they could set up the sieve script in advance of their vacation. -- -Gary Mills--Unix Support--U of M Academic Computing and Networking- 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
Re: Timed Actions in Sieve
Zitat von Ian G Batten <[EMAIL PROTECTED]>: > We've been having a chat about how useful it would be to have timed > actions in sieve: so that a vacation message could be set up for a > duration which would automatically revert, so that a forwarding could > be set up for the duration of a short-term project, etc, etc. The > naive way is to add support to the sieve interface of choice (the > squirrelmail plugin in our case) to handle deferred actions, but I > can think of all sorts of security problems with that. Another would > be a means to auto-generate regexps to match on Date: headers, but > that's really tacky. The full solution would be to have the current > time available in sieve scripts, to then match on. Has anyone else > thought about this area? > > ian There seams to be some work is this area already : http://tools.ietf.org/html/draft-freed-sieve-date-index-07 Anyone aware of the status of this project?? Regards Andreas 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
Re: Timed Actions in Sieve
I had looked into this before, but really haven't had a chance to follow up on it. There is an draft for a sieve date/time extension, which allows you to use time comparisons in conditionals -- for example, the vacation message defined by a date range. This looks like its the current version of the draft: http://tools.ietf.org/html/draft-freed-sieve-date-index-07 On Nov 13, 2007, at 06:24, Ian G Batten wrote: > We've been having a chat about how useful it would be to have timed > actions in sieve: so that a vacation message could be set up for a > duration which would automatically revert, so that a forwarding could > be set up for the duration of a short-term project, etc, etc. The > naive way is to add support to the sieve interface of choice (the > squirrelmail plugin in our case) to handle deferred actions, but I > can think of all sorts of security problems with that. Another would > be a means to auto-generate regexps to match on Date: headers, but > that's really tacky. The full solution would be to have the current > time available in sieve scripts, to then match on. Has anyone else > thought about this area? > > ian > > > 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 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
Re: Timed Actions in Sieve
I had the same problem and solved it using a bash programan that generates the necesary sieve scripts. This is run with cron every day at night It checks for configuration request on a directory, process those files and creates sieve scripts for vacation activation and for deactivation, finaly it uses sieveshell to upload the scripts. At this moment this scripts are in their first version I hope to improve them but It would be better to have this functionality in sieve. bye Listaccount wrote: > Zitat von Ian G Batten <[EMAIL PROTECTED]>: > > >> We've been having a chat about how useful it would be to have timed >> actions in sieve: so that a vacation message could be set up for a >> duration which would automatically revert, so that a forwarding could >> be set up for the duration of a short-term project, etc, etc. The >> naive way is to add support to the sieve interface of choice (the >> squirrelmail plugin in our case) to handle deferred actions, but I >> can think of all sorts of security problems with that. Another would >> be a means to auto-generate regexps to match on Date: headers, but >> that's really tacky. The full solution would be to have the current >> time available in sieve scripts, to then match on. Has anyone else >> thought about this area? >> >> ian >> > > This would be for sure a really useful extension for sieve. The Horde > Project (www.horde.org) has the same problem for the sieve web > interface "Ingo" where it is up until now solved by regexp matching > headers. But as headers can be forged and unreliable (wrong system > clock at sending site) a sieve extension for access the local system > time/timezone and compare against it would be preferable. > > Regards > > Andreas > > > 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 > -- Juan Pablo Baudoin Gerente Nacional de sistemas Kieffer & Asociados Tel: (591) 2 243 3434 Cel: (591) 720 01485 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
Re: Timed Actions in Sieve
Zitat von Ian G Batten <[EMAIL PROTECTED]>: > We've been having a chat about how useful it would be to have timed > actions in sieve: so that a vacation message could be set up for a > duration which would automatically revert, so that a forwarding could > be set up for the duration of a short-term project, etc, etc. The > naive way is to add support to the sieve interface of choice (the > squirrelmail plugin in our case) to handle deferred actions, but I > can think of all sorts of security problems with that. Another would > be a means to auto-generate regexps to match on Date: headers, but > that's really tacky. The full solution would be to have the current > time available in sieve scripts, to then match on. Has anyone else > thought about this area? > > ian This would be for sure a really useful extension for sieve. The Horde Project (www.horde.org) has the same problem for the sieve web interface "Ingo" where it is up until now solved by regexp matching headers. But as headers can be forged and unreliable (wrong system clock at sending site) a sieve extension for access the local system time/timezone and compare against it would be preferable. Regards Andreas 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
Timed Actions in Sieve
We've been having a chat about how useful it would be to have timed actions in sieve: so that a vacation message could be set up for a duration which would automatically revert, so that a forwarding could be set up for the duration of a short-term project, etc, etc. The naive way is to add support to the sieve interface of choice (the squirrelmail plugin in our case) to handle deferred actions, but I can think of all sorts of security problems with that. Another would be a means to auto-generate regexps to match on Date: headers, but that's really tacky. The full solution would be to have the current time available in sieve scripts, to then match on. Has anyone else thought about this area? ian 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
