Reindl Harald wrote:
> I have no idea how i should do this with sieve in future because we
> switch here from mysql-database to a protocl and afaik there
> can be only one active sieve-script for each user
I'm not sure I understand what you're saying here.
Indeed, there can be only one active sieve script per user. But there is
nothing to prevent you from inserting sieve scripts directly through the
sql interface. No need to go through timsieved, unless you want to make
sure scripts are valid.
the basic autoreply sievescript reads as:
-------
require "vacation";
if true {
vacation :days 7 :addresses [$ADDRESS] :subject "$SUBJECT" "$BODY";
}
-------
where $ADDRESS is a comma delimited list of address that should respond,
$SUBJECT is the subject header for the reply message and $BODY is the,
well, body.
you can easily prepend this sieve snippet to any active sievescript, if
you allow users to set their own filters.
there is also a couple of PHP (and at least one python) implementations
of the client side of managesieve (the protocol spoken by dbmail-timsieved).
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
