On 30/Apr/10 11:06, Matus UHLAR - fantomas wrote:
> On 28.04.10 12:59, Alessandro Vesely wrote:
>>  The mechanism I was referring to is the one that sets whitelisting from 
>> rcptfilters. Courier splits recipients by temporarily rejecting the 
>> non-matching ones, so as to force the client to send the message twice.
>
> That is precisely what I'd like to achieve:
>
> if first recipient is abuse, temporarily reject all non-abuse recipients
> if first recipient is not abuse, temporarily reject all abuse recipients
>
> but looking at rcptfilter, I can't imagine how I'd implement this, do you 
> have any hints?

Not many, besides the considerations below. I try and change the 
subject to see if I can catch Sam's attention on whether that extra 
smtpfilter is really needed...

>>  Global filters not using the "allfilters" socket directory can be skipped 
>> that way, so this could be the trick I was looking for. However, moving all 
>> filters to plain "filters" mode would then require an extra smtpfilter call 
>> for the normal case of global filters being active, if I've understood it 
>> correctly. IOW: by returning 99, rcptfilters enable _both_ global plain 
>> filters and local content filters. There is no way to enable global but not 
>> local ones, is there?

After the splitting mechanism, yet another possibility to whitelist 
global filters, in case one runs multiple ones, is to return "000 Ok." 
from, say, 0filter (the first one in its directory). However, this 
kind of "STMP response" is not documented in 
http://www.courier-mta.org/courierfilter.html so Sam's confirmation is 
needed also for this bit.

-- 


------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to