In the implementation of sieve for Cyrus that I'm working on, I'm
following the following convention:
Running a script accumulates a list of actions to take.
Upon successful termination of the script, ALL actions are taken.
Currently, this allows unlimited fileinto's and forward's.
If no actions have been accumulated by script termination, a keep is
performed.
If an action conflicts with an action already on the list, there's a
run-time error. That is, if a "keep" has been specified and then we
come across "reject", that's an error. "reject" and "discard"
conflict with all other actions (and each other). "fileinto",
"forward", and "keep" can all be performed together.
If any run-time errors occur, a "keep" is performed.
---
I think this is a logical collection of rules. Site policies may want
to limit the number of forwards or fileintos done.
Larry