Re: [courier-users] Whitelist filtering, including a draft patch

2013-01-25 Thread Alessandro Vesely
On Thu 24/Jan/2013 13:08:21 +0100 Sam Varshavchik wrote: Just looking at the results of trying to meta-program the DNSBL lookup logic in couriertcpd, using pcre, doesn't look right to me. PCRE in couriertcpd would be ok, it's just all the rest of it looks overly complicated. Yeah, it

Re: [courier-users] Whitelist filtering, including a draft patch

2013-01-24 Thread Alessandro Vesely
On Thu 24/Jan/2013 02:00:15 +0100 Sam Varshavchik wrote: Alessandro Vesely writes: -allow=zone[,varspec]... [...] Now for passing the results to global filters. In 2010 we thought of I still think -allow is ok, but I don't see much need to do anything with regards to the headers. If

Re: [courier-users] Whitelist filtering, including a draft patch

2013-01-24 Thread Sam Varshavchik
Alessandro Vesely writes: Global filters, however, cannot. My initial idea was to use ctlfile records to pass values to --and possibly among-- filters. It's you who said it's simpler to use the message header (there were traces of that argument quoted in my previous message.) Perhaps, but

Re: [courier-users] Whitelist filtering, including a draft patch

2013-01-23 Thread Alessandro Vesely
Hi Sam and All, let me try and resume this: -allow=zone[,varspec]... By example --so as to solicit comments from more people-- the change enables to configure an additional variable in etc/esmtpd: WHITELISTS='-allow=swl.spamhaus.org' The default behavior is to set an empty BLOCK= so that

Re: [courier-users] Whitelist filtering, including a draft patch

2013-01-23 Thread Sam Varshavchik
Alessandro Vesely writes: Hi Sam and All, let me try and resume this: -allow=zone[,varspec]... By example --so as to solicit comments from more people-- the change enables to configure an additional variable in etc/esmtpd: WHITELISTS='-allow=swl.spamhaus.org' The default behavior is to