great On Mon, May 23, 2011 at 2:41 PM, Thomas Eckardt <[email protected]>wrote:
> >My bombMaxPenaltyVal is set to 70. With bombReMaxHits set to only 1, in > the > >gui analyze window, it still adds up all of the matches. > > - ignore 'bombReMaxHits' > - the analyzer shows more information than used by a real scan > > >>>>> how ever - these are still more information, than used by processing > a > >>>>> mail - there for example, the 'test3(20)' would never be reached > (found). > > > > > > Von: K Post <[email protected]> > An: ASSP development mailing list <[email protected]> > Datum: 23.05.2011 20:34 > Betreff: Re: [Assp-test] Antwort: Re: bombRe multiple matches > > > > bombLog is what I was looking for. Verbose definitely helps with testing > instead of just showing the highest. Thanks for pointing that out. > > My bombMaxPenaltyVal is set to 70. With bombReMaxHits set to only 1, in > the > gui analyze window, it still adds up all of the matches. > > > > On Mon, May 23, 2011 at 11:20 AM, Thomas Eckardt > <[email protected] > > wrote: > > > >bombReMaxHits > > > > If 'bombMaxPenaltyVal' is defined (!= 0) and reached while doing > regexes > > over the mail - assp stopps the current regex tests, because further > > checks will not increase the resulting penalty. > > > > >The result is: > > >bombRe : 'highest match: "Payment Department" with valence: 5 - PB > value > > = 10' > > >matching bombRe(file:files/bombre.txt[line 3]): 'UN Remittance , > Payment > > Department' > > > > setting 'bombLog' to verbose will give you some more informations - like > : > > > > - with the following text in the analyzer: > > > > text=test2 > > test8 > > test3 > > > > - and a testRe of: > > > > test2=>2 > > ... > > test8=>80 > > ... > > test3 > > ... > > > > you'll get the following result: > > > > testRe: 'highest match: "'test8 (80)' , 'test2 (40)' , 'test3 (20)'" > with > > valence: 80 - PB value = 70' > > matching testRe(file:files/testre.txt[line 2]): 'test2 , test8' > > > > > > were the first line shows all matches with the (PB-value), the resulting > > value (here it is the 80, because it is the highest) and the used value > > (here 'bombMaxPenaltyVal') - and the second line shows the used regexes > > (in order) to reach 'bombMaxPenaltyVal' or 'bombReMaxHits' > > The rule behind is simple - add all values until max is reached, but if > a > > single value is high enought use this one - because this is the major > > reason for blocking. > > > > Because the matched regexes are listed in line two, it should be simple > to > > find them in a file - an additionaly line (2) will be written for ever > > include file that contains a matching regex. > > > > how ever - these are still more information, than used by processing a > > mail - there for example, the 'test3(20)' would never be reached > (found). > > > > Thomas > > > > > > > > > > > > > > Von: K Post <[email protected]> > > An: ASSP development mailing list <[email protected]> > > Datum: 23.05.2011 15:47 > > Betreff: Re: [Assp-test] bombRe multiple matches > > > > > > > > > > Thanks Fritz, that's what I thought. > > > > Note, this doesn't work in an outdated 2.x version. > > > > When I did a mail analyze in the gui, it only showed the one score of 5 > > (valance is 50 * 0.10 = 5), instead of adding the 5's together. It also > > only showed one match. This was with bombReMaxHits set to 10. Same > > results > > with bombReMaxHits set to 1. > > > > HOWEVER, I just installed the 2.0.2(3.0.24) version in a test virtual > > machine. With bombReMaxHits set to ONE, now it does add the scores > > together > > (but that seems wrong since it's set to 1). > > > > Using the bombRe listed in my first post, I tested: > > text=UN Remittance Payment Department > > > > The result is: > > bombRe : 'highest match: "Payment Department" with valence: 5 - PB value > = > > 10' > > matching bombRe(file:files/bombre.txt[line 3]): 'UN Remittance , Payment > > Department' > > > > Thoughts and notes: > > 1) Changing bombReMaxHits to 10 in 2.0.2(3.0.24) has the exact same > > results > > (which are correct now) - I don't know if this is just a potential bug > > with > > the mail analyzer gui, or if bombReMaxHits doesn't have any effect in > > processing real mail, but it seems in the analyzer at least > bombReMaxHits > > set to 1 still scores everything. > > > > 2) In the analyzer, could it be changed to show what line number EACH > > match > > was found on? Maybe replace the current 2 line output with something > like > > this instead? > > > > match found in bombRe(file:files/bombre.txt): > > line 3: *UN Remittance* (valance 5) > > line 4: *Payment Department* (valance 5) > > Total PB value 10 > > > > if bombReMaxHits is set to a number lower than the total matches found, > > maybe put "**not scored" after lines that aren't due to having too many > > matches? > > > > That's just a little more descriptive IMO. > > > > Thanks. Hoping to update production to the new version soon. > > > > > > > > > > > > On Sun, May 22, 2011 at 11:50 PM, Fritz Borgstedt <[email protected]> wrote: > > > > > ASSP development mailing list <[email protected]> > > > schreibt: > > > >The mail analyzer is telling me that only the highest score is used. > > > >I seem > > > >to remember a trick to have these score from lines matching in bombRe > > > >be > > > >added together, > > > > > > The "trick" is to set : > > > Maximum Hits for Bombs in Header and Data (bombReMaxHits) > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > What Every C/C++ and Fortran developer Should Know! > > > Read this article and learn how Intel has extended the reach of its > > > next-generation tools to help Windows* and Linux* C/C++ and Fortran > > > developers boost performance applications - including clusters. > > > http://p.sf.net/sfu/intel-dev2devmay > > > _______________________________________________ > > > Assp-test mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > > > > > > > ------------------------------------------------------------------------------ > > What Every C/C++ and Fortran developer Should Know! > > Read this article and learn how Intel has extended the reach of its > > next-generation tools to help Windows* and Linux* C/C++ and Fortran > > developers boost performance applications - including clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > 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! > > ******************************************************* > > > > > > > > > > > > ------------------------------------------------------------------------------ > > What Every C/C++ and Fortran developer Should Know! > > Read this article and learn how Intel has extended the reach of its > > next-generation tools to help Windows* and Linux* C/C++ and Fortran > > developers boost performance applications - including clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > Assp-test mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > ------------------------------------------------------------------------------ > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > 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! > ******************************************************* > > > > > ------------------------------------------------------------------------------ > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
