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
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-ter
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
ve
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
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-ter
