Author: W B Hacker Date: To: exim users Subject: Re: [exim] ACL rule
jean-paul natola wrote: >>>>>> I want to tell exim NOT to send messages over 1Mb to spamassassin
>>>>>> for> > scanning? What is the syntax> > Set a macro, e.g.:
>>>>>> 'SCAN_MAX', in the 'main' section.> > SCAN_MAX = 1M> > > and where
>>>>>> in the config file do I place it?> > > > At an acl in
>>>>>> 'acl_smtp_data' (older Exim)> or in 'acl_smtp_mime' (newer Exim -
>>>>>> also acl_not_smtp_mime for local) and in > either case *before*
>>>>>> invoking SA or <whatever other> scanner(s):> > Use something like
>>>>>> this:> > # DATA_18_SCAN_3: IF message larger than SCAN_MAX, THEN
>>>>>> log,> # deny OR warn AND accept unscanned, advising recipient.> #
>>>>>> deny> warn> condition = ${if >{$message_size}{SCAN_MAX} {true}}>
>>>>>> message = X-Oversize: Message too large to scan.> log_message =
>>>>>> D18S3 Passed unscanned - exceeds SCAN_MAX
> I was follwoing you ok up to this point
>
>> set acl_m19 = 1> > > THEN test the acl_m19 (or whatever) value before
>> invoking scanning.
>>
> >
>
>> You may use more than one of these if you want separate limits for SA,
>> ClamAV, > et al.
> Ideally I would like i meg to for both SPAM and Clam
>
>
Another poster has shown a single-step test.
The one above sets an acl_m(n) variable for two reasons:
- It is easier to test the variable multiple times than to perform the size
comparison multiple times.
- an acl_m(n) variable 'travels' all the way thru DATA phase into the queue,
hence is available to be read in router/transport sets, used there to manipulate
routing, headers, etc.
