On Thu, 06 Sep 2007 10:11:38 -0700
JT Moree [EMAIL PROTECTED] wrote:
My idea would be that there are only two things that can be whitelisted:
connections and transactions. On the base of what logic, and at what
stage, is up to the plugin, but if the whitelist flag is set, any DENY*
return
On Sat, Sep 15, 2007 at 08:27:19AM +0200, Hanno Hecker wrote:
I'm not really happy with the all or nothing approach of whitelisting /
blacklisting. There should be a score based whitelist, which can be
fine tuned by the admin.
Blacklisting and whitelisting _are_ all or nothing, by definition.
On 15-Sep-07, at 2:27 AM, Hanno Hecker wrote:
The current dnsbl plugin returns DENY if the client is in one of the
given lists, but there are some lists I trust more than others. I'd
like to see something where I can set a score right below the
threshold
for (e.g.) the geoip plugin and then
Fuelled by some of the recent discussions, I think the whitelisting
concept needs to be re-thought.
i agree
My idea would be that there are only two things that can be whitelisted:
connections and transactions. On the base of what logic, and at what
stage, is up to the plugin, but if the
On 6-Sep-07, at 11:33 AM, Johan Almqvist wrote:
My idea would be that there are only two things that can be
whitelisted: connections and transactions. On the base of what
logic, and at what stage, is up to the plugin, but if the whitelist
flag is set, any DENY* return value from subsequent
On 6-Sep-07, at 1:47 PM, Johan Almqvist wrote:
Matt Sergeant wrote:
The way I see it is that whitelisting is basically meant as a
bypass for anti-spam filters, but not (for example) certain other
filters (like recipient checks). So I wondered if hooks should
declare themselves as
csere matyas wrote:
we have a client that doesnt want to loose any mail, and asked us not to
scan any mail addressed to him.
is there a way to do recipient whitelisting, eg if the mail is to
[EMAIL PROTECTED] it would always pass, and get delivered?
Make a copy of plugins/check_badrcpto and
On 2006-01-31 11:09:55 +0100, csere matyas wrote:
we have a client that doesnt want to loose any mail, and asked us not to
scan any mail addressed to him.
is there a way to do recipient whitelisting, eg if the mail is to
[EMAIL PROTECTED] it would always pass, and get delivered?
Gavin
On Thu, Jan 29, 2004 at 04:38:24PM +0200, Aric Fedida wrote:
So now the question is, how do I whitelist a certain ip address, so that
qpsmtpd plugins will be bypassed for that ip address?
As a halfway measure, you could whitelist their HELO with the whitelist
plugin I posted here a while back.
[crass self reply]
On Thu, Jan 29, 2004 at 11:02:49AM -0800, Devin Carraway wrote:
As a halfway measure, you could whitelist their HELO with the whitelist
plugin I posted here a while back. Whitelisting a remote host is a
valid case, I'll see what would be involved there.
Okay, I feel
Peter,
Your scoring suggestion wouldn't be hard to implement.. every
plugin can return DECLINED and set a score in the -{notes} data
structure somewhere. The last plugin to run can look at the score
and decide to (OK,DENY).
But I wouldn't want that to be the default. At
On 2003-09-20 09:13:48 -0700, Robert Spier wrote:
Your scoring suggestion wouldn't be hard to implement.. every
plugin can return DECLINED and set a score in the -{notes} data
structure somewhere. The last plugin to run can look at the score
and decide to (OK,DENY).
Yup,
12 matches
Mail list logo
