On 28/Apr/10 19:51, Matus UHLAR - fantomas wrote:
> On 28.04.10 12:59, Alessandro Vesely wrote:
>>  You mean you read recipients from ctlfile lines starting with "r"?
>
> I already do it in our logging filter.

Fine. I hoped to find a trick to do it for all filters at once.

>>  How are you going to handle an abusive message for multiple
>>  recipients, only one of which is<abuse>  or<postmaster>? Courier
>>  already has a whitelisted/not-whitelisted mechanism, but it only works
>>  for whitelistable filters...
>
> what would be the difference between multiple recipients in To/Cc and in
> envelope ?

Not much, besides what Michelle noted. I guess it is a policy rule. A 
site's policy might be to only concede special whitelisting when 
<abuse> --or <postmaster>-- is the sole recipient, equally addressed 
in envelope and header. (BTW, I get very few spam into these 
mailboxes, compared to what I get in into the others.)

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.

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?

As a final note, recent TB versions apparently skip filtering if 
.mailfilter has something like

   if ($nofiltering)
   {
     KEYWORDS="NonJunk"
     to "./Maildir/.MyAbuseFolder"
   }

-- 

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

Reply via email to