OK, you're just taking me too literally. I was saying "us dummies" trying (unsuccessful) to be funny by jabbing myself in the gut.
On Sun, Nov 8, 2009 at 1:48 PM, Thomas Eckardt/eck <[email protected]> wrote: >>>>Let's make it more clear for us dummies out there. > > I will never do any think for dummies - just give the child an other name! > > Thomas > > > > > K Post <[email protected]> > 08.11.2009 19:34 > Bitte antworten an > ASSP development mailing list <[email protected]> > > > An > ASSP development mailing list <[email protected]> > Kopie > > Thema > Re: [Assp-test] Antwort: Re: fixes and changes in 2.0.1_RC0.5.16 > > > > > > >>>Let's make it more clear for us dummies out there. >>No - this is a professional version ! > > I can't tell if you're being serious or not, but how are we supposed > to have known, short of looking at the code, what that norm number > means? > > I don't mean to argue, just discuss. I'll write the code and provide > it here, if you don't want to use it, that's fine (always) - no hard > feelings. > > You seem to agree with me at least in part - if there's a problem with > the norm, you already give a great pointer like this: > > Corpus norm: 0.1074 > Corpus norm should be between 0.6 and 1.4 > > Recommendation: You need more spam messages in the corpus. > > I'm just saying that if it is 0.67 that we should have > corpus norm: 0.6700 (sightly ham heavy) > > You're already putting things in each and every rebuild log like: > > Nov-08-09 08:15:00 Do Not Collect Messages with RedListed address: Enabled > **Messages with RedListed addresses will be removed from the corpus!** > > I'm not sure why you'd feel that this 2 line reminder is needed in > every log, but a good reminder of what the corpus norm number means > (which is very important IMHO) isn't a good idea. > > > On Sun, Nov 8, 2009 at 1:21 PM, Thomas Eckardt/eck > <[email protected]> wrote: >>>Let's make it more clear for us dummies out there. >> >> No - this is a professional version ! >> >> Thomas >> >> >> >> >> K Post <[email protected]> >> 08.11.2009 16:16 >> Bitte antworten an >> ASSP development mailing list <[email protected]> >> >> >> An >> ASSP development mailing list <[email protected]> >> Kopie >> >> Thema >> Re: [Assp-test] fixes and changes in 2.0.1_RC0.5.16 >> >> >> >> >> >> >> First, holy cow! Thanks for all of those changes in 2.0.1 rc 0.5.16. >> >> 1) Whitelisting emails are now working. That's huge. >> >> 2) I found the issue with the embedded analyze info in the ham/spam >> reports. If "Spam and Ham Reports will trigger an additional Analyze >> Report (DoAdditionalAnalyze)" is set to send a report, doesn't matter >> to whom, then a report is generated AND in the ham/spam reply there's >> an analysis too. This is true in 0.5.16. >> >> Like this: >> >> Thank you for your not-spam report. >> Your report will help ASSP better detect spam messages in the future. >> >> >> Subject: The message subject >> Feature Matching: >> >> Whitelist: '[email protected]' >> >> Bayesian Analysis: >> Bad Words:Bad Prob Good >> Words:Good Prob >> >> Totals: >> >> >> Spam/Ham Probabilities: >> >> >> Spam Probability: >> probability 0.5000 >> >> >> If I set DoAdditionalAnalyze to none, then this report doesn't appear >> in the reply. I want a report to go to the sender and an analyze to >> me, but i don't want the analyze in the user reply. >> >> >> 3) On occasion, it appears that there are duplicate whitelist status >> lines like this: >> >> [email protected] is not on Whitelist >> [email protected] is not on Whitelist >> >> In this example original email that address was the to and reply-to. >> >> >> 4) While we're on this topic, I think it would be better if in the >> ham/spam report replies if we changed it so the original subject >> appears in parentethis. So instead of >> Spam Report Received Original Subject >> it would be >> Spam Report Received (Original Subject) >> >> It's just easier to read that way. "Spam Report Received" is what we >> have the subject configured as fyi. >> >> >> 5) Last, with Outlook 2007, with the report emails (and other emails >> from ASSP, like rebuild reports), I'm getting "Extra line breaks in >> this message were removed." In #3 above, those two whitelist report >> lines were actually on the same line. The message that we put for >> not-spam reports: >> >> Thank you for your not-spam report. >> Your report will help ASSP better detect spam messages in the future. >> >> which is on 2 lines in the editor (lines 2 and 3, with 1 being the >> subject), shows as one line. >> >> In the rebuild reports most lines start on their own line, but those >> that are supposed printed on 2 lines like >> Nov-08-09 08:15:00 Do Not Collect Messages with RedListed address: > Enabled >> **Messages with RedListed addresses will be removed from the corpus!** >> >> Which appears on 2 lines in the admin editor, but as >> >> Nov-08-09 08:15:00 Do Not Collect Messages with RedListed address: >> Enabled **Messages with RedListed addresses will be removed from the >> corpus!** >> >> in outlook 2007. >> >> >> (ok, one more thing, unrelated) in the rebuild log, it would be nice >> when printing the corpus norm, if we indicated that, 1 is perfect, >> less indicates that the corpus is ham heavy, more indicates that the >> corpus is spam heavy. between .6 and 1.4 is an acceptable range. How >> about doing something like: >> >> Nov-08-09 08:47:17 Corpus norm: 1.1248 (slightly spam heavy) >> Nov-08-09 08:47:17 Corpus norm: 0.9000 (slightly ham heavy) >> Nov-08-09 08:47:17 Corpus norm: 0.0548 (very ham heavy) - and >> print >> the existing warning >> Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and >> print >> the existing warning >> >> I may actually have the ham/spam ratio backwards, which emphasises my >> point. Let's make it more clear for us dummies out there. >> >> Thanks for keeping these revisions coming out so frequently and for >> implementing so many of my suggestions. ASSP just keeps getting >> better and better. >> >> > ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and > focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Assp-test mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/assp-test >> >> >> >> DISCLAIMER: >> ******************************************************* >> This email and any files transmitted with it may be confidential, > legally >> privileged and protected in law and are intended solely for the use of > the >> >> individual to whom it is addressed. >> This email was multiple times scanned for viruses. There should be no >> known virus in this email! >> ******************************************************* >> >> >> > ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day >> trial. Simplify your report design, integration and deployment - and > focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Assp-test mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/assp-test >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > DISCLAIMER: > ******************************************************* > This email and any files transmitted with it may be confidential, legally > privileged and protected in law and are intended solely for the use of the > > individual to whom it is addressed. > This email was multiple times scanned for viruses. There should be no > known virus in this email! > ******************************************************* > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
