So the action limitations need to be spelled out in the draft, right?
That is, some actions need to prohibit other actions from happening.
obviously necessary:
* Only one reply per message is reasonable. (You can only reply to one
place.)
* Only one reject per message. (You can only reject the message to the
sender once.)
good ideas:
* reject prohibits forward. (or forward prohibits reject.)
* reject prohibits keep/fileinto.
possibilities:
* only one forward per message.
In the case where there's a conflict, what happens? Three possibilities:
* require implementations to reject any script they can't guarantee will
have problems (this is pretty hard)
* take the first/last action specified, and just get on with life
* run-time error, do a keep, then mail the user explaining what happened
--
Tim Showalter
tjs+(_at_)andrew(_dot_)cmu(_dot_)edu