On Sun, 2006-11-26 at 23:07 +0100, Kjetil Torgrim Homme wrote:
On Sun, 2006-11-26 at 13:46 -0800, Aaron Stone wrote:
The special considerations I can think of are that the implicit keep
does not cross between the postmaster script and the user's script,
except in the case of a reject. That is, if the postmaster does a
fileinto, discard, keep, redirect, whatever, this affects only the
"postmaster's copy" of the message. A reject should trash the message
and cancel the user's delivery, however.
Hmm. Can of worms? Can we tease out a consistent behavior? Would
recommending a dummy postmaster user solve the managesieve question for
global scripts?
sounds to me like you want to use this to duplicate e-mail, for SarbOx
archival purposes or whatever. I don't think this is relevant for
Sieve. make the copy in your MTA so that the archival account is a
firstclass citizen as far as Sieve is concerned.
I'm sure some of my users have this in mind, and others have other
things in mind. If I provide multiscript functionality, that's one
feature for me to write and many purposes they can use it for.
I do agree that the specific case of keeping a second copy of mail is
probably better done by an MTA hook, if possible, but I don't see any
reason to prevent a Sieve script from being used for this purpose. Let's
not hang the whole discussion on this one use case, however -- given
that Ned and Tony have both said that their implementations have some
form of multiscript, I think we can assume that it is useful enough to
look into some more.
Aaron