[SA-exim] PermReject

[Marc MERLIN]

On Wed, May 29, 2002 at 09:10:56PM -0400, Patrice Fournier wrote:
> If you leave the X-Spam-Flag: check there, it also means that a spam tagged
> as such by another system won't be rejected by sa-exim even if it scored
> 200, right?
 
Correct, and it may not be what you need/want
 
> hmmm.. is $local_part really available there? What's in there when the

No.

> message is destined to multiple recipients? Why don't we use this to check
> for postmaster instead of the X-SA-Disable header?
 
You can't access $local_part when you get there.

hence, you need this

  warn     message       = X-SA-Disable: yes
             local_parts   = postmaster
 
> While were at it, as anyone configured sa-exim to scan/reject messages to
> some users while accepting it to others?

I remember having done so

> I was thinking about something like this using the rcpt ACL:
> if (first recipient)
>   set a variable/header to indicate if SA must run for that recipient
> else
>   if (current_recipient SA setting != first recipient SA setting)
>     temp reject

I'm not sure I understand, and not sure what you want to do would work
either.

> Now, if SA setting is a boolean value sometimes some recipients will
> receive temp reject thus permiting us to still reject the message at SMTP
> time for those users who don't want it. Of course, this is best if no other
> ACL can produce temp reject (or at least, will not do so most of the time)

local_scan runs after DATA, you can't have  it do some things for some users
and other things for other users unless you duplicate the mail and refeed it
to exim
The local_scan  code does have  access to the  list of receipients,  but you
can't use them in condition since local_part  would eval to a list and not a
value.

> How does yahoo does rejections of only some of the recipients? (it's yahoo

mail from: <myadd@domain.tld>
250 sender <myadd@domain.tld> ok
rcpt to: <marcmerlinns@yahoo.com>
250 recipient <marcmerlinns@yahoo.com> ok
data
354 go ahead
test