On Wed, Oct 20, 2004 at 02:06:09PM -0700, Marc Perkel wrote:
> I'm wanting to use the seive router to be used for exceptions and have
> it fall through to the next routers if the seive doesn't do anything.
Sieve, as defined by RFC 3028, requires that if the filter does not
do anything, an implicit 'keep' is executed, that is the same as
'fileinto "inbox"'. The RFC is pretty clear about what 'fileinto'
does:
The "fileinto" action delivers the message into the specified folder.
If you were into reading too many laws, you could probably say that at
your place, delivery into the inbox folder means to pass on to the next
router. :) I am not sure if the router could still fail if $address_file
is "inbox", but even if it could do that, I don't suggest it. The good
thing about Sieve is being a standard. If it does not fit, then don't
use it. I suggest an Exim filter for such applications.
Personally, I don't like the implicit keep being defined the way it is,
because it forbids using the filter for aliases without assigned storage.
Too late to change the standard, though.
Michael
