Milter-greylist

Hello list,

Theres another though of nice enchancement of greylist.db, 
and its about some more information in the # Summary field:

Today it looks like this:

#
# Summary: 16704 records, 1132 greylisted, 15572 whitelisted
#

My RFE would be to add a extra column i the summary for those connections that never made it to the auto-whitelist state, those who got rejected, timed-out or flushed whatever you want to call it. 

My idea was that the "flushed" would just be a simple counter which would add +1 every time a entry from the greylisted-part of the database expired. To make the "flushed"-counter easier to implement/code, it should always count every flushed entry from the greylisting-db. 
Even if two separate db-entries came to the same recipient, from the same sender, form the same relay-ip twice (a almost indentical truple, except for the time). So, no extra memory of which truples that got flushed.
And of course, the first truple has to timeout before the second one is collected, otherwise it will be auto-whitelisted...

So it would look like this perhaps:

#
# Summary: 16704 records, 1132 greylisted, 15572 whitelisted, XXX flushed
#

Would it be useful to anyone else?

I think it would be nice to see a small summary of how many Spam/UCE milter-greylist accually kicks during runingtime :-)

/P

On Thu, 2005-07-21 at 19:25 +0200, fredrik.pettai@... wrote:

> 
> #
> # Summary: 16704 records, 1132 greylisted, 15572 whitelisted, XXX flushed
> #
> 
> Would it be useful to anyone else?

+1

-- 
Thomas Cameron, RHCE, CNE, MCSE, MCT
512-241-0774 (office)
512-924-8592 (cell)

<fredrik.pettai@...> wrote:

> # Summary: 16704 records, 1132 greylisted, 15572 whitelisted, XXX flushed
> #
> 
> Would it be useful to anyone else?

How do you intend to reset this counter? Will it increase forever?

What about something like flushed 1533/hour

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

> How do you intend to reset this counter? Will it increase forever?

Yes, that was my first idea, to get a complete summary. 
But thats maybe not a great idea. However, i though that the counter could change to a format like "1,234*10^6" after passing the million barrier so the string showed whouldn't been like 12345678912345395235 flushed

And then zeroed out then milter-greylist is restarted (like the first enhancement that i suggested ("slow-relay-tagging").

> What about something like flushed 1533/hour

Then I would prefer flushed 12335/day (then the date changes on the machine, and logged into syslog then recalculated)

But perhaps that could be made customazible like the options greylist/timeout. That you could choose between seconds, minutes, hours and days... 
(So you could make it match your greylist/timeout interval)

For example

flushidx 1d / 2h / 30m etc.
(or whatever you want to call it...)

/P