View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001520 | unreal | documentation | public | 2004-02-06 13:06 | 2004-02-06 21:52 |
| Reporter | AngryWolf | Assigned To | |||
| Priority | normal | Severity | text | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta19 | ||||
| Summary | 0001520: Confusing examples for /spamfilter | ||||
| Description | In the examples describing how to use /spamfilter in help.conf and other documentations, I find too confusing and purposeless to prepend and append stars to the expressions given in the "regex" parameter. Actually none of them are badword expressions, since they contain spaces or any other characters with ascii codes not between 65 and 123. Would you mind correcting that? Also, could you replace "regex" with something more appropriate in the syntax of /spamfilter to make people see fast badword matching is supported? In my opinion "regex" isn't enough, because not everyone reads the description of all parameters, particularly if they can guess at the first sight what they are used for. Thanks in advance. | ||||
| 3rd party modules | |||||
|
|
I've NFI where you are making a fuss off.. In fact I disagree with most what you said here, it's called 'regex' because it's MENT to be a regex, it supports the few simple fastbadwords stuff too.. so what? The "it's confusing blabla" stuff is also a totally weird invalid point, what is more logical than blocking "*Hi I ate a hamburger*"? Remember that spamfilter isn't +G.. for example it does not (and will not) support replacing of words, so it's ment to match on whole sentences... when thinking of it, perhaps the whole fastbadwords (or actually fastspamfilter) stuff will be ripped out since TRE has been integrated now [sooner than expected]. Anyway, feel free to come up with some good and easy examples of practical regex use (like the latest worms/bots/adsbla). |
|
|
I think I'll do just that (rip it out), and replace the examples with valid regex... but really, it is ment to be regex and not like the confusing stuff with +G :). |
|
|
I apologize if I look fussy, probably I used too strong words, sorry. I just wanted to be clear. If you disagree with the things I said, it's okay. If the "regex" parameter meant to be a regex, that's OK. And as I currently don't see any purposes to use FBRS in it, I agree in removing its support, then it's no longer a documentation issue. I neither talked about +G, nor about replacing of words, and you probably know that fast badword matching might use useful in other features too. When I posted this bugreport I thought antispam is one of those. Unfortunately I'm not familiar with the latest viruses and spam texts, but I would help if I could. It's not an easy issue, as noone can be sure "Come watch me on my webcam and chat" and every other spam-like messages really come from a spammer. :-) A wrongly chosen expression can cause more trouble than gains. But yeah, exact spam messages are most of the time good examples... Sorry, I'm not the person who can help in that. |
|
|
np... I'm already in the process of ripping out support and updating docs now. |
|
|
Done in .2081. I'll now have a look at a "spamfilter blabla matched bla" notify snomask. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-02-06 13:06 | AngryWolf | New Issue | |
| 2004-02-06 18:04 | syzop | Note Added: 0004890 | |
| 2004-02-06 19:58 | syzop | Note Added: 0004891 | |
| 2004-02-06 20:30 | AngryWolf | Note Added: 0004893 | |
| 2004-02-06 21:14 | syzop | Note Added: 0004895 | |
| 2004-02-06 21:52 | syzop | Status | new => closed |
| 2004-02-06 21:52 | syzop | Note Added: 0004897 |
