> > On 28.04.10 12:59, Alessandro Vesely wrote:
> >> You mean you read recipients from ctlfile lines starting with "r"?
> On 28/Apr/10 19:51, Matus UHLAR - fantomas wrote:
> > I already do it in our logging filter.
On 29.04.10 18:48, Alessandro Vesely wrote:
> Fine. I hoped to find a trick to do it for all filters at once.
Since I will need to check for recipients and parse them by two functions
(logging and phish checking), I think I'll split the functionality first to
get recipients, then process them, where all functions will be able to
process them.
Hmmm, as long as we're already parsing the mail header to get the
message-id, I'll apparently be able to parse recipients from header, howevee
I don't need it yet.
> >> 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.)
I get quite much spam to abuse mailbox, its address is mentionsd in RIPE
(RIR) database. Looking at it, we get many reports that do not contain our
address(es) in headers but are informational for us (well, if they are real
reports...?)
> 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?
> 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
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
99 percent of lawyers give the rest a bad name.
------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
