On man, 2004-10-25 at 06:35 -0700, Marc Perkel wrote:
> The principle of either implicit keep or explicit keep means to "keep"
> the message.
I don't see any reason why an implicit keep should behave differently
from an explicit keep, and I think it would be a mistake to make it
possible to distinguish them.
> In most systems to keep the message means to deliver it to
> the inbox. But - suppose the inbox was not the default destination for
> mail? Then doesn'r keep really mean to deliver to the default destination?
that's just playing with words. what does "inbox" mean if not "default
destination"? Sieve does not mandate anything about how the mail is
stored.
> In my case keep mean pass it on to a series of routers that does the
> keep for me.
that's fine.
> In some cases there is no inbox to keep to. I process email
> that is eventually delivered to other hosts for delivery (preprocess
> spam filtering). So keep for those domains means to pass the message on
> to the target host. So - if seive remains restrictive that it has to
> deliver to a mailbox - it's totally useless in my environment.
Sieve is not restrictive.
--
Kjetil T.
