without modifying code.

I've deployed this here on drupal.org and I think that the threat level of 1 is too low for continuous operation. I've increased it to 20. I'd like to do that in the admin UI.

Comments

bryrock’s picture

bryrock commented
Assigned: Unassigned » bryrock

+ Assignment

bryrock’s picture

bryrock commented
Status: Active » Needs review

Configurable greylisting threshold has been added to admin settings UI. Options are 1, 2, 3, 4, 5, 10, 15, 20, 25, 30, 35, 40, 45.

This has been committed to the 6.x-2.x-dev fork. If all goes well then I'll put out a 6.x release soon. Will also add to 7.x.

killes@www.drop.org’s picture

killes@www.drop.org commented

Thanks!

Can you add a variable for blacklisting too? I find that 50 is a bit rigid. In particular I'd like to be able to switch off blacklisting completely.

Also, http:bl gives back more information than just a value. It also gives back a "last seen" value. I'd like to be able to use this also for denying access.

bryrock’s picture

bryrock commented

Could you give me some example scenarios of how you'd like to use "last seen" in conjunction with the threat level? In other words, what sort of priorities do you have in mind when evaluating a visitor for grey-listing consideration?

killes@www.drop.org’s picture

killes@www.drop.org commented

I think the simplest case would be to whitelist everything that has a "last seen" value greater than a configurable value. 2 weeks for example.

bryrock’s picture

bryrock commented

Regardless of threat level in any respect?

killes@www.drop.org’s picture

killes@www.drop.org commented

Yeah, I think it would be hard to come up with an algorithm.

RogueM’s picture

RogueM commented

subscribe

bryrock’s picture

bryrock commented

Since greylisting is now configurable, I'll ask that the feature requests for blacklisting and the "last seen" variation be moved to new, separate issues so that this greylisting issue can closed without other contingencies.

RogueM’s picture

RogueM commented

double post

RogueM’s picture

RogueM commented

OK, but when you say 'Since greylisting is now configurable', this is only true of the 6.x version right? I updated http:BL yesterday and can't see any way (besides modifying the threshold manually in httpbl.module) though I'm using Drupal 7.7 and therefore the 7.x version of the module.

bryrock’s picture

bryrock commented
Status: Needs review » Fixed

Configurable greylisting threshold is now also available in 7.x-1.0-rc3.

RogueM’s picture

RogueM commented

great stuff!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.