Frank Cusack wrote:
On December 28, 2009 10:50:32 PM +0100 Stephan Bosch
<[email protected]> wrote:
See the solution I presented elsewhere in this thread. That should do
just that.
Not if the user has control over his sieve scripts though (in which
case anything can happen).
That's the idea of a sieve_before script. That can only be set and
administered by the system administrator. If the script finishes without
error, all actions executed therein are definitive and cannot be
influenced by the subsequently executed user script.
Regards,
Stephan.
