JunkMatcher 1.6.1

JunkMatcher filters spam using powerful regular expressions, IP query against multiple blacklists (such as SpamCop.net) and various other techniques such as email property matching, HTML final rendering matching, etc. You can match against almost every bit of a message (including attachment filenames and charsets), and the raw material for matching is cleaned out for you to defeat some of the tricks spammers use to obfuscate their messages.
JunkMatcher can be added to Mail.app as a rule so it can be used hand-in-hand with Mail.apps built-in (statistical) junk filter. Users can decide what actions to take on the matched messages (mark as junk/read/flagged/colored, move them to Junk/Trash mailbox etc.).
A self-contained GUI - JunkMatcher Central is also included so you can conduct "Email forensics": testing and building your regular expression patterns, browsing the log file of the past matchings, etc. You can even report spam to SpamCop.net directly from the log window. Many settings are also available in it so you can customize the entire matching process to your hearts content.
Enhancements:
- Bug fixed: Fixed an installation issue for users upgrading from 1.5.8 or earlier. If everything has worked for you, you dont need to upgrade to this version.
- There are many new features introduced in 1.6.0; make sure you read about them here
- Added SpamBayes "Happy Meal Plan" (automatic balanced training): If turned on (default, in the Test Inspector) SpamBayes will try to feed itself with yummy spam/ham in a balanced way - this happens even when SpamBayes property test is not turned on to make sure SpamBayes will learn from the results of the other tests. Due to this addition the SpamBayes property test is now turned on by default.
- Added the ability to correct JunkMatcher directly from Mail.app (save a trip to JunkMatcher.app): Just do what you usually do - click on the "junk bag" icon in Mail.apps toolbar, choose "Mark as Junk Mail" item in Mail.apps contextual menu, or move a message into/out of a Junk mailbox etc. Your action will be automatically reflected in the Log window of JunkMatcher.app.
- Added UI to set ham/spam cutoff values for SpamBayes (in the Test Inspector): Each cutoff value is a positive number between 0.0 and 1.0 (exclusive), and ham cutoff < spam cutoff. Any message with probability > spam cutoff (computed by SpamBayes of course) will be considered spam, and any message with probability < ham cutoff will be considered "definite" ham. The rest are classified as "unsure", but currently "unsure" is synonymous with "ham". :-)
- Added a new preference setting "Filter the test table if Match All finds positive(s)" (default is off). If you turn it on, after you apply a "Match All" in the Analyzer window, the search field will be automatically filled with string "test:matched" to filter the test table so you only see the positive tests. Clearing out the search field will show you the complete list of tests again.
- JunkMatcher now remembers which messages you have used for training, and will skip them if you try to retrain on them.
- Log entries are now color-coded in the "Received Date" column to indicate their training status; they will be automatically updated when you finish training.
- When doing a "Match All" in JunkMatcher.app with SpamBayes property test turned on, the "Last Match All" field in the Test Inspector window now shows the probability computed for the message even if the message is *ham*.
- Added a menu item under View: Inspect SpamBayes (cmd-opt-B). It will open the Test Inspector window on SpamBayes property test directly.
- Improved the speed of training processes.
- Improved stability when configuring JunkMatcher while matching is underway in Mail.app.
- Behavior changed: If you already have "JunkMatcher" rule in Mail.app, the installation process will not try to alter its settings (e.g., whether you want to color matched messages, what color you want, and whether you want to move the messages to Junk folder etc.).
- Bug fixed: MD5 keys of incoming emails were not computed in a consistent way.
- Bug fixed: When JunkMatcher.app is running, doing a "Match All" immediately after training sometimes did not use the latest training result.
- Bug fixed: When log is automatically recycled while JunkMatcher.app is running, making corrections to the subsequent log entries in the same session would cause errors.
- Bug fixed: Sometimes saving tests in JunkMatcher.app while Mail.app is running would produce a bunch of "A test is AWOL" error messages in the console.
- Many other GUI enhancements and dead bugs.
- JunkMatcher Howto website is again updated with much more information.