Also, 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 <[email protected]> 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: '[email protected]' > > Bayesian Analysis: > Bad Words:Bad Prob Good Words:Good Prob > > Totals: > > > Spam/Ham Probabilities: > > > Spam Probability: > probability 0.5000 > > > If I set DoAdditionalAnalyze to none, then this report doesn't appear > in the reply. I want a report to go to the sender and an analyze to > me, but i don't want the analyze in the user reply. > > > 3) On occasion, it appears that there are duplicate whitelist status > lines like this: > > [email protected] is not on Whitelist > [email protected] is not on Whitelist > > In this example original email that address was the to and reply-to. > > > 4) While we're on this topic, I think it would be better if in the > ham/spam report replies if we changed it so the original subject > appears in parentethis. So instead of > Spam Report Received Original Subject > it would be > Spam Report Received (Original Subject) > > It's just easier to read that way. "Spam Report Received" is what we > have the subject configured as fyi. > > > 5) Last, with Outlook 2007, with the report emails (and other emails > from ASSP, like rebuild reports), I'm getting "Extra line breaks in > this message were removed." In #3 above, those two whitelist report > lines were actually on the same line. The message that we put for > not-spam reports: > > Thank you for your not-spam report. > Your report will help ASSP better detect spam messages in the future. > > which is on 2 lines in the editor (lines 2 and 3, with 1 being the > subject), shows as one line. > > In the rebuild reports most lines start on their own line, but those > that are supposed printed on 2 lines like > Nov-08-09 08:15:00 Do Not Collect Messages with RedListed address: Enabled > **Messages with RedListed addresses will be removed from the corpus!** > > Which appears on 2 lines in the admin editor, but as > > Nov-08-09 08:15:00 Do Not Collect Messages with RedListed address: > Enabled **Messages with RedListed addresses will be removed from the > corpus!** > > in outlook 2007. > > > (ok, one more thing, unrelated) in the rebuild log, it would be nice > when printing the corpus norm, if we indicated that, 1 is perfect, > less indicates that the corpus is ham heavy, more indicates that the > corpus is spam heavy. between .6 and 1.4 is an acceptable range. How > about doing something like: > > Nov-08-09 08:47:17 Corpus norm: 1.1248 (slightly spam heavy) > Nov-08-09 08:47:17 Corpus norm: 0.9000 (slightly ham heavy) > Nov-08-09 08:47:17 Corpus norm: 0.0548 (very ham heavy) - and print > the existing warning > Nov-08-09 08:47:17 Corpus norm: 1.9548 (very spam heavy) - and print > the existing warning > > I may actually have the ham/spam ratio backwards, which emphasises my > point. Let's make it more clear for us dummies out there. > > Thanks for keeping these revisions coming out so frequently and for > implementing so many of my suggestions. ASSP just keeps getting > better and better. > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
