Re: [exim] Enhancing Seive definitions in the Exim environme…

Top Page
Delete this message
Reply to this message
Author: Marc Perkel
Date:  
To: Tor Slettnes
CC: Exim User's Mailing List
Subject: Re: [exim] Enhancing Seive definitions in the Exim environment
How about a separate command for an explicit keep too?

explicit_keep = {false|true}

The reason being that to me "keep" means to pass it to the next router
which will eventually keep it. On my setup I will NEVER do direct
delivery to files from Sieve. To me "keep" means the same as "finish" in
exim routers.


Tor Slettnes wrote:

>
> You are not addressing "implicit keep" with a setting like that --
> that wording seems to be applying to explicit keeps as well.
>
> In fact, I think that setting would be a bad idea. Even if you
> explicitly said "keep" in your sieve filter, the router would be
> skipped. That's not what sane people consider "keep" to mean.
>
> Better to make only _implicit_ "keep" optional:
> implicit_keep = {false|true}
>
> ("true" being default, per RFC).
>
>
> -tor
>
>