Zitat von Ian G Batten <ian.batten@xxxxxxxxxxxxxx>: > 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
