|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
|
|
fixes and changes in 2.0.1_RC0.5.16Hi all,
fixed: - filenames of reportfiles could be wrong - complete report section (show/add/remove) changed (adapted from V1 - maintent by Fritz) changed : 'GreedyWhitelistAdditions','How add Greedy Senders to Whitelist','0:none:1:envelope only|2:all senders', 'Defines what sender addresses are added to the whitelist if a message is considered to be from a whitelisted sender. NotGreedyWhitelist is considered in determining if a message is from a whitelisted sender.' MaillogTail - Loglines in separate <div> with separate scrollbar added: 'EmailErrorsModifyNoP','Combined Spam Report and NoProcessing Deletion','0:disabled|1:modify noprocessing|2:show noprocessing' 'If set to \'modify noProcessing\' Spam Reports will remove addresses from noProcessing list. If set to \'show noProcessing\' Spam Reports will show if addresses are on noProcessing list.','Basic' Fritz's webpage will be unmaintent for a week!!! The download is available at: http://assp.cvs.sourceforge.net/viewvc/*checkout*/assp/assp2/assp.pl Thomas 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: fixes and changes in 2.0.1_RC0.5.16First, 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: 'externaluser@...' 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: webmaster@... is not on Whitelist webmaster@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/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 ! Thomas K Post <nntp.post@...> 08.11.2009 16:16 Bitte antworten an ASSP development mailing list <assp-test@...> An ASSP development mailing list <assp-test@...> 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: 'externaluser@...' 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: webmaster@... is not on Whitelist webmaster@... 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 the existing warning Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and 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 Assp-test@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: fixes and changes in 2.0.1_RC0.5.16Also, could we get the Apply Changes and logout button that appears on
top of the left menu to be instead moved to the right of ASSP (as service) - Configuration (root) (right above the settings). This would let more of the left menu fit on the screen, which would be helpful for those of us doing admin work on low resolution laptops. Putting "manage users" at the bottom of the list, by show rebuild log, would also move everything up a line and help out. Once that's done, we could move Expand All, Collapse All, and sorted on the same line as "Main", maybe smaller font or using icons or shorthand instead (+ all, - all, sorted) and that would save even more space. Last, I clicked on "sorted" and found a small problem in IE at least.. The window flew out, but its left edge was not aligned with the left edge of the window, instead it was just to the right of the ASSP logo. Clicking on the menu on "Sorted config" (the vertical lettering) to remove the menu, has it fly to the left, but not all the way off the screen. Its right edge is just to the left of the P in the assp logo. i had to reload the admin page for it to be totally gone. no biggie here, I don't know that i've ever used that function before. On Sun, Nov 8, 2009 at 10:15 AM, K Post <nntp.post@...> wrote: > 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: 'externaluser@...' > > 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: > > webmaster@... is not on Whitelist > webmaster@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: 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 <Thomas.Eckardt@...> wrote: >>Let's make it more clear for us dummies out there. > > No - this is a professional version ! > > Thomas > > > > > K Post <nntp.post@...> > 08.11.2009 16:16 > Bitte antworten an > ASSP development mailing list <assp-test@...> > > > An > ASSP development mailing list <assp-test@...> > 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: 'externaluser@...' > > 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: > > webmaster@... is not on Whitelist > webmaster@... 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 > the existing warning > Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and > 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 > Assp-test@... > 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 > Assp-test@... > 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Antwort: Re: fixes and changes in 2.0.1_RC0.5.16>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. Set 'DoAdditionalAnalyze ' to 'SEND TO EmailAnalyzeTo' Thomas K Post <nntp.post@...> 08.11.2009 16:16 Bitte antworten an ASSP development mailing list <assp-test@...> An ASSP development mailing list <assp-test@...> 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: 'externaluser@...' 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: webmaster@... is not on Whitelist webmaster@... 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 the existing warning Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and 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 Assp-test@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16>>>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 <nntp.post@...> 08.11.2009 19:34 Bitte antworten an ASSP development mailing list <assp-test@...> An ASSP development mailing list <assp-test@...> 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 <Thomas.Eckardt@...> wrote: >>Let's make it more clear for us dummies out there. > > No - this is a professional version ! > > Thomas > > > > > K Post <nntp.post@...> > 08.11.2009 16:16 > Bitte antworten an > ASSP development mailing list <assp-test@...> > > > An > ASSP development mailing list <assp-test@...> > 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: 'externaluser@...' > > 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: > > webmaster@... is not on Whitelist > webmaster@... 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: > **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 > the existing warning > Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and > 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 > Assp-test@... > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > DISCLAIMER: > ******************************************************* > This email and any files transmitted with it may be confidential, > 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 > Assp-test@... > 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 Assp-test@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16OK, 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 <Thomas.Eckardt@...> 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 <nntp.post@...> > 08.11.2009 19:34 > Bitte antworten an > ASSP development mailing list <assp-test@...> > > > An > ASSP development mailing list <assp-test@...> > 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 > <Thomas.Eckardt@...> wrote: >>>Let's make it more clear for us dummies out there. >> >> No - this is a professional version ! >> >> Thomas >> >> >> >> >> K Post <nntp.post@...> >> 08.11.2009 16:16 >> Bitte antworten an >> ASSP development mailing list <assp-test@...> >> >> >> An >> ASSP development mailing list <assp-test@...> >> 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: 'externaluser@...' >> >> 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: >> >> webmaster@... is not on Whitelist >> webmaster@... 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 >> the existing warning >> Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and >> 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 >> Assp-test@... >> 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 >> Assp-test@... >> 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 > Assp-test@... > 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 > Assp-test@... > 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Antwort: Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16Just send me the code changes.
Thomas K Post <nntp.post@...> 08.11.2009 20:17 Bitte antworten an ASSP development mailing list <assp-test@...> An ASSP development mailing list <assp-test@...> Kopie Thema Re: [Assp-test] Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16 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 <Thomas.Eckardt@...> 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 <nntp.post@...> > 08.11.2009 19:34 > Bitte antworten an > ASSP development mailing list <assp-test@...> > > > An > ASSP development mailing list <assp-test@...> > 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: > **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 > <Thomas.Eckardt@...> wrote: >>>Let's make it more clear for us dummies out there. >> >> No - this is a professional version ! >> >> Thomas >> >> >> >> >> K Post <nntp.post@...> >> 08.11.2009 16:16 >> Bitte antworten an >> ASSP development mailing list <assp-test@...> >> >> >> An >> ASSP development mailing list <assp-test@...> >> 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: 'externaluser@...' >> >> 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: >> >> webmaster@... is not on Whitelist >> webmaster@... 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 >> the existing warning >> Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - >> 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 >> Assp-test@... >> 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 >> Assp-test@... >> 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 > Assp-test@... > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > DISCLAIMER: > ******************************************************* > This email and any files transmitted with it may be confidential, > 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 > Assp-test@... > 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 Assp-test@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16>>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. > > Set 'DoAdditionalAnalyze ' to 'SEND TO EmailAnalyzeTo' Right. That's how I have it. I get the analyze report just fine. BUT the sender also gets analysis, not as a separate email like I get (and want), but right int he body of the report reply. The only way I seem to be able to stop the analysis from appearing in the reply is to set DoAdditionalAnalyze to no additional report. ------------------------------------------------------------------------------ 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16OK - now I know what you meen. AnalyseText sets $this->{report} and we use
this to send the analyse report - but it is not reset to empty after that. Will change it. Thomas K Post <nntp.post@...> 08.11.2009 20:26 Bitte antworten an ASSP development mailing list <assp-test@...> An ASSP development mailing list <assp-test@...> Kopie Thema Re: [Assp-test] Antwort: Re: fixes and changes in 2.0.1_RC0.5.16 >>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. > > Set 'DoAdditionalAnalyze ' to 'SEND TO EmailAnalyzeTo' Right. That's how I have it. I get the analyze report just fine. BUT the sender also gets analysis, not as a separate email like I get (and want), but right int he body of the report reply. The only way I seem to be able to stop the analysis from appearing in the reply is to set DoAdditionalAnalyze to no additional report. ------------------------------------------------------------------------------ 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 Assp-test@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16On Sun, Nov 8, 2009 at 2:38 PM, Thomas Eckardt/eck
<Thomas.Eckardt@...> wrote: > OK - now I know what you meen. AnalyseText sets $this->{report} and we use > this to send the analyse report - but it is not reset to empty after that. > > Will change it. > Thanks. Obviously, not urgent. Nor is this requested addition or something like it- else { #norm exists, print it my $normdesc = ''; if ( $norm < 0.6 ) { $normdesc = '(warning: extremely ham heavy)'; } elsif ( $norm < 0.9 ) { $normdesc = '(ok - slighly ham heavy)'; } elsif ( $norm < 1.1 ) { $normdesc = '(very good - balanced)'; } <-- I'm guessing between .9 and 1.1 is very good elsif ( $norm < 1.4 ) { $normdesc = '(ok - slighly spam heavy)'; } else { $normdesc = '(warning: extremely spam heavy)'; } &rb_printlog( "Corpus norm:\t%.4f %s\n", $norm, $normdesc ); } I think I've got that last line right with the printf syntax, but if not, it's the normdesc variable that should be inserted after the norm for that little bit of extra explanation. ------------------------------------------------------------------------------ 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Antwort: Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16wrong syntax - does'nt matter -> done!
Thomas K Post <nntp.post@...> 08.11.2009 20:55 Bitte antworten an ASSP development mailing list <assp-test@...> An ASSP development mailing list <assp-test@...> Kopie Thema Re: [Assp-test] Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16 On Sun, Nov 8, 2009 at 2:38 PM, Thomas Eckardt/eck <Thomas.Eckardt@...> wrote: > OK - now I know what you meen. AnalyseText sets $this->{report} and we use > this to send the analyse report - but it is not reset to empty after that. > > Will change it. > Thanks. Obviously, not urgent. Nor is this requested addition or something like it- else { #norm exists, print it my $normdesc = ''; if ( $norm < 0.6 ) { $normdesc = '(warning: extremely ham heavy)'; } elsif ( $norm < 0.9 ) { $normdesc = '(ok - slighly ham heavy)'; } elsif ( $norm < 1.1 ) { $normdesc = '(very good - balanced)'; } <-- I'm guessing between .9 and 1.1 is very good elsif ( $norm < 1.4 ) { $normdesc = '(ok - slighly spam heavy)'; } else { $normdesc = '(warning: extremely spam heavy)'; } &rb_printlog( "Corpus norm:\t%.4f %s\n", $norm, $normdesc ); } I think I've got that last line right with the printf syntax, but if not, it's the normdesc variable that should be inserted after the norm for that little bit of extra explanation. ------------------------------------------------------------------------------ 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 Assp-test@... 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16Thanks!
On Sun, Nov 8, 2009 at 2:19 PM, Thomas Eckardt/eck <Thomas.Eckardt@...> wrote: > Just send me the code changes. > > Thomas > > > > > K Post <nntp.post@...> > 08.11.2009 20:17 > Bitte antworten an > ASSP development mailing list <assp-test@...> > > > An > ASSP development mailing list <assp-test@...> > Kopie > > Thema > Re: [Assp-test] Antwort: Re: Antwort: Re: fixes and changes in > 2.0.1_RC0.5.16 > > > > > > > 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 > <Thomas.Eckardt@...> 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 <nntp.post@...> >> 08.11.2009 19:34 >> Bitte antworten an >> ASSP development mailing list <assp-test@...> >> >> >> An >> ASSP development mailing list <assp-test@...> >> 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 >> <Thomas.Eckardt@...> wrote: >>>>Let's make it more clear for us dummies out there. >>> >>> No - this is a professional version ! >>> >>> Thomas >>> >>> >>> >>> >>> K Post <nntp.post@...> >>> 08.11.2009 16:16 >>> Bitte antworten an >>> ASSP development mailing list <assp-test@...> >>> >>> >>> An >>> ASSP development mailing list <assp-test@...> >>> 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: 'externaluser@...' >>> >>> 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: >>> >>> webmaster@... is not on Whitelist >>> webmaster@... 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 >>> the existing warning >>> Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - > and >>> 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 >>> Assp-test@... >>> 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 >>> Assp-test@... >>> 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 >> Assp-test@... >> 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 >> Assp-test@... >> 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 > Assp-test@... > 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 > Assp-test@... > 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16On Nov 8, 2009, at 10:21 AM, Thomas Eckardt/eck wrote:
>> Let's make it more clear for us dummies out there. > > No - this is a professional version ! Disagree, it can be professional, the goal of any software should be to be user friendly. The best software is professional software, whatever that means, but that empowers a new user to use the software as though they were a professional. There is no excuse for user facing complex software. ( complex under the hood, elegant on the surface ) At the very least, the more easy you make it on the user, the less questions you have on the mailing list. -- Scott * If you contact me off list replace talklists@ with scott@ * ------------------------------------------------------------------------------ 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16On Nov 8, 2009, at 11:54 AM, K Post wrote:
> On Sun, Nov 8, 2009 at 2:38 PM, Thomas Eckardt/eck > <Thomas.Eckardt@...> wrote: >> OK - now I know what you meen. AnalyseText sets $this->{report} and >> we use >> this to send the analyse report - but it is not reset to empty >> after that. >> >> Will change it. >> > > Thanks. Obviously, not urgent. Nor is this requested addition or > something like it- > > else { #norm exists, print it > > my $normdesc = ''; > if ( $norm < 0.6 ) { $normdesc = '(warning: extremely ham > heavy)'; } > elsif ( $norm < 0.9 ) { $normdesc = '(ok - slighly ham > heavy)'; } > elsif ( $norm < 1.1 ) { $normdesc = '(very good - > balanced)'; } <-- I'm guessing between .9 and 1.1 is very good > elsif ( $norm < 1.4 ) { $normdesc = '(ok - slighly spam > heavy)'; } > else { $normdesc = '(warning: extremely spam > heavy)'; } > &rb_printlog( "Corpus norm:\t%.4f %s\n", $norm, $normdesc ); > } > > > I think I've got that last line right with the printf syntax, but if > not, it's the normdesc variable that should be inserted after the norm > for that little bit of extra explanation. Nice. Not to nitpick, but how about an effort to be case consistent. warning: extremely ham heavy - instead use - Warning: Extremely ham heavy. And is it really a warning, or an alert? What does ASSP have as a standard for defining messages? I would take from Apache, from whom many others have taken, and is widely understood: emerg - System is unstable alert - Immediate action required crit - Critical error error - Non-critical error warn - Warning notice - Normal but significant info - Informational debug - Debug level These log levels and cosmetic lines in the display the user sees should be consistent across the board. So in my opinion, if I see your messages, I think something is very wrong on the warning side. All of those are simply "info" status. Does ASSP have a messaging class, msg($status, 'the message', optional- over-ride args) this may or may not send to the log, or screen, but it is controllable, and provides consistency to all messages. Probably a good idea to localize them with variable names as well. I am not sure I agree with putting the perens in the string in the code. If you want those, those should go into the warning class as well. It is just one more area for someone to miss putting them in, and we have log lines an screen messages that take on all different forms of syntax. Just food for thought. -- Scott * If you contact me off list replace talklists@ with scott@ * ------------------------------------------------------------------------------ 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: fixes and changes in 2.0.1_RC0.5.16ASSP development mailing list <assp-test@...>
schreibt: > >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. ------------------------------------------------------------------------------ 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
|
|
Re: Antwort: Re: Antwort: Re: fixes and changes in 2.0.1_RC0.5.16ASSP development mailing list <assp-test@...>
schreibt: > &rb_printlog( "Corpus norm:\t%.4f %s\n", $norm, $normdesc ); may be better: &rb_ printlog( "Corpus norm:\t%.4f %s $normdesc \n", $norm ); ------------------------------------------------------------------------------ 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 Assp-test@... https://lists.sourceforge.net/lists/listinfo/assp-test |
| Free embeddable forum powered by Nabble | Forum Help |