Re: BayesFilter 201: Much more aggressive?

2005-01-10 Thread Foster, Graham
Hello Fabio SR Nope, not here, no false positives here since installing it. ven, gen 07 2005, 00:02:10, DNS-BLACKLISTED, Message-ID: [EMAIL PROTECTED], From: Sean Rima [EMAIL PROTECTED], Subject: Re: BayesFilter 201: Much more aggressive?, Score: 100, Reason: cached DNS request Mon, Jan 10

Re: BayesFilter 201: Much more aggressive?

2005-01-10 Thread Dierk Haasis
Hello Graham! On Monday, January 10, 2005 at 10:20:11 AM you wrote: Dierk Ethan seem to have a problem about being blacklisted too :-( It's not us or our domains specifically. After reading up on it I guess it is pure coincidence if anyone - in this case me and Ethan - get filtered; looks

Re: BayesFilter 201: Much more aggressive?

2005-01-10 Thread Foster, Graham
Hello Dierk To relieve oneself from too much false positives is to increase the number of hits for classifying as spam from the default 2; I use 8 since 4 was still too low. As the default install only comes with 8 blacklist sites, and the message in the UI says is DNS count ABOVE n, then by

Re: BayesFilter 201: Much more aggressive?

2005-01-10 Thread Dierk Haasis
Hello Graham! On Monday, January 10, 2005 at 11:12:46 AM you wrote: As the default install only comes with 8 blacklist sites, and the message in the UI says is DNS count ABOVE n, then by increasing it to 8 are you really just disabling the blacklisting? (or have you added more sites?) Got

Re: BayesFilter 201: Much more aggressive?

2005-01-10 Thread Hendrik Oesterlin
Dierk Haasis wrotes on 10/01/2005 at 21:25:30 +1100 subject BayesFilter 201: Much more aggressive? : Hello Graham! On Monday, January 10, 2005 at 11:12:46 AM you wrote: As the default install only comes with 8 blacklist sites, and the message in the UI says is DNS count ABOVE n

BayesFilter 201: Much more aggressive?

2005-01-08 Thread Achim Winkler
if someone has problems with false sorted mails please send me the part of the logfile so that i can see what happens, so that i can fix the possible problems. achim Current beta is 3.0.2.10 | 'Using TBBETA' information:

Re[2]: BayesFilter 201: Much more aggressive?

2005-01-07 Thread Fabio Cipparone
SR Nope, not here, no false positives here since installing it. ven, gen 07 2005, 00:02:10, DNS-BLACKLISTED, Message-ID: [EMAIL PROTECTED], From: Sean Rima [EMAIL PROTECTED], Subject: Re: BayesFilter 201: Much more aggressive?, Score: 100, Reason: cached DNS request -- Fabio

Re[2]: BayesFilter 201: Much more aggressive?

2005-01-07 Thread Fabio Cipparone
SR Nope, not here, no false positives here since installing it. you may not believe this but your message was my first false positive. -- Fabio Current beta is 3.0.2.10 | 'Using TBBETA' information:

Re: BayesFilter 201: Much more aggressive?

2005-01-07 Thread Nick Danger
Reply to message sent 1/6/2005, @ 09:17:45 (2:17 AM Locally) ~~~ Hello Dierk, Anybody seen something similar? Yep. After I installed the update I noticed no mail had come in. I check the junk filter and everything that had arrived

Re[3]: BayesFilter 201: Much more aggressive?

2005-01-07 Thread Sean Rima
Hello Fabio, Friday, January 7, 2005, 10:36:42 AM, you wrote: SR Nope, not here, no false positives here since installing it. you may not believe this but your message was my first false positive. LOL, must be my sig :) Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: [EMAIL PROTECTED] AIM:

BayesFilter 201: Much more aggressive?

2005-01-06 Thread Dierk Haasis
Hello TBBETA Members! Yesterday I installed Achim's bug-fixed BF 2.0.1. Before that I very, very rarely had a false positive (by 2.0 and predecessors), all in all I can only remember four instances and they were easily explainable. This morning I polled my mail and four out of six

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Tim Casten
Hello Dierk, Thursday, January 6, 2005, 3:17:45 AM, you wrote: Yesterday I installed Achim's bug-fixed BF 2.0.1. Before that I very, very rarely had a false positive (by 2.0 and predecessors), all in all I can only remember four instances and they were easily explainable. This

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Peter Fjelsten
Dierk, On 06-01-2005 09:17, you [DH] wrote in mid:[EMAIL PROTECTED]: DH Yesterday I installed Achim's bug-fixed BF 2.0.1. Before that I DH very, very rarely had a false positive (by 2.0 and predecessors), DH all in all I can only remember four instances and they were easily DH

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Hendrik Oesterlin
Dierk Haasis wrotes on 06/01/2005 at 19:17:45 +1100 subject BayesFilter 201: Much more aggressive? : This morning I polled my mail and four out of six messages from this list were suddenly deemed Junk. I didn't change any of my settings. Anybody seen something similar? no false

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Dierk Haasis
Hello Hendrik! On Thursday, January 6, 2005 at 1:59:10 PM you wrote: no false positives here. Please look in the Bayesfilter-logfile if it was the Bayesian or the Regex method that caused your false positives! I went through the log with a machete to extract the significant entries; here are

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Peter Fjelsten
Dierk, On 06-01-2005 14:26, you [DH] wrote in mid:[EMAIL PROTECTED]: Ursache: gespeicherte DNS-Anfrage DNSBL. Ursache: dnsbl.sorbs.net list.dsbl.org And again. Ursache: gespeicherte DNS-Anfrage And again. So it is due to the fact that DNSBL finally works. DH Curiously my own message was

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Dierk Haasis
Hello Peter! On Thursday, January 6, 2005 at 2:36:58 PM you wrote: I does not look like you are on lists (to any greater extent). Hm, as far as I can interpret the results, I'd say it was pure coincidence that my own message got filtered/blacklisted. Shouldn't be; I just notched up the number

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Achim Winkler
hello, please check the logfile which filter catched the false sorted mails. if it was the dns blacklist filter, try to increase the default value for dns filtering. if it was the regular expression filter try to increase the threshold value. alternative you can disable one of them or both!!!

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Dierk Haasis
Hello Achim! On Thursday, January 6, 2005 at 8:02:33 PM you wrote: please check the logfile which filter catched the false sorted mails. if it was the dns blacklist filter, try to increase the default value for dns filtering. At least the messages I found the lines in the log for showed DNS

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Sean Rima
Hello Dierk, Thursday, January 6, 2005, 8:17:45 AM, you wrote: Hello TBBETA Members! Yesterday I installed Achim's bug-fixed BF 2.0.1. Before that I very, very rarely had a false positive (by 2.0 and predecessors), all in all I can only remember four instances and they were easily

Re: BayesFilter 201: Much more aggressive?

2005-01-06 Thread Krzysztof KudĀ³acik
2005-01-06|09:17 you wrote: This morning I polled my mail and four out of six messages from this list were suddenly deemed Junk. I didn't change any of my settings. Anybody seen something similar? Not here - on contrary: my plug-in seems to be overtained: ver 2.0 and 2.0.1 seems to be more