AW: AW: [Exim] problem with nested condition

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Lumpp, Wolfgang
Date:  
À: exim-users
Sujet: AW: AW: [Exim] problem with nested condition
Hi,

> Von: Nico Erfurth [mailto:masta@perlgolf.de]
> Lumpp, Wolfgang wrote:
>
> > sorry, but same error-message.
> > I've crosschecked it several times.
>
> Oooppps, you did not open the first condition
>
> ${if and { \
>             { \
>               or { \
>                 {match {$header_X-Spam-Status:}{\N.*hits=0\..*\N}} \
>                 {match {$header_X-Spam-Status:}{\N.*hits=1\.0.*\N}} \
>                 {match {$header_X-Spam-Status:}{\N.*hits=-.*\N}} \
>               }\
>             } \
>             {< {$message_size}{1M}} \
>           }{yes}{no}}

>

Now I've got it ;-)

Thats the router:
    condition = ${if and { \
                { \
                or { \
                    {match
{$header_X-Spam-Status:}{\N.*hits=0\..*\N}} \
                    {match
{$header_X-Spam-Status:}{\N.*hits=1\.0.*\N}} \
                    {match
{$header_X-Spam-Status:}{\N.*hits=-.*\N}} \
                } \
                } \
            { < {$message_size}{300k}} \
            { !def:h_X-Size:} \
            }{yes}{no}}
    driver = accept
    transport = spam_deliver
    unseen


This one sits directly after the amavisd-new router.
The transport is an appendfile, where I get the mail 2 times :-(
Therefore I tried to add the X-Size header in the amavis router to detect it
in the spam_deliver_router.
How can I avoid this behaviour?

Thanks
Wolfgang