Yeah, I'm not sure if the acl variable would be set in that case either.
Either way though, I was more trying to find a way to kill off the
requirement for a second duplicate condition test to achieve the end result.
Just seems a little silly that I'd have to double up a condition test to do
this since I know from the first test it will fail, I just want to add a
message letting the receiver know :P
I believe Exim actually does let you have a message within an accept
statement, it's just that it doesn't seem to honor it by adding the header.
I at least don't see any *harm* in this feature being added, so I'd assume
it wouldn't be a big deal to do?
Eli.
-----Original Message-----
From: Bradford Carpenter [
mailto:jbc@mac.com]
Sent: Thursday, January 22, 2004 9:35 PM
To: eli-list@???
Subject: Re: [Exim] Allow message to work with accept in ACLs?
On Thu, 22 Jan 2004 17:41:47 -0500, Eli wrote:
> I was wondering if anyone else has though of having this feature or not?
>
> Currently I have my spam scanning ACL do this at the top:
>
> warn message = X-Spam-Error: Message too big, scan
> skipped
> condition = ${if > {$message_size}{5M} {yes}{no}}
>
> accept condition = ${if > {$message_size}{5M} {yes}{no}}
>
> So that it can bypass any emails that are too large for scanning. I don't
> like having to duplicate an identical condition in two places since I
later
> plan to use MySQL to get the message size limit, so I'd be doing 2 queries
> when it would be nice to reduce it to just 1.
As far as not doing two queries, I'd think you could use an acl
variable:
warn message = X-Spam-Error: Message too big, scan skipped
condition = ${if > {$message_size}{5M} {yes}{no}}
set acl_m5 = skipscan
accept condition = ${if eq{$acl_m5}{skipscan} {yes}{no}}
Exim Specs don't really say explicitly, but "the processing of a verb
ceases as soon as its outcome is known" would seem to indicate the
variable will not get set if the condition fails. You'd still need two
condition statements and two verbs, though.
Brad
