Pkg exim4 users - Jun 2011 - save, in a user filter, is not a significant command

Consider the following user filter:

    $ cat .forward
    # exim filter
    
    if $h_subject: is "exim filter bug"
    then
      testprint "$h_subject printed by is operator"
      seen save bug
    endif
    deliver jc at rome.example
    $ 

  Here, without the seen modifier, a message with the right subject
will be saved, and also sent to jc at rome.example.  Is that expected with
the out of the box configuration?

Regid Ichira <regid23 at yahoo.com> wrote:
>  Consider the following user filter:
>    $ cat .forward
>    # exim filter
>    if $h_subject: is "exim filter bug"
>    then
>      testprint "$h_subject printed by is operator"
>      seen save bug
>    endif
>    deliver jc at rome.example
>    $ 
>  Here, without the seen modifier, a message with the right subject
> will be saved, and also sent to jc at rome.example.  Is that expected with
> the out of the box configuration?
Hello,
Yes it is. exim filter processing does not stop on the first match.
Exim will happily save five local copies and forward three new copies
to external addresses. If you want to save the message to the bug
mailbox and stop processing of matching addresses afterwards, use the
finish command:

--------------------
# exim filter
if $h_subject: is "exim filter bug"
then
  testprint "$h_subject printed by is operator"
  save bug
  finish
endif
deliver jc at rome.example
--------------------

The existence of significant deliveries influences what happens
*after* the filter was processed. i.e. whether exim will need to run
the message through another router (e.g. delivery to /var/mail/) or
whether the message was processsed and delivered by the filter.
However as "save" is significant by default "seen save bug"
and "save
bug" cause exactly the same behavior. 

cu andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.''
`I sew his ears on from time to time, sure''