View Issue Details

IDProjectCategoryView StatusLast Update
0002578unrealircdpublic2007-04-27 05:15
Reporterferoz Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionwont fix 
Product Version3.2.3 
Summary0002578: Spamfilter expiry time
DescriptionThink it would be usefull to have an expiry time on spamfilters just like glines, so that they get deleted after a period of time..
We add some links to spamfilter that are no more alive or dont get spammed any more, it would be good if we could set an expiry date/time to those kind of spamfilter.
3rd party modules

Activities

codemastr

2005-07-02 12:18

reporter   ~0010156

Why can't you manually remove them? Setting an expire time is bad for your example anyway. So you set an expire time of 1 week. Well, in reality, it takes 2 weeks for that particular spam to stop, so now it gets through for 1 week. You should be removing it manually. The expire time is to "end a punishment" not to decide "this is no longer a threat." The latter requires a human decision, not a machine decision.

w00t

2005-07-03 02:33

reporter   ~0010158

You raise a valid point codemastr, but how does the human know when the threat is over given we don't see things happening all the time - especially on a quieter network.

Perhaps if there was some statistics being kept on how many things had been whacked by each spamfilter?

codemastr

2005-07-03 13:06

reporter   ~0010159

[quote]Perhaps if there was some statistics being kept on how many things had been whacked by each spamfilter?[/quote]
And how would this be useful? You'd have to keep track of how frequently it changes as well. For example, it might read 923892037 matches, but in the last 6 months, there have only been 2 matches. I personally think it is incredibly easy to tell whether matches are occurring... watch kill messages, tkl addition messages, etc.

aquanight

2005-07-03 13:40

reporter   ~0010160

Or /mode yournick +s +S and watch the actual Spamfilter catch messages :) .

w00t

2005-07-03 22:27

reporter   ~0010172

My point is that on small networks, that isn't going to work too well. You might be only getting say, one spamfilter hit a week TOTAL, it might only ever be hitting one definition.

As for the watching messages idea, also a good point - but remembering that opers aren't online 24/7, and even if you've got multiple opers - do you really think they're all going to be able to collate data on this kind of thing? :P.

I'm not too sure on this idea myself, just coming up with ideas ;).

codemastr

2005-07-04 13:22

reporter   ~0010175

[quote]As for the watching messages idea, also a good point - but remembering that opers aren't online 24/7, and even if you've got multiple opers - do you really think they're all going to be able to collate data on this kind of thing? :P.[/quote]
Then the proper solution is to add logging support, not to add some crazy semi-functional counter system.

w00t

2005-07-05 02:24

reporter   ~0010179

That's no problem - I'm just pointing out an issue, not necessarily a correct solution :p.

stskeeps

2007-04-27 05:15

reporter   ~0013810

Please resubmit for 3.3 if this is still an issue.

Issue History

Date Modified Username Field Change
2005-06-30 08:23 feroz New Issue
2005-07-02 12:18 codemastr Note Added: 0010156
2005-07-03 02:33 w00t Note Added: 0010158
2005-07-03 13:06 codemastr Note Added: 0010159
2005-07-03 13:40 aquanight Note Added: 0010160
2005-07-03 22:27 w00t Note Added: 0010172
2005-07-04 13:22 codemastr Note Added: 0010175
2005-07-05 02:24 w00t Note Added: 0010179
2007-04-27 05:15 stskeeps Status new => closed
2007-04-27 05:15 stskeeps Note Added: 0013810
2007-04-27 05:15 stskeeps Resolution open => wont fix