1   Introduction

2   Installing and Updating

2.3   Installing SpamSieve

Double-click the SpamSieve-2.7.4.dmg file to mount the SpamSieve disk image. Then drag the SpamSieve application to your Applications folder. It is important that SpamSieve be installed directly in the Applications folder (not in another folder, or in a subfolder), because otherwise your mail program might not be able to find it.

Next, you must follow the instructions in the Using SpamSieve section in order to set up your mail program to use SpamSieve.

/Users/<username>/Library/Application Support/SpamSieve

/Users/<username>/Library/Preferences/com.c-command.SpamSieve.plist

3   Using SpamSieve

There are four basic steps to installing and using SpamSieve:

1. Put the SpamSieve application in your applications folder. This is described in the Installing SpamSieve section.
2. Set up your mail program to use SpamSieve to filter your mail. This is described in sections 3.1 through 3.7 (below) and in the Legacy Mail Programs section. Find the section below that corresponds to the mail program that you’re using.
3. Train SpamSieve with some examples of your spam and good messages, as described in the Do an Initial Training section. (This step is optional but highly recommended.)
4. SpamSieve will launch automatically when new mail arrives. It will examine each incoming message and move the spam messages to a separate mailbox. In order to keep SpamSieve’s accuracy high, you’ll need to tell it about any spam messages that you find in your inbox or good messages that you find in your spam mailbox. This is described in the Correct All Mistakes section.

You can return to this page at any time by going to SpamSieve’s Help menu, choosing SpamSieve Help, and clicking on Using SpamSieve in the table of contents. The Help menu also contains a PDF version of this manual.

The rest of this manual contains detailed information about how SpamSieve works and how it can be customized. If you have a question, it’s probably answered here. However, following the above four steps is all most users will need to do to effectively use SpamSieve.

4   iPhone Spam Filtering

Due to limitations of the iPhone platform, there is not currently an iPhone version of SpamSieve. However, you can use SpamSieve on your Mac to keep the spam off your iPhone or iPod touch. The Mac has much more bandwidth and processing power, so it makes sense to do the spam filtering there, anyway. When you check for mail on your iPhone, you won’t waste time or battery power downloading or processing spam messages.

To use SpamSieve with your iPhone, you’ll need to set both the Mac and the iPhone to connect to your mail server using the IMAP mail protocol. Most providers support both IMAP and the older POP protocol, but some only support POP. Apple’s MobileMe service automatically uses IMAP.

When using IMAP, all computers and iPhones that connect to the same mail account will share the same mailboxes, and they will be synchronized automatically. (The syncing happens when you open the Mail application, not when you connect the Mac and iPhone and sync in iTunes.) When your mail program is running on your Mac, it will periodically check for new mail. New messages will arrive in the inbox, and SpamSieve will move the spam messages to the spam mailbox. When the iPhone checks for new mail, the spam messages will generally already have been moved out of the inbox.

If the iPhone happens to see a new spam message before the Mac does, it will appear in the inbox for a short while. When the Mac sees it, it will move it to the spam mailbox and it will disappear from the inbox on the iPhone. The iPhone supports push e-mail, which lets it see new messages instantly. If you receive a lot of spam, you may prefer to turn off the push feature. That will give the Mac a chance to filter the messages before you see them on the iPhone.

The remainder of this section discusses how to setup Apple Mail to keep spam off your iPhone. A similar setup will also work with other mail programs that support IMAP.

1. Choose Preferences… from the Mail menu and click on Accounts. Your account(s) will be listed at the left of the window. If it already says IMAP or MobileMe under your account, there’s nothing more that you need to do.
2. If it says POP, you will need to disable the POP account and create a new IMAP one. Click on the POP account and make note of the contents of the Account Information tab. Click on the Advanced tab. Uncheck Include when automatically checking for new mail. Then click the Remove now button to remove from the server any messages that you’ve already downloaded.
3. Click the + button at the bottom of the window and follow the steps to create a new account. Choose IMAP for the account type. For the server and login, enter the information that you noted for the POP account. (Note: some providers use a different incoming mail server name for IMAP.) Put “IMAP” at the end of the description so that you can tell this account apart from the old one.
4. You should now be able to check for mail, and Mail will be using IMAP instead of POP. There will be two sets of mailboxes (Inbox, Sent, etc.) in the main window. If desired, you can go to each of these mailboxes and drag the messages from the old mailboxes to the IMAP ones.
5. Go back to Mail’s Preferences window, click on the POP account, and click the Advanced tab. Then uncheck Enable this account. You will be using the new IMAP account instead, although the old POP settings, and any messages that you didn’t transfer to the IMAP mailboxes, will still be available should you want to go back to the old setup.
6. Quit Mail and open iTunes. Click on your iPhone under Devices and then click the Info tab. Under Mail Accounts, make sure that Sync selected Mail accounts and your new IMAP account are checked. Then click the Sync button at the bottom of the window.

That’s all you need to do, but some more advanced configurations are also possible:

Remote Spam Mailbox

With the above setup, the Inbox, Sent mailbox, and any mailboxes that you create on the server are shared between the Mac and the iPhone. The spam messages are removed from the server and stored locally in the Spam mailbox on the Mac. This is faster, and it means that the spam messages won’t count towards your server quota.

Some users prefer to store the Spam mailbox on the server. This way, if SpamSieve accidentally puts a good message in the Spam mailbox, you can access the message on the iPhone when away from the Mac. To do this, choose Mailbox ‣ New Mailbox… to create new mailbox on the server called Spam. Open the Rules section of Mail’s preferences and change the SpamSieve rule to move the messages to this new mailbox instead of the old one. If you do find a good message in the Spam mailbox, do not use the iPhone to move it out of the Spam mailbox. Instead, when you get back to your Mac, select the message and choose SpamSieve - Train as Good.

Remote Training

If you’ll be away from your Mac for long periods of time, you can train SpamSieve directly from the iPhone. Correcting mistakes promptly will keep SpamSieve running at peak accuracy.

The Setting up a Spam Filtering Drone section describes how to setup Mail for remote training. To train SpamSieve, use the iPhone’s Mail application to move messages into either the AddToGood or AddToSpam mailbox.

5   Customization

5.7   Mailsmith Customization

Choose Show Other Scripts from SpamSieve’s SpamSieve menu. This reveals the Mailsmith Extras folder, which contains AppleScripts for use with Mailsmith. These make it possible for scripters to further customize and automate the labeling and marking of messages in Mailsmith. If you are using Mailsmith 2.0 and do not write your own AppleScripts, you can ignore the Mailsmith Extras folder.

You can add the AppleScripts to Mailsmith’s Scripts menu by copying them to the Scripts folder inside the Mailsmith Support folder. A filter such as the following may be used to change the labels of incoming spam messages.

This filter will pass all messages along to SpamSieve for analysis. It will set the Is Spam or Is Not Spam property of the message, and change the label of the message if it is spam. This is roughly equivalent to enabling SpamSieve in Mailsmith’s preferences, but because it uses AppleScript it is more customizable. Additionally, you can change the filter criteria to pass only select messages along to SpamSieve.

6   Menus

/Users/<username>/Library/Application Support/Eudora/PlugIns/

6.3   The Filter Menu

6.3.1   Show Corpus

The corpus is a collection of messages, both spam and good, with which you have trained SpamSieve. SpamSieve’s Bayesian classifier analyzes the contents of the messages and uses this information to predict whether future messages are spam or good. The contents of the corpus are managed by SpamSieve; therefore, once you’ve trained SpamSieve with a message, deleting the message from your e-mail program will not affect SpamSieve because the information from that message is stored in the corpus.

The Show Corpus command opens the Corpus window so that you can examine the words that SpamSieve has found in your e-mails. You can click on the name of a column to sort by that column. Click again on the column to reverse the sort direction. The meanings of the columns are as follows:

Word

A word in the corpus.

Spam

The number of times the word has occurred in spam messages.

Good

The number of times the word has occurred in good messages.

Total

The total number of times the word has occurred.

Prob.

The probability that a message is spam, given that it contains the word (and in the absence of other evidence).

Last Used

The date that the word was added to the corpus, or the date that it last appeared in a received message (whichever is later).

You can copy the selected rows to the clipboard or drag and drop them into another application.

With the window sorted by Word, you can type the first few letters of a word to locate that word in the corpus. Similarly, you can sort by one of the other columns and type a number to locate the first word whose value for the sorted column matches the number you typed.

You can edit the spam and good counts associated with a word by double-clicking on the number in the Spam or Good column. Changing the numbers for important words can greatly affect SpamSieve’s accuracy, so you shouldn’t make changes without good reason.

You can remove words that you don’t want in the corpus by selecting them and pressing Delete.

6.3.2   Reset Corpus…

This command removes all the words and messages from the corpus. (It does not change the whitelist or blocklist.) After resetting the corpus, you can retrain SpamSieve from scratch, and SpamSieve will let you use your old messages in the retraining. Resetting the corpus and re-training SpamSieve with a proper mix of recent messages can increase SpamSieve’s accuracy and reduce its memory use.

Before you reset the corpus, SpamSieve automatically saves a backup in case you need to go back to the old corpus. The backups are saved in this folder:

/Users/<username>/Library/Application Support/SpamSieve/

To restore from a backup, choose Import Corpus… from the File menu and choose the appropriate Corpus <date>.plist file.

6.3.3   Show Statistics

This command opens the Statistics window, which displays the following information:

Filtered Mail

Good Messages

The number of non-spam messages that SpamSieve has filtered.

Spam Messages

The number of spam messages that SpamSieve has filtered.

Spam Messages Per Day

The average number of spam messages received per 24-hour period.

SpamSieve Accuracy

False Positives

The number of good messages that SpamSieve identified as spam.

False Negatives

The number of spam messages that SpamSieve identified as good.

% Correct

The percent of messages that SpamSieve identified correctly.

Corpus

Good Messages

The number of non-spam messages that are used to identify spam messages.

Spam Messages

The number of spam messages that are used to identify spam messages.

Total Words

The total number of unique words in the corpus.

Rules

Blocklist Rules

The number of rules on SpamSieve’s blocklist.

Whitelist Rules

The number of rules on SpamSieve’s whitelist.

You can copy all the statistics to the clipboard using the Copy command in the Edit menu or by clicking the Copy Stats button.

Normally, SpamSieve shows statistics for all the messages that it processed since it was installed. Because the accuracy and the number of messages you receive change with time, you may wish to only see recent statistics. Click the Set Date… button at the bottom of the window to control which old statistics are hidden from view. You can edit the date and time shown in the sheet, or enter an entirely new date. SpamSieve will also accept dates specified in natural language, such as “last Sunday at dinner” or “today.” The Now button enters the current date and time.

If you’ve chosen a suitable date and the “Filtered Messages” section shows zero filtered messages, that means that your mail program did not ask SpamSieve to filter any incoming messages. You should check to make sure that the mail program setup is correct.

6.3.4   Open Log

SpamSieve keeps a log of messages that it has filtered, words that it has used to decide whether the messages were spam, messages you have added to the corpus, and any errors that have occurred. This command opens the log file so that you can look at it. Normally, there is no reason (aside from curiosity) to look at the log file. However, if you believe SpamSieve is not working as it should, the log file provides useful information about what SpamSieve has done.

1. For each incoming message, there should be an entry in SpamSieve’s log that says Predicted: Good or Predicted: Spam. If you see only Trained: entries (or no entries at all) for a message, then the mail program did not ask SpamSieve to analyze that message, and you should check the setup.
2. If SpamSieve left a spam message in your inbox, there will be a Predicted: Good entry for that message in the log. The Reason can provide clues for why SpamSieve thought the message was good.
   • If it says sender <address> in address book, you might want to remove that address from address book, add it to the Me card, or else uncheck SpamSieve’s option to Use Mac OS X Address Book.
   • If it says sender <address> in Entourage address book, you might want to remove that address from Entourage’s address book (then click Load while holding down the Option key) or uncheck SpamSieve’s option to Use Entourage address book.
   • If spam messages are being predicted as good and you don’t understand why, please send in a report.
3. If SpamSieve moved a good message to the spam folder, there will be a Predicted: Spam entry for that message in the log. The Reason can provide clues for why SpamSieve thought the message was spam.

If you find that the log file is taking up too much disk space, you can delete it at any time. SpamSieve will then start a new log file as needed.

6.3.5   Edit Log

This command opens the log file in a text editor such as TextEdit or TextWrangler instead of Console. This makes it easier to read and search large log files. You can control which editor SpamSieve uses by choosing Get Info in the Finder on a .txt file, changing the application in the Open with pane, and pressing Change All.

6.3.6   Show Blocklist

This opens the Blocklist window. The blocklist consists of a list of rules. If a message matches one or more rules on the blocklist, SpamSieve will predict that it is spam. Each row in the blocklist window represents one rule.

The meanings of the columns are as follows:

Date

The date that the rule was added to the blocklist.

Header

The part of the message that will be matched against the rule.

Match Style

How the rule text will be matched against the text from the message’s header.

Text to match

The text that will be matched against the message’s header.

✓

If this is checked, the rule is enabled. Disabled rules do not block any messages, but they are useful because they prevent SpamSieve from re-learning a rule that you don’t want.

For example, say that you get forged spam messages from your own address. When you receive such a message, and tell SpamSieve that it’s spam, any rule on the whitelist with your address would be disabled. This will enable future such messages to be caught. If you later get a legitimate message from your own address and tell SpamSieve that it’s good, the whitelist rule will remain disabled. If you had previously deleted the rule instead of disabling it, telling SpamSieve that the message was good would create a new, enabled whitelist rule, which is probably not what you want.

Hits

The number of spam messages that the rule blocked, a rough measure of how effective it is.

When SpamSieve checks whether a message matches a rule, it compares the part of the message named by the Header column with the contents of the rule’s Text to Match column. The following are the message parts that may be used in the Header column:

From (address)

The e-mail address of the message’s sender.

From (name)

The name of the message’s sender.

To (any address)

The e-mail addresses of the primary recipients of the message. SpamSieve checks each recipient separately to see whether it matches the rule.

CC (any address)

The e-mail addresses of the carbon copy recipients of the message. SpamSieve checks each recipient separately to see whether it matches the rule.

Reply-To (address)

The address that you would be sending to if you replied to the message. This is often the same as the From address, but it could also be a mailing list or an alternate address for the sender. If the message does not specify a Reply-To, then the rule will not match.

Any Recipient

The To and CC addresses.

Any Address

The From, To, CC, Reply-To, and SendTo addresses.

List-ID

For mailing list messages, this hidden header indicates which mailing list the message was sent to.

List-Unsubscribe

For mailing list messages, this hidden header indicates how to unsubscribe from the mailing list. Some mailing list messages that do not have a List-ID header do have a List-Unsubscribe header.

Mailing-List

For mailing list messages, this hidden header indicates which mailing list the message was sent to. Some mailing list messages that do not have a List-ID header do have a Mailing-List header.

Received (any)

The Received headers contain information about the servers that relayed the message on its journey from the sender to the recipient.

Return-Path

This header contains information about where the message originated.

Subject

The subject of the message.

Body (any text part)

The contents of the message. Some messages contain more than one text part (for instance, plain text and HTML representations of the same message). The rule matches the message if any of the text parts matches the rule’s text.

Any Character Set

The character set often indicates the language of the message. Many spam messages are sent using Asian or Cyrillic character sets, and SpamSieve is pre-configured to block these. The IANA maintains a list of character sets.

Any Attachment Name

Many spam messages contain attachments whose names end with .pif or .scr. SpamSieve ships with some blocklist rules pre-configured to catch messages containing spammy attachments.

There are several different ways in which SpamSieve can compare the text in the message’s header to the rule’s text. In all cases, capitalization does not matter; lowercase letters are considered the same as their uppercase counterparts.

Is Equal to

The message matches the rule if its text is exactly the same as the rule’s text. This is the fastest style of matching. If you leave the text blank, the rule will match messages that have blank values for that header—for example when there is an empty Subject header. Sometimes, messages (especially spam ones) omit headers. To match an omitted header, enter <SpamSieve-Unknown-Subject>, <SpamSieve-Unknown-From>, <SpamSieve-Unknown-FromName>, or <SpamSieve-Unknown-To> depending on the header selected.

Contains

The message matches the rule if the message text contains the rule text.

Starts with

The message matches the rule if the message text begins with the rule text.

Ends with

The message matches the rule if the message text ends with the rule text. This is useful for matching domain names. For example, to match messages sent from Apple, you could create an Ends with rule with text @apple.com.

Matches Regex

This is like Contains, except that the rule text is treated as a Perl-compatible regular expression. Regular expressions are a powerful way of specifying patterns of text, for instance: e-mail addresses that contain numbers before the @ sign or subjects that are longer than 30 characters. For example, a Matches Regex rule with the text:

^.*(?<!^sales|^support)@domain\.com$

would match all messages where the match field ends with @domain.com but is not sales@domain.com or support@domain.com. This can be used to block messages sent to fake addresses. And this regex:

(?-i)^(Re: )?[A-Z]{2,8}, [ a-z0-9'?!]*$

matches a common pattern of spam message subjects.

If the regular expression entered in the Text to Match column is invalid, SpamSieve will color it in red, and it will not match any messages.

You can edit a rule’s Header or Match Style by clicking in the corresponding column and selecting from the pop-up menu. To edit a rule’s Text to Match, double-click the text.

Training SpamSieve with a spam message adds its sender to the blocklist. You can delete a rule from the blocklist by selecting it and pressing Delete. Generally, there is little reason to delete rules; if you don’t like what a rule is doing, you should instead uncheck the rule to prevent SpamSieve from re-learning it. Also, SpamSieve is optimized such that having lots of rules does not reduce performance.

You can copy the selected rules to the clipboard or drag and drop them into another application. You can type the first few letters of a rule’s Text to Match to quickly locate that rule, or use the search field in the toolbar to focus on a group of related rules.

6.3.7   Show Whitelist

The whitelist works the same way as the blocklist except that messages sent from addresses on the whitelist are never considered to be spam. The whitelist also has special support for mailing lists. If you train SpamSieve with a good message from a mailing list, it will add a rule to the whitelist that matches the message’s mailing list header (List-ID, List-Unsubscribe, or Mailing-List). Then SpamSieve will know that all messages from that mailing list are good, regardless of who sent them.

The whitelist is most commonly used for matching messages sent from particular addresses, domains, or mailing lists. You can also use the whitelist to create codewords. For instance, you could create a rule in the whitelist that matches subjects containing “eggplant” (or some other word unlikely to occur in regular mail). You can tell select people to put “eggplant” in the subject of messages that they send you, and then you can be assured that their messages will get through, even if the sender addresses are not in your address book or whitelist.

6.3.8   Add Rule

This command creates a new rule in either the whitelist or blocklist. This is useful if you want to add your own rules to the whitelist or blocklist, rather than having SpamSieve learn the rules when you train it with messages. For example, you could create a blocklist rule to catch spam messages with a particular subject, or a whitelist rule to always accept messages sent from a certain domain.

7   Preferences

7.1   Filters

SpamSieve uses a variety of filters to determine whether messages are spam or good. It consults the filters in the order listed in this window. When a filter decides that the message is good or spam, SpamSieve stops moving down the list. Thus, the order of the filters makes a difference. You can see from the order that if a message’s sender is on the whitelist, it will be marked as good even if the Bayesian classifier would have predicted it to be spam. Normally this is what you want; the point of a whitelist is that you can be sure that certain messages will never be marked as spam.

7.1.1   Check for message in corpus

SpamSieve learns as you train it, but training is not instant. Training SpamSieve with a message will not necessarily give it enough information to classify that message correctly based only on the words in the message. However, once you have added a message to the corpus, SpamSieve knows whether it is good or spam, even though it might not make the correct prediction based on word probabilities. This option causes SpamSieve to see if it knows whether a message is good or spam before trying to calculate its spam probability. If SpamSieve has seen the message before, it will always classify it correctly. You can disable this option if you want to see what SpamSieve would have predicted if it did not already know whether the message was good or spam.

7.1.2   Use Mac OS X Address Book

With this option enabled, SpamSieve will never predict a message to be spam if its sender’s e-mail address is in the system address book.

You can add addresses to the system address book using the Address Book application (located in the /Applications folder), or directly from an e-mail program that supports the system address book.

Mailsmith and PowerMail users should be sure to enable the option to use Apple’s Address Book. Entourage users may prefer to use their address book as a whitelist instead of Apple’s. This is described in the Setting up Entourage section.

If spam messages get through to your inbox because they are sent from addresses in your address book, you can either uncheck Use Mac OS X Address Book or see Exclude my addresses.

7.1.3   Exclude my addresses

Enable this option so that spam messages with your own return address are not marked as good. (Spammers sometimes forge the return address to be your own, in an attempt to get through spam filters.) Disable this option if you send yourself messages and want to make sure that they are never marked as spam. SpamSieve looks on the “Me” card in Apple’s Address Book to determine which addresses are yours. The easiest way to add your addresses to the “Me” card is to open your mail program and then use SpamSieve’s Update Address Book “Me” Card command.

You can also use this feature to catch spam messages sent from certain addresses in your address book. Normally, if you have Use Mac OS X Address Book checked, messages from addresses in your address book will never be classified as spam. This is generally what you want, but there may be one or two particular addresses that spammers keep forging. By using Exclude my addresses and adding those addresses to the “Me” card in Address Book, you can get SpamSieve to analyze the full contents of those messages to determine whether they are spam. SpamSieve will continue to use the other addresses in the address book as before, always classifying messages from them as good.

7.1.4   Use Entourage address book

This option and the Load button are not needed if you have Entourage 11.2.3 or later and have Synchronize contacts with Address Book and .Mac checked in Entourage’s preferences.

If you have an older version of Entourage or if you do not wish to sync your Entourage contacts with the Mac OS X address book, you should:

1. Go to Entourage’s Security preferences and make sure that Warn before allowing an external application to access the address book is unchecked. If there are no Security preferences in your version of Entourage, you can skip this step.
2. Open SpamSieve’s Preferences window. Make sure that Use Entourage address book is checked, and click the Load button. Then click on the SpamSieve icon in the Dock and choose Update Address Book “Me” Card from the SpamSieve menu (next to the Apple menu).

With this option enabled, SpamSieve will not predict a message to be spam if its sender’s e-mail address is in the Entourage address book. However, if you have Exclude my addresses checked, addresses on the Mac OS X address book’s “Me” card will not be checked against Entourage’s address book. This helps prevent forged spams from getting through.

When you start using SpamSieve, you should click the Load button to make SpamSieve read in the addresses in the Entourage address book. (This will cause SpamSieve to launch Entourage if it is not already open.) The addresses are loaded into SpamSieve’s memory and stored in its preferences file, but they are not displayed in the Whitelist window because they are not whitelist rules.

If you have multiple Entourage identities, you can load the addresses into SpamSieve in sequence. Click Load, then change to another identity and click Load again, etc.

Whenever you add addresses to the Entourage address book, you should go back to SpamSieve’s preferences and click Load so that SpamSieve learns about the new addresses. If you remove addresses from the Entourage address book, you should hold down the Option key when clicking Load; this tells SpamSieve to forget the old addresses before loading the new ones. Do not click Load while Entourage is downloading and filtering mail, as this may cause it to freeze.

7.1.5   Use SpamSieve whitelist

Enable this option so that messages that match (enabled) rules on the SpamSieve whitelist are never marked as spam.

7.1.6   Use SpamSieve blocklist

Enable this option so that messages that match (enabled) rules on the SpamSieve blocklist are always marked as spam.

7.1.7   Use Habeas Safelist

The Habeas Safelist is list of senders who agree to only send e-mail that meets Habeas’ stringent compliance requirements. With this option checked, SpamSieve will consider a message to be non-spam if finds the sending mail server’s IP address on the Habeas Safelist. This entails contacting Habeas’ server to lookup the address, but there is little performance penalty for doing this, since SpamSieve only contacts the server when the message contains Habeas headers:

X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.

or:

Accreditor: Habeas
X-Habeas-Report: Please report use of this mark in spam to <http://www.habeas.com/report/>

7.1.8   “ADV” messages are spam

This option causes SpamSieve to always mark messages as spam if they contain some variant of “ADV” at the start of the subject line. The “ADV” marker is used by some commercial bulk mailers.

7.1.9   Encoded HTML mail is spam

Many spammers encode the contents of their messages with base-64 so that filters cannot see the incriminating words they contain. SpamSieve can decode and look inside these messages. This option causes it to mark all such as spam, regardless of their contents, on the theory that legitimate senders do not try to obscure their messages. This does not affect messages encrypted with PGP.

7.1.10   Use Bayesian classifier

This enables SpamSieve’s main spam detector, which uses the corpus and word probabilities to identify spam messages.

7.2   Notification

All e-mail programs can notify you when you receive new messages, but some will also notify you even when all the new messages are spam. If your e-mail program is not savvy in this way, you can turn off its notification and let SpamSieve notify you only when there are new good messages.

7.2.1   Play sound

This makes SpamSieve play a sound when new good messages are received. To add a sound to the menu, copy the sound file to the Sounds folder in your Library folder. SpamSieve will also look for sounds that are built into your installed e-mail programs.

7.2.2   Bounce Dock icon

This makes SpamSieve bounce its Dock icon once when new good messages are received.

7.2.3   Keep bouncing

You might not be looking at the Dock icon when it first bounces, so this makes SpamSieve continue bouncing its Dock icon until you activate SpamSieve or your e-mail program.

7.2.4   Show number of new good messages in Dock

This option makes SpamSieve show the number of new good messages in its Dock icon. If there are no new good messages or if SpamSieve or the mail program is frontmost, SpamSieve will not show any number (rather than showing zero). Clicking the Dock icon, activating your e-mail program, or training SpamSieve with a message will reset the count.

The slider lets you control the size of the number in the Dock icon.

If you’re using DragThing 5.3 or later, SpamSieve can show the message count in its tile in DragThing’s process dock.

7.2.5   Flash PowerMate

If you have a Griffin PowerMate, this option will make it flash when new good messages arrive. The flashing will stop when you activate SpamSieve or your mail program.

To change the rate of the pulsing, open System Preferences and go to the PowerMate pane. Adjust the Rate slider in the Pulsing section of the window.

This feature is compatible with versions 1.6.4 and 2.1 of the PowerMate software.

7.2.6   A spam message is uncertain if

SpamSieve assigns each message a score between 0 and 100, and it considers messages with scores 50 or greater to be spam. The farther the score is away from the middle (50), the more confident SpamSieve is about whether the message is spam. Put another way, if you are trying to double-check SpamSieve’s work, you should focus your attention on the messages with scores closer to 50. If SpamSieve has made any mistakes, it is more likely to be with messages scored at 70 or 30 than with those scored at 95 or 5.

Spam messages that SpamSieve thought were good (false negatives) are generally easy for humans to spot. They tend to stick out amongst lots of good messages in the inbox.

Good messages that SpamSieve thought were spam (false positives) are harder to spot. They can be buried amongst piles of messages in the spam folder. To help you find these messages, SpamSieve can notify you about uncertain spam messages, i.e. the messages in the spam folder that you should focus your attention on.

The pop-up menu lets you control the range of scores that SpamSieve considers to be uncertain. For example, if you set it to 75 (the default), messages that SpamSieve thought were spam but which have scores below 75 will be considered uncertain.

• Growl will show a notification bubble for each uncertain message. For more information, see the Use Growl global notification system section.
• In Entourage, the uncertain messages will be categorized as Uncertain Junk instead of Junk and will appear in a different color. For more information, see the Spam Message Categories section.

By making it easier to spot uncertain messages, these mechanisms help you to efficiently verify whether SpamSieve has filtered your mail correctly.

Uncertain messages are considered to be spam, unless you tell SpamSieve otherwise; there is no need to train SpamSieve that they are spam.

7.2.7   Use Growl global notification system

Growl is a free, third-party package that can enhance SpamSieve’s notification abilities. Once you have downloaded and installed Growl, the next time SpamSieve is launched it will use Growl to notify you when new messages arrive. You can customize the notification style and enable/disable notifications using the Growl pane in System Preferences.

The following notifications are available:

Good Message Count

This notification mimics the red number in SpamSieve’s Dock icon. After a batch of good messages arrives, it tells you how many new messages there are and then fades away.

Good Messages (in Address Book)

This posts one notification for each good message that arrives (where the sender is in your address book), showing the message’s subject, the first few lines of its body, and (if possible) a picture of the sender.

Good Messages (Not in Address Book)

This posts one notification for each good message that arrives (where the sender is not in your address book), showing the message’s subject and the first few lines of its body.

Uncertain Spam

This notification helps you spot false positives by telling you when a message has arrived that SpamSieve thinks is spam, but that may actually be good. By watching these notifications, you can spot false positives without having to look through the entire contents of the spam folder in your mail program. Unlike the other notifications, Uncertain Spam notifications will persist until you click to dismiss them. For more information, see the A spam message is uncertain if preference.

If you are not using Growl, turn off this option in order to improve performance.

7.2.8   Include message bodies

Growl notifications always include the message’s subject and sender. This setting controls whether they also include the first few lines of the message’s body. Including the message body provides more context, which is particularly useful for Uncertain Spam notifications, but it also uses more screen space.

7.3   Training

7.3.1   Allow duplicates in corpus

If you allow duplicate messages in the corpus, training SpamSieve with the same message twice will increase the corpus counts for the words in that message. If you do not allow duplicate messages, the second and subsequent trainings with that message will have no effect. By default, duplicate messages are not allowed in the corpus. This is nice because it means that you do not have to remember which messages you have already trained SpamSieve with; accidentally training with the same message more than once will not skew the data that you are providing to SpamSieve. If you wish to intentionally skew the data, you can check one or both boxes to allow duplicates.

7.3.2   Auto-train with incoming mail

This option causes SpamSieve to automatically train itself with newly received messages based on their predicted categories. Thus, after the initial training you would only need to train SpamSieve to correct its mistakes. It would automatically learn from the other new messages, as needed, trying to keep a proper balance of good and spam messages in the corpus. As the corpus increases in size, the rate of auto-training will automatically decrease to prevent it from growing too large.

Most SpamSieve users should keep auto-training on at all times. Reasons that you might turn it off include:

Testing Purposes

If you’re trying to figure out why SpamSieve is processing a certain kind of message in a certain way, turning off auto-training reduces the interactions among SpamSieve’s components and makes it easier to see what’s happening.

Unable to Correct Mistakes

When auto-training is enabled, it is imperative that you correct SpamSieve when it makes a mistake; otherwise it will “learn” things that aren’t true and begin making predictions based on that incorrect information. If your mail program and filters are set up such that you cannot tell when SpamSieve has made a mistake (or if you can see the mistakes but sometimes forget to correct them), then you should not use auto-training.

Multiple Copies of SpamSieve

If you are using multiple copies of SpamSieve (on different Macs) to filter the same IMAP account, it’s hard to know which one(s) to correct when a mistake is made. With auto-training off, you don’t have to worry about that.

Bulk Processing

For example, if SpamSieve will be processing a large number of incoming messages in a row, and you will not be able to correct any mistakes until later. In this case, using auto-training could magnify one or two mistakes into many, as SpamSieve would assume that it had classified the earlier messages correctly, and learned from that (possibly incorrect) assumption.

Delayed Corrections

If it will be a long time between when SpamSieve filters some messages and when you can correct any mistakes, the situation is similar to Bulk Processing, so you may want to turn off auto-training.

7.3.3   Train SpamSieve whitelist

With this option enabled, training SpamSieve with a good message will add the message sender’s name and address to SpamSieve’s whitelist. Training SpamSieve with a spam message will disable the name and address if they appear in the whitelist.

Example: You receive an Amazon order receipt and train SpamSieve with it as a good message. This puts auto-confirm@amazon.com on the whitelist so that future order receipts are always marked as good. A spammer might decide that auto-confirm@amazon.com would make a good fake return address. If you receive such a spam, SpamSieve would mark it as good because the sender was on the whitelist. If you then tell SpamSieve that the message is spam, it will disable the whitelist rule so that it can catch future spam messages with that return address.

7.3.4   Train SpamSieve blocklist

With this option enabled, training SpamSieve with a spam message will add the message sender’s name and address to SpamSieve’s blocklist. Training SpamSieve with a good message will disable the sender’s name and address if they appear in the blocklist.

7.3.5   Train Bayesian classifier

With this option enabled, training SpamSieve with a message will add the words from that message to SpamSieve’s corpus. It is highly recommended that you train the Bayesian classifier, as it is what SpamSieve uses to catch most spam messages.

7.4   Advanced

7.4.1   Spam-catching Strategy

This slider lets you adjust SpamSieve’s bias. The bias controls how aggressive SpamSieve’s Bayesian classifier is at catching spam. When SpamSieve is more aggressive, it is better at catching spam messages that share some characteristics with your good mail. When SpamSieve is more conservative, it will be better at marking borderline messages such as order confirmations and press releases as good. This setting is very powerful, and most users should stick to the middle range. It is also not a substitute for training SpamSieve or making sure that it’s setup properly. Only change the bias if SpamSieve is consistently making errors in the same direction.

7.4.2   Save false negatives to disk

False negatives are spam messages that SpamSieve examined but didn’t think were spam. This option causes SpamSieve to save such messages for later analysis. Clicking the Show button opens the folder containing the saved messages. You can e-mail this folder, along with SpamSieve’s log file, to spamsieve-fn@c-command.com. By looking at the messages that SpamSieve missed, I can improve its algorithms to catch such messages in the future.

Note: Enabling this option will slow down SpamSieve’s processing.

Note: If the False Negatives folder is empty, even after enabling Save false negatives to disk and training SpamSieve with an uncaught spam message, there is probably a setup problem in your mail program. Use the Open Log command to see whether SpamSieve made a prediction for that message.

7.4.3   Use photo-realistic Dock icon

This option causes SpamSieve to use a more modern Dock icon, which may or may not fit in better with your other Dock icons.

7.4.4   Quit when mail client quits

With this checked, SpamSieve will quit itself when you quit an e-mail program, provided that there are no other mail programs running. This prevents SpamSieve’s icon from filling up your Dock when it’s not actually being used.

8   Frequently Asked Questions

8.3   What information should I include when I report a problem?

Make sure that your message says which versions of Mac OS X and SpamSieve you are using, as well as the name and version of your mail program.

Open the Console application (in the Utilities folder) and check the All Messages area for errors from your mail program or SpamSieve.

If the problem concerns SpamSieve’s training or its accuracy, please attach the log file:

/Users/<username>/Library/Logs/SpamSieve/SpamSieve Log.log

to your message. That is, the file is called SpamSieve Log.log, and it is located inside the SpamSieve folder in the Logs folder in the Library folder that’s in your home folder. (In most cases there’s no need to attach the old, dated log files, whose names end with .log.bz2.)

If you are reporting spam messages that SpamSieve didn’t catch, please do not forward the messages using your mail program. Instead, enable the Save false negatives to disk preference so that SpamSieve will save future such messages to the folder:

/Users/<username>/Library/Application Support/SpamSieve/False Negatives/

Then send the files in this folder to spamsieve-fn@c-command.com as an attachment. If, after enabling the preference, a spam message gets through and is not saved in the False Negatives folder, this likely means that there is a setup problem and SpamSieve was not given an opportunity to filter that message.

If the problem concerns SpamSieve’s setup and interaction with your mail program, please include relevant screenshots of the SpamSieve rule, the rules list, or the message list. To take a screenshot, hold down the Apple and Shift keys and press the number 4. Then use the mouse to select the area of the screen that you want to take a picture of. This will create a file called Picture 1 on your desktop. Pressing the keys again will create Picture 2, etc.

/Users/<username>/Library/Application Support/SpamSieve/

/Users/<username>/Library/Preferences/com.c-command.SpamSieve.plist

<key>LSUIElement</key>
<string>0</string>

<key>LSUIElement</key>
<string>1</string>

9   Legacy Mail Programs

The following mail programs are discontinued, but they can still be used with SpamSieve.

10   Legal Stuff

Distribution

Please distribute the unmodified SpamSieve-2.7.4.dmg file on the Web, LANs, compilation CD-ROMs, etc. You may not charge for it (beyond a reasonable cost for media) or distribute the contents of the disk image file in isolation. You may not distribute your serial number.

Limited Warranty

The software is provided “as is,” without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.

License

A license for SpamSieve is good for one person or one computer. You may install it on one Mac, and everyone sharing that Mac may use it (on that Mac). Alternatively, you may install it and use it on multiple Macs (e.g. your desktop Mac and your laptop); then you (and no one else) may use it on any of those Macs. For multiple users on multiple Macs, you should purchase multiple licenses.

Copyright and Trademarks

SpamSieve and this manual are copyright © 2002–2009 by C-Command Software. All rights reserved.

SpamSieve is a trademark of C-Command Software. Mac is a registered trademark of Apple Computer. All other products mentioned are trademarks of their respective owners.

Components

The following open-source components are used in SpamSieve:

• Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England.

• Core Foundation is available under the terms of the Apple Public Source License.

• Growl is Copyright © The Growl Project, 2004-2007 All rights reserved.

  Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. Neither the name of Growl nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

• Thanks to Allan Odgaard for some code snippets that are used in the Software Update installer.

• EDCommon is Copyright © 1999—2002 by Erik Doernenburg. All rights reserved. Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation, and that credit is given to Erik Doernenburg in all documents and publicity pertaining to direct or indirect use of this code or its derivatives.

• EDMessage is Copyright © 2000—2002 by Erik Doernenburg and Axel Katerbau. All rights reserved. Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation, and that credit is given to Erik Doernenburg in all documents and publicity pertaining to direct or indirect use of this code or its derivatives.

11   Version History

2.7.4—April 13, 2009

• Improved compatibility with pre-release versions of Mac OS X 10.6 (Snow Leopard).
• SpamSieve is better able to recover from corpus files that were damaged due to disk errors.
• Improved the Entourage installer’s error handling.
• Improved the error reporting when saving the corpus.
• Improved the troubleshooting instructions.
• Fixed a problem where messages trained as good in Apple Mail could be moved into the inbox of a disabled account.
• Fixed a bug that could cause harmless error messages to be logged to the Console when playing System 7 sound files.
• The crash reporter now warns before sending a report without an e-mail address.
• You can now press Enter to click the Send Report button in the crash reporter.

2.7.3—January 26, 2009

• Rewrote and restructured the manual to make the setup and troubleshooting instructions clearer.
• Replaced the Training Tip window with an alert that’s displayed when SpamSieve’s corpus is empty. This goes along with the more explicit guidance that ongoing training is only necessary to correct mistakes.
• The Entourage installer no longer asks before replacing existing script files. If you want to customize the scripts (rare these days, since there are so many built-in configuration options), you should use copies with different names to avoid having SpamSieve overwrite them.
• Changed the recommended Entourage rule setup to better handle uncertain messages. The installer now creates the Uncertain Junk category if necessary.
• Made the Apple Mail plug-in installer more robust.
• Worked around a problem parsing certain multipart messages.
• Adjusted the built-in blocklist rules for better accuracy.
• Reduced memory usage when processing message attachments.
• Fixed a bug sorting in rules windows.
• Fixed a bug marking incoming Entourage messages as Uncertain Junk.
• Updated the localizations.

2.7.2—October 29, 2008

• Made various accuracy improvements.
• Improved compatibility with pre-release versions of Mac OS X 10.6 (Snow Leopard). There are now two separate versions of SpamSieve’s Apple Mail plug-in. Version 1.3 is for Mac OS X 10.4; version 1.4 is for Mac OS X 10.5 and later. SpamSieve will auto-choose which one to install (or update) based on the version of Mac OS X that you’re running.
• Added new sections to the manual about Whitelisting Previous Recipients and iPhone Spam Filtering. Expanded the Auto-train with incoming mail section.
• Worked around a problem where the Edit Log command would try to open SpamSieve’s log using Script Editor if Launch Services was confused.
• Rewrote filesystem code to improve performance and error reporting.
• If there’s an error getting the downloads folder for a software update, SpamSieve now defaults to Downloads rather than Desktop.
• Worked around a problem where training (using Apple Mail on Mac OS X 10.5) could be interrupted.
• Added Korean localization.
• Moved .nib files that don’t need localization out of the English.lproj folder. This should make it easier to run SpamSieve in a language other than English without changing the default language on your Mac.
• Fixed some small memory leaks.
• Improved reporting of unexpected errors.
• Added placeholder text to the Purchase window.
• Added Help button to the Software Update window.

2.7.1—June 4, 2008

• Fixed a regression in version 2.7 where SpamSieve was slow loading certain large corpus files when running on Mac OS X 10.5.
• Worked around a bug in Mac OS X 10.4 that could cause a crash when training a message with Apple Mail.
• Made some minor accuracy improvements.

2.7—May 21, 2008

• Now requires Mac OS X 10.4 or later.
• Made a variety of accuracy improvements, focused on dealing with obfuscations, image attachments, URLs, and HTML.
• Improved corpus speed and memory use.
• Made various improvements to the column widths and alignments in the rules and corpus windows, and added alternating row colors.
• Fixed a rare problem where Apple Mail on Mac OS X 10.5 might hang if you trained a message as spam while Mail was downloading messages.
• If the OS reports an error when playing a sound as an alert sound, SpamSieve now plays it using the normal sound channel.
• Increased the range of possible values for the uncertain spam threshold.
• Improved sorting of sound names in the pop-up menu.
• Fixed bug where SpamSieve wouldn’t launch if the Microsoft User Data folder had been replaced by an alias file that was invalid.
• No longer shows the Reset Corpus/History alert at launch if you hold down other modifier keys in addition to Command-Option.
• Updated the Dutch localization.

2.6.6—January 23, 2008

• Made various accuracy improvements.
• Rewrote internal corpus storage to work around a performance bug in Mac OS X 10.5 that could, in some circumstances, make SpamSieve very slow to launch.
• Worked around a problem on Mac OS X 10.5 where the Apple Mail plug-in would sometimes try to launch multiple copies of SpamSieve (and then they’d all self-quit, leading to -609 errors).
• Made some internal changes so that Use Growl global notification system works more reliably on Mac OS X 10.5.
• The Flash PowerMate notification feature now works with version 2.1 of the PowerMate software.
• If SpamSieve’s corpus file or history database is damaged, you can now hold down the Command and Option keys at launch to reset them.
• Growl notifications are now posted from a background thread, to speed up message filtering.
• Fixed bug where the open panel for the Import Addresses… command was slow.
• Worked around a problem that could cause corruption of SpamSieve’s Entourage scripts.
• Fixed rare crash when processing HTML messages.
• If SpamSieve is unable to install its Apple Mail plug-in, it now does a better job of helping you complete the installation manually.
• Integration with Apple Mail and Entourage no longer relies on the mydefaults command-line tool, since it had some limitations and there were occasional problems installing it.
• The software updater is better at handling invalid downloads folders.
• Added Dutch localization and updated the other localizations.

2.6.5—November 14, 2007

• Now requires Mac OS X 10.3 or later.
• Made various accuracy improvements.
• Added high-resolution version of the application icon.
• Adjusted the appearance of the status indicators (•, G, S) for better visibility in the Leopard Dock.
• Updated the default whitelist rules.
• Updated documentation for Mac OS X 10.5.
• Updated to PCRE 7.4.
• Improved compatibility with pre-release versions of Entourage 2008.
• The Train as Good command in Apple Mail now recognizes spam mailboxes whose names end with “Spam”, and it works with the Trash mailbox on Mac OS X 10.5.
• Worked around change in Apple Mail on Mac OS X10.5 that could cause the Train as Spam command not to move the messages.
• Fixed bug where the Apple Help didn’t work on Mac OS X 10.5.
• Fixed hang processing some pathological HTML spams.
• Fixed bug where Growl notification preferences got reset if you ran SpamSieve under different localizations.
• Fixed unnecessary Console logging when loading Entourage addresses.
• Updated Italian localization.

2.6.4—August 20, 2007

• Made more accuracy improvements for messages with attachments.
• Fixed a bug that could cause crashes when processing messages containing PDF attachments.
• Updated localizations.

2.6.3—August 3, 2007

• Made various accuracy improvements, particularly for messages with attachments.
• Improved compatibility with pre-release versions of Mac OS X 10.5 Leopard.
• Fixed bug where the Software Update checker didn’t always re-check for new updates.
• Restored progress bar when loading Entourage addresses.
• Updated the localizations.
• Improved the documentation.
• Fixed help book icon.

2.6.2—May 4, 2007

• Made changes to prevent a crash on Mac OS X 10.4.9 when quitting in response to a mail program quitting.
• Slight changes for better accuracy.
• Fixed regression where the Import Addresses… command didn’t always work for text files in the default encoding.
• Blocklist and whitelist rules that use Body (any text part) can now match text from the headers of bounced messages (which e-mail clients often display as part of the message body).
• The Software Update feature now checks whether the updated version can run on your installed version of Mac OS X.
• Better logging of messages that don’t have a sender.
• Fixed a threading bug.
• Made an optimization to the Apple Mail plug-in.
• Adjusted the setup instructions for Apple Mail to avoid problem with the Previous Recipients list.
• Modernized the crash reporter code.
• Updated the French and German localizations.

2.6.1—April 9, 2007

• Fixed regression where SpamSieve wouldn’t launch if you had a large number of Mac OS 9 sound files.
• Fixed bug where Thunderbird messages that were manually marked as junk weren’t moved to the junk folder. If you are using Thunderbird, first update to SpamSieve 2.6.1, then choose Install Thunderbird Plug-In from the SpamSieve menu to update the plug-in.
• Made change prevent crash on Mac OS X 10.4.9 when quitting in response to a mail program quitting.

2.6—March 19, 2007

• SpamSieve now works with Mozilla Thunderbird.
• Improved detection of image spams and phishing messages.
• Made various message analysis improvements to increase the accuracy of the Bayesian filter.
• AppleScripting the whitelist and blocklist is much more efficient for scripts that access a lot of rules.
• Improved compatibility with pre-release versions of Mac OS X 10.5 Leopard.
• When installing a plug-in for a mail program, SpamSieve now opens the relevant page of the Apple Help to help you complete the installation.
• The alert when SpamSieve has auto-updated its Apple Mail plug-in is now non-modal, so it doesn’t interfere with spam filtering.
• The Software Update checker now works behind an HTTP proxy, and the auto-updater is now compatible with FileVault.
• Can now import addresses from the incorrectly encoded .vcf files that are generated by recent versions of Address Book.
• Growl notifications are now enabled by default.
• The Apple Mail plug-in is more robust.
• Fixed some small memory leaks.
• Made some performance optimizations to the message tokenizer.
• SpamSieve is more robust when processing incomplete messages.
• The Entourage “Train Good” command now moves messages out of the Uncertain Spam folder.
• The Apple Mail “Train as Good” command now moves messages out of zSpam mailboxes.
• Updated to PCRE 7.0.

2.5—October 30, 2006

• Made lots of changes to the parser and classifiers to improve accuracy, especially for HTML and image messages.
• The in-memory corpus representation is much more efficient, which should lead to lower memory use and greater speed.
• Rewrote the Software Update feature. When a new version is available, it can now show you the release notes. SpamSieve now downloads the new version itself, rather than relying on your browser. On 10.3 and later, the Download & Install button will cause SpamSieve to auto-update itself to the latest version.
• Improved accuracy on messages containing misspelled words.
• Now requires Mac OS X 10.2.8 or later.
• Auto-training now places a higher priority on corpus balance compared to learning from novel messages.
• Improved the Apple Mail plug-in’s Train as Good script to work around a bug in Mail.
• Improved the reliability of the Apple Mail training commands.
• Made further changes to improve the success rate of the Apple Mail plug-in installer.
• Updated to PCRE 6.7.
• Entourage training progress messages no longer block if Entourage is in the background.
• Worked around OS bug that prevented the Statistics sheet from properly parsing dates when the user’s date format started with a two-digit year.
• No longer quits with an internal error if the mydefaults tool can’t be installed.
• Added keyboard shortcut for Hide Others.
• Fixed bug with Purchase window sheet.
• Removed some old, unused code.
• Updated the toolbar icons.
• Various localization and documentation improvements.
• Fixed bug with display of remaining demo time.
• The Entourage script installer is more robust when contacting Entourage via AppleScript fails.
• Improved compatibility with Leopard.
• The date in the Statistics window more closely matches the user’s preferences (10.4 and later).
• Better at detecting damaged corpus files (instead of crashing).
• Fixed bug where Uncertain Spam growls were always sent, even if disabled in SpamSieve’s preferences.
• Adjusted workaround for Help Viewer bug.
• Increased the maximum width of the Hits column in rule list windows.
• Added thousands separators throughout the Statistics, Corpus, and rules windows.
• Fixed bug where adding a rule didn’t create a new rule if there was already a rule with a blank “Text to Match.”
• Fixed rare crashing bug when performing operations during idle time.
• Removed the Import Messages command (which let you train SpamSieve directly from a file in mbox format), because there are now very few situations where it is useful, and it was confusing people.
• Added screenshot showing where to find Entourage scripts.

2.4.4—July 13, 2006

• Made various changes to improve SpamSieve’s accuracy, particularly when processing blank messages, HTML messages, and messages containing images.
• The following strings may now be used in rules to match headers that are missing: <SpamSieve-Unknown-Subject>, <SpamSieve-Unknown-From>, <SpamSieve-Unknown-FromName>, <SpamSieve-Unknown-To>. It is somewhat common for messages to have a blank subject (which can be matched using the empty string), but legitimate messages that omit the Subject for From header are rare, and now these can easily be matched by creating the appropriate rules on the blocklist.
• Quit when mail client quits is now enabled by default.
• Log entries are now abbreviated when the string that matched the rule is long.
• The Apple Mail Train as Good command can now move messages out of submailboxes of the Junk mailbox.
• The Apple Mail plug-in installer works better when the folder permissions are messed up.
• Can now auto-recover from damaged message store files, rather than complaining to the user about them.
• If SpamSieve is hidden when launched, it will refrain from opening the Training Tip window.
• Improved the documentation, training tips, and localizations.
• Various code modernization and bullet-proofing throughout.
• Fixed localization bugs that could cause crashes.
• Fixed crash when hiding the progress panel.
• Fixed crash when saving false negatives to disk.
• Made changes to the Entourage scripts to try to work around an OS bug that causes them to grow and eventually become corrupted.
• Worked around OS bug to prevent freezes when attempting to play damaged sound files.

2.4.3—March 30, 2006

• Improved SpamSieve’s accuracy by counteracting various spammer tricks.
• Removed the delay, when using Apple Mail on Tiger, between choosing “Train as Good” or “Train as Spam” and when training actually started.
• The Entourage scripts now report progress part way through bulk trainings and allow you to cancel. They also warn if it looks like you’re training SpamSieve with too many messages, and they’re better at preventing duplicate categories from being created in Entourage. The “Train Spam” script now removes the spam messages from the server.
• Growl notifications from people in the address book now include the “To” address for mailing list messages. This makes it easier to decide whether to ignore the notification.
• Fixed bug that caused part of SpamSieve’s corpus to be written to disk incorrectly when running on Intel. In most cases, no ill effects would have been observed, and SpamSieve will repair the corpus file the first time you launch 2.4.3.
• Improved the error messages.
• Improved the display of the demo time remaining.
• Updated the localizations.

2.4.2—February 23, 2006

• SpamSieve is now much better at catching a new type of spam message that previous versions had been inconsistent at catching.
• Worked around some more spammer tricks to improve accuracy.
• Improved the way message attachments are analyzed.
• Fixed bug that could cause improper analysis of messages from Apple Mail or Eudora, leading to reduced accuracy.
• Improved phish detection.
• Improved the performance of the Apple Mail training commands on Tiger and Jaguar.
• Made some changes to the way spam messages are colored in Apple Mail. Now, the most spammy color (blue) is reserved for messages with scores 99 or higher, i.e. messages that matched a blocklist rule, had encoded HTML parts, or were known to definitely be spam.
• The Show Window command in Apple Mail can now open the SpamSieve help.
• Under certain circumstances, SpamSieve can now detect at launch whether the application package is damaged, rather than too-quietly reporting errors in the log during message processing.
• Improved the troubleshooting documentation.
• Updated the Japanese localization.

2.4.1—January 25, 2006

• SpamSieve is now a universal binary.
• Made various changes to SpamSieve’s tokenizer and HTML parser to improve accuracy.
• Improved filtering of messages containing attachments.
• Added Apple Mail settings to control whether messages trained as spam are marked as read and/or left on the server.
• Better at finding notification sounds that are built into mail clients.
• Now shows uncertain growls when notification is suppressed.
• SpamSieve now delegates more file reveal operations to Path Finder 4, since it fixes a bug in Path Finder 3 that prevented certain reveals from working.
• Rather than typing (or copying and pasting) your name and serial number to personalize SpamSieve, you can now click the x-spamsieve:// URL that’s sent to you when you purchase SpamSieve or get a serial number reminder.
• Fixed bug where the rules list would scroll one rule up if it was scrolled to the bottom and you edited a rule.
• Added Spanish localization and updated the Danish, Italian, Swedish, and Vietnamese localizations.
• Improved the installation and troubleshooting documentation.
• Removed spurious Section 4.4.1 of the manual.

2.4—November 16, 2005

• Made various changes to the Bayesian engine to improve accuracy.
• Added some heuristics for detecting phishes.
• Apple Mail messages can now be filed into different mailboxes based on how spammy they are (requires 10.3 or 10.4).
• The Apple Mail plug-in is now a Universal Binary, so SpamSieve can be used on Intel-based Macs without running Mail in Rosetta.
• Added support for the new (non-haiku) Habeas headers.
• SpamSieve now plays notification sounds using the alert volume rather than the master volume, and they’ll be played on the same output device as alerts and sound effects. (The old behavior is still in effect when playing classic sound files and when running on Jaguar.)
• Added suppressing notification AppleScript parameter. You can use this to prevent SpamSieve from bouncing its Dock icon or showing Growls when recalculating the spam scores of old messages.
• The Software Update alert is now a sheet, so it won’t interfere with spam filtering.
• If Path Finder is running, it will be used instead of the Finder to reveal files/folders.
• Made various tweaks to keep PowerMates from flashing when they shouldn’t.
• Adjusted the standard set of rules.
• You can now tab back and forth between the search field and table in the corpus and rules windows (requires 10.4).
• Predicted entries in the log now show the message’s sender.
• Added preference to control whether Apple Mail false positives are marked as unread.
• Added Technical Support & Feedback item to the Help menu.
• The Entourage scripts try even harder to avoid creating duplicate categories.
• SpamSieve now avoids loading the address book except when absolutely necessary. Thus, if your address book is corrupted such that loading it would cause a crash, you’ll still be able to receive mail if you turn off SpamSieve’s address book–related features.
• Messages with empty senders are no longer considered to be from people in the address book, even if the address book contains a contact with such an address.
• Fixed longstanding bug in which sorting the blocklist or whitelist by Header or Match Style would group the rules appropriately, but wouldn’t order the groups alphabetically by the localized text in the column.
• Improved the error messages in the application and in the Apple Mail plug-in.
• Made a change to prevent Apple Mail from deadlocking (in rare circumstances) when training SpamSieve on Mac OS X 10.4.3.
• Fixed regression where Trained: (Auto) log entries occurred before the corresponding Predicted ones.
• The Apple Mail training commands now respect the preference for whether to color messages.
• Added hidden preference LogSpam that you can turn on with defaults write com.c-command.SpamSieve LogSpam YES to make SpamSieve keep a maildir-style folder of the spam messages it’s seen. Right now, this is not recommended for general use on slower machines.
• Updated link to Habeas Safelist.
• Updated eSellerate, PCRE, and SQLite libraries.
• Added Danish localization and improved the other localizations.
• Various documentation improvements, including:
  • Described how to place Entourage messages in different mailboxes based on how spammy they are.
  • Added section describing how to redirect non-spam Apple Mail messages to another account, e.g. to filter the mail that you receive on your Blackberry.

2.3.2—August 8, 2005

• Made various improvements to increase SpamSieve’s accuracy.
• Added Quit when mail client quits option.
• Sped up filtering when Growl notifications are enabled. Improved the text/layout of the Growl notifications.
• Re-installing or updating Eudora could have the effect of re-enabling Eudora’s built-in junk plug-ins. This could reduce the filtering accuracy and cause unexpected behavior as multiple plug-ins acted on the same messages. Now, if SpamSieve detects that its Eudora plug-in is installed, it will automatically disable any other Eudora junk plug-ins.
• When you reset the corpus, SpamSieve automatically creates a dated backup so that it’s possible to revert, if need be.
• The pop-up menu for selecting the uncertainty threshold now supports scores as high as 98. This makes it possible to designate all non-blocklisted spam messages as uncertain.
• The S and G indicators are now only shown in the Dock icon after manual training, not auto-training.
• The log is now UTF-8 rather than ASCII, so it should be much more readable for people using localized versions of SpamSieve.
• More errors are now logged.
• Better at finding sound files that are built into Mailsmith.
• Worked around Tiger bug that would cause archived log files to not decompress automatically when opened.
• Fixed regression where SpamSieve could crash if you tried to install the Entourage scripts when Entourage was not installed.
• Fixed bug in Apple Mail’s Train as Good, where it didn’t always move messages out of the Spam mailbox if there were lots of recipients.
• Fixed Entourage Train Good script to not make a new Uncertain Junk category when one already exists (but Entourage says that it doesn’t).
• Worked around AppleScript error that could occur when running Entourage scripts.
• The regex code is more bulletproof in the face of rare OS errors.
• Added better heuristic for determining which files SpamSieve can import addresses from. This should prevent some rare crashes.
• Updated the Habeas link in the Preferences window.
• The history database is more robust on Tiger.
• The Purchase window now makes it more clear when the serial number has been successfully entered. Merged the Web Purchase… and Instant Purchase… buttons.
• Adjusted the way the remaining demo time is displayed, as it led many people to believe that they had less than a month of total trial time.
• Improved training tips and the manual.
• Added French translation of manual. Updated Vietnamese manual. Fixed regression where the Italian and Vietnamese manuals were inaccessible.

2.3.1—May 16, 2005

• Works with Apple Mail on Mac OS X 10.4.1. SpamSieve should automatically install a new copy of its Apple Mail plug-in the first time it’s launched, but if it doesn’t you can do so by choosing Install Apple Mail Plug-In from the SpamSieve menu.
• Various accuracy improvements.
• Renamed the Apple Mail training commands to Train as Good and Train as Spam.
• Train as Spam is much faster in Apple Mail on 10.4 when there are multiple messages selected.
• If SpamSieve’s Dock icon is hidden, a new SpamSieve - Open Window command will appear in Apple Mail’s Message menu. This lets you quit SpamSieve or access its windows and settings while its menu bar is hidden.
• Worked around Apple Mail bug so that Train as Good now moves spam messages out of Mail’s Spam folder on 10.4, provided that SpamSieve had put them there.
• Reduced the maximum size of the Growl notification bubbles.
• Better at parsing malformed messages.
• The HTML parser is much faster with certain pathological spam messages that could previously drag parsing out for a minute or more.
• Worked around Entourage bug that could lead to the creation of multiple Uncertain Junk categories.
• SpamSieve no longer complains about the permissions on Apple Mail’s Bundles folder if you’re using a different mail program.
• Removed the Prune Corpus command. With auto-training being much smarter than in earlier versions, it’s almost never advisable to prune, and improper pruning severely reduces accuracy.
• The demo reminder window updates the number of days remaining if you leave SpamSieve running for days or weeks at a time.
• Fixed bug that could cause a crash when using Instant Purchase.
• Worked around crash caused by bug in 10.2.
• Updated localizations.

2.3—April 25, 2005

• General
  • Works with Mac OS X 10.4 (Tiger).
  • Made lots of improvements to SpamSieve’s parsers and tokenizer for better accuracy. To fully take advantage of this, you will need to reset SpamSieve’s corpus and re-train it (e.g. with 300 recent good messages and 600 recent spams). However, this is certainly not required, and I expect that most people will opt for the simpler upgrade of just installing the new SpamSieve application.
  • Auto-training works better. SpamSieve is smarter about selecting which incoming messages to train itself with, so that it reaches a high level of accuracy sooner, and it is better at adapting to new types of mail that you receive.
  • Improved the training tips and the training section of the manual so that it’s clearer what the best practices are.
  • When training the whitelist, SpamSieve will now create rules that match the addresses of the other recipients. This should reduce false positives from people who haven’t previously sent you mail, but who correspond with the same people you do.
  • Added Update Address Book “Me” Card command.
• Scriptability
  • Added selection AppleScript property, which can be used to get the selected token infos in the corpus or the selected rules in the whitelist or blocklist window. One use of this is demonstrated in a script that adds the addresses of the selected whitelist rules to the Address Book.
  • Added AppleScript properties and commands to access SpamSieve’s windows and log. One use of this is demonstrated in a script that lets you open SpamSieve’s windows if its Dock icon is hidden (and thus the menu bar is inaccessible).
• Notification
  • Added option to control whether Growl notifications contain excerpts of the message body.
  • The new message count in SpamSieve’s Dock icon is now auto-positioned.
  • Fixed regression where dragging the slider to adjust the size of the number in the Dock icon didn’t temporarily show the number so that you could preview the results.
• Apple Mail Integration
  • Improved accuracy due to better decoding of Apple Mail messages.
  • The commands for training SpamSieve from Apple Mail are now in Mail’s Message menu, rather than in the Scripts menu. This lets you access those commands in the same way on 10.2 through 10.4, and you don’t have to worry about changing the scripts around if you boot into a different version of the OS.
  • The Apple Mail plug-in is faster at processing messages.
  • If the Apple Mail plug-in is installed but disabled for some reason (e.g. a location switch or OS re-install), SpamSieve will automatically re-enable it (takes effect when you relaunch Mail).
  • Worked around bug in Mail that could prevent Train Good or Train Spam from working properly when training multiple messages at once that were already in their final destination.
• Eudora Integration
  • The installer no longer asks you to find Eudora except when absolutely necessary.
  • The Eudora plug-in is now installed in the Application Support folder rather than inside the Eudora application package. Thus, it’s no longer necessary to re-install the plug-in when updating Eudora, although you still may need to disable the SpamWatch and SpamHeaders plug-ins if updating Eudora re-enables them.
  • Added a Cancel button to the alert that you get if Eudora is already running when you ask SpamSieve to install the Eudora plug-in, in case you don’t want to quit Eudora at that time.
• Fixes and Tweaks
  • The Apple Help is now multiple linked pages, rather than a single page, so you can now use Help Viewer’s search box.
  • Simplified the setup instructions in the manual, and added new sections on customization.
  • Improved duplicate message detection.
  • Fixed bug where e-mail addresses were not always correctly parsed out of mail headers.
  • Tweaked the format of Trained entries in the log.
  • Worked around OS bug that could cause SpamSieve to freeze when installing AppleScripts.
  • SpamSieve is better at following aliases and more tolerant of incorrect permissions when looking for its support files.
  • Updated to eSellerate Engine 3.6.1.
  • Improved serial number name entry.
  • Various localization fixes.
  • The ? buttons in the Preferences window now open the specific help sections on Jaguar.
  • Fixed longstanding unreported bug where you could launch multiple instances of SpamSieve if you were using Jaguar.

2.2.4—February 10, 2005

• Increased the speed of SpamSieve’s message processing.
• Processing messages with Entourage is much faster. To realize the speed increase, re-install SpamSieve’s Entourage scripts and let it replace the existing ones.
• Improved accuracy through better HTML and header processing. (It is not necessary to reset the corpus.)
• Colors to indicate spamminess in Apple Mail are now enabled by default.
• Can now play sounds (and bounce the Dock icon) when mail arrives, even if SpamSieve or a mail program is frontmost.
• Added option to Entourage’s Change Settings to make all spam messages marked with category Junk instead of marking some of them with Uncertain Junk.
• Added more standard blocklist rules for non-Latin character sets.
• AppleScript errors complaining about not being able to find the SpamSieve application should be much less common now. If you do see such an error, asking SpamSieve to re-install the scripts for Apple Mail or Entourage (and letting it replace the existing scripts) should cure things.
• Improved name and serial number entry.
• The Edit Log command is no longer an alternate menu item.
• Can now load Entourage addresses when Launch Services can’t find Entourage.
• The default classifier reports better scores.
• The behavior of the default classifier (if no rules or other classifiers match, and the Bayesian classifier is disabled) may now be changed by setting the DefaultIsGood default. Normally this is YES, but you can set it to NO to make SpamSieve treat all non-whitelisted messages as spam.
• Pruning now is recorded in the log.
• Updated the Russian localization.
• Added Swedish and Vietnamese localizations.
• Expanded and improved the manual.
• The Entourage scripts no longer mark messages with multiple copies of the same category.
• Fixed bug where SpamSieve would sometimes incorrectly think that it had made a mistake (if auto-training was on and the user had asked it to reclassify a message).
• Fixed bug in the Change Settings scripts.
• No longer reports an error when trying to reset an empty initial corpus.
• Fixed crash when quitting after resetting an empty corpus.
• Fixed bug where SpamSieve would crash when reading a damaged corpus file.
• Worked around OS bug that could cause crashes when creating the Uncertain Junk category in Entourage.
• Notification dismissal now works on Tiger.
• Apple Mail’s scripts are now installed in the correct location when running on Tiger.

2.2.3—November 15, 2004

• Fixed bug where SpamSieve would complain of a permissions error at startup.

2.2.2—November 14, 2004

• Can notify with Growl when good messages arrive, and to help spot false positives without looking through the entire contents of the spam folder.
• Added Change Settings commands for Apple Mail and Entourage, which let you configure script options (spam folder name, behavior when using Train Good and Train Spam, etc.) without having to edit the scripts. The settings are stored in SpamSieve’s preferences file, so they will persist if you update or re-install the scripts.
• Fixed bug where SpamSieve would report a syntax error when processing certain messages (typically in non-ASCII character sets).
• Better accuracy due to improved header and body analysis.
• Better accuracy due to smarter auto-creation of From (name) rules.
• Auto-training now takes scores into account; the corpus is updated using messages that were harder to classify, to forestall errors.
• Better handling of spam messages that lie about their encoding.
• Entourage now uses two separate categories for spam messages, so that you can see which ones are more (or less) spammy.
• Improved accuracy when processing messages in German.
• Any Address rules now match SendTo addresses.
• Better handling of messages with “From ” lines.
• Worked around Mail performance problem where Add Good would hang if there were a lot of recipients.
• The Dock (and DragThing) good message counter no longer increases for messages received while the mail program is active.
• Added Russian localization.
• Improved the French localization.
• Better recovery from damaged Rules and History.db files.
• Added Italian-localized installation instructions.
• Improved launch time.
• Better parsing of PGP messages.
• Worked around 10.2 bug that could cause crashes when the Training Tip window was updated.
• Fixed bad interaction between auto-training and duplicates when the corpus was small.
• More tolerant of incorrect file and folder permissions.
• If Launch Services cannot find the Eudora application, the installer will now try some heuristics and prompt the user to locate Eudora, rather than giving up.
• The Apple Mail and Eudora plug-ins are better at finding and launching the SpamSieve application, and they will notify the user if they are unable to do this.
• Updated to eSellerate 3.5.9, which provides support for registration names using non-ASCII characters.
• When you type in your serial number, SpamSieve normalizes its spacing and case.
• The Add Good and Add Spam AppleScripts have been renamed Train Good and Train Spam. When installing the new scripts, SpamSieve will automatically move the old ones to the trash.
• The Entourage spam folder is now called Junk E-mail instead of Spam, since Entourage 2004 already has a so-named folder.

2.2.1—September 20, 2004

• Shows count of new good messages in DragThing 5.3 and later, if you install an integration script. (This script will be built into future versions of DragThing.)
• Fixed accuracy regressions from 2.1.4 and made some accuracy improvements.
• Added Italian localization.
• Auto-training will no longer add duplicate messages to the corpus, because they interfere with undo.
• You can now start a new paragraph in the crash reporter by pressing Return rather than Command-Return.
• Tries to add itself to the Launch Services database at launch, to make it easier for the scripts and plug-ins to find the SpamSieve application.
• Fixed bug where the help buttons in the Preferences window didn’t work unless the main help had previously been opened.
• Improved the French and Japanese localizations.
• The Edit Log command will now open the log using an editor, rather than Console, if BBEdit is unavailable.
• Improved accuracy statistics when using Apple Mail IMAP accounts.
• The mailbox parser is faster and more tolerant of malformed mbox files.
• No longer tries to roll over the log more than once per day.
• Fixed regression where adding to the whitelist or blocklist didn’t work if a disabled rule matched the message.
• Fixed crash that could happen when showing progress bar at launch.
• Fixed crash when scanning System 7–format sounds.
• Fixed bug where slightly spammy Apple Mail messages would be colored and recorded as spam, but not moved to the Spam mailbox.

2.2—August 24, 2004

• Accuracy Improvements
  • SpamSieve is smarter about what text to tokenize, it extracts more information from messages, it’s better at detecting invisible text, and it can undo more spammer obfuscations.
  • The Bayesian classifier can leverage the results of SpamAssassin’s heuristic tests. It also assigns better word probabilities and is better at deciding which parts of the message are important.
  • Messages containing Habeas headers are now checked against the Habeas Whitelist. This protects against spam messages that include Habeas headers in order to get through filters.
  • Removed the Import Seed Spam command, as it would reduce accuracy with recent versions of SpamSieve.
• General Improvements
  • Auto-training is more automatic. There is now a single checkbox to enable auto-training and, if it’s on, SpamSieve will try to do the right thing when it processes new messages. That is, it will train itself using messages of the types that it needs to see more of, and it will prevent the corpus from growing unbalanced or overly large. Also, it will update the whitelist using every incoming good message, so that you can have a complete whitelist without bloating the corpus.
  • The rules and corpus windows now have toolbars, and they support iTunes-style filter-searching.
  • The corpus and rules are now scriptable, and SpamSieve now supports AppleScript Kit terminology.
  • Assorted performance enhancements make SpamSieve faster and improve the responsiveness of its user interface.
  • Added Portuguese localization.
• Blocklist and Whitelist
  • Rules support more match fields: From (name), Any Recipient, Any Address, Any Character Set, and Any Attachment Name.
  • The new Import Addresses… command lets you import blocklist and whitelist rules from text files (e.g. address book exports or mbox files).
  • Added default blocklist rules for .pif and .scr attachments and a default whitelist rule for lists.c-command.com.
  • Rules can now match the empty string, e.g. when there is a subject header, but the subject is blank. They can also match absent headers by matching against, e.g. <SpamSieve-Unknown-Subject>.
  • The Text to Match field now abbreviates using an ellipsis if the text won’t all fit.
• Notification
  • Can make a Griffin PowerMate flash when new good messages arrive.
  • Now supports System 7–format notification sounds as well as Entourage sound sets. In addition to the Library/Sounds folders, SpamSieve will now look for sounds installed with Apple Mail, Entourage, Mailsmith, and PowerMail.
  • Doesn’t play the notification sound if you are using fast user switching and SpamSieve is running in one of the background sessions.
  • Notifications that require dismissal (continuous bouncing, PowerMate flashing) are no longer triggered when SpamSieve or the mail program is already frontmost. Thus, you don’t have to deactivate the mail program and then activate it again to dismiss the notification.
• Apple Mail Integration
  • Sets the colors of spam messages to reflect how spammy they are, making it easier to skim the Spam mailbox for false positives.
  • Protects against Web bugs by telling Mail not to load the images from messages that are classified as spam.
  • The Add Good script is better at moving messages from the Spam folder back to the correct inbox, and it will mark them as unread when it does so.
  • The Add Good and Add Spam now work with Mac OS X 10.3.5.
  • The plug-in will look for SpamSieve in the Applications folder, even if Launch Services is confused and says it can’t find it.
• Entourage Integration
  • The Exclude my addresses switch now also applies to the Entourage address book, to reduce the chances of a forged spam getting through.
  • Added new scripting verb add entourage addresses. This will allow you to keep the Entourage addresses in sync by using an Entourage shutdown schedule.
  • Can automatically add the recipients of the messages you send to the whitelist.
  • Sanity-checks addresses that are loaded from Entourage. For instance, if both the name and the address were entered in Entourage’s address field, SpamSieve will now extract just the address, rather than taking Entourage’s word for it.
  • The Add Good script now works with the Possible Spam folder and marks false positives as unread.
  • Messages can have more than one category, so SpamSieve now adds and removes the Junk category from the message, rather than replacing the category. This means that marking a message as junk doesn’t wipe out other categories on the message.
  • Shows a progress bar while importing Entourage addresses.
• Eudora Integration
  • Removed the option to use the full Eudora junk score range; this setting is now always in effect.
• Mailsmith Integration
  • Can automatically add the recipients of the messages you send to the whitelist.
• PowerMail Integration
  • Can automatically add the recipients of the messages you send to the whitelist.
• Statistics and Log
  • The Statistics window shows the number of blocklist and whitelist rules and the number of spam messages received per day. The date sheet has a Now button that enters the current date and time.
  • The log is now stored in ~/Library/Logs/SpamSieve. The Open Log command now opens the log in Console, so that it’s easier to monitor as it changes. To get the old behavior of opening the log in a text editor, hold down Option and choose Edit Log.
  • If the log file grows larger than 5 MB, SpamSieve compresses it, archives it by date, and starts a new log.
  • When SpamSieve makes a mistake, the log records which classifier made the error and what the message’s score was. The log also now records parse errors and the number of messages in the corpus.
• Fixes and Tweaks
  • SpamSieve can optionally show an alternate, more photo-realistic, icon in the Dock.
  • There is a new mailing list for discussion of SpamSieve.
  • Each tab of the Preferences window now contains a help button that will open the corresponding section of the Apple help.
  • Updated to PCRE 4.5 and SQLite 2.8.15.
  • Fixed bug where SpamSieve could crash when generating a message’s identifier if a system routine failed.
  • Fixed bug in EDMessage that could cause crashes when decoding certain quoted-printable messages.
  • Better handling of 8-bit subjects with no specified encoding.
  • Worked around Panther bug that could cause crashes or drawing artifacts on the desktop by no longer trying to draw on the Dock icon when it’s hidden.
  • Worked around OS bug that prevented certain notification sounds from playing.
  • Fixed bug where the selection was not always preserved when editing blocklist and whitelist rules.
  • The Show Corpus, Show Statistics, and Preferences… commands in the Dock menu now bring SpamSieve to the front.
  • The progress window when exporting the corpus sometimes lagged a bit before closing automatically.
  • Fixed bug where SpamSieve would get confused if you entered the empty string as a date.

2.1.4—April 15, 2004

• Fixed bug where SpamSieve could crash when installing the Eudora plug-in if you were using Eudora 6.0.x.
• Fixed regression where SpamSieve couldn’t process certain messages, resulting in a script error and reduced accuracy.
• Added French localization.
• Updated AOL instructions, since AOL now supports IMAP.

2.1.3—April 13, 2004

• Added menu commands for installing the Apple Mail plug-in and scripts, the Eudora plug-in, and the Entourage scripts. These items are now stored inside the SpamSieve application package.
• Scripts for the other applications are now stored inside the application bundle, not at the root of the disk image. The Show Other Scripts menu command will reveal them in the Finder.
• Apple Mail and Eudora users should update their plug-ins, using the commands in the SpamSieve menu.
• Added the score script command, which returns an integer between 0 and 100 indicating how spammy the message is. 50 and higher mean spam.
• The Predicted lines in SpamSieve’s log now show the scores of the messages.
• Can now use Eudora’s full 0-to-100 junk score range if you check the appropriate box in the Advanced preferences.
• Improved parsing of messages with 8-bit transfer data.
• Faster at processing messages.
• Added support for Outlook Express 5.
• Worked around OS bug that could cause SpamSieve to come to the front each time a message was processed in Apple Mail or Eudora (usually if an X11 application was frontmost).
• Fixed bug where errors encountered while processing messages were not reported in the log.
• Worked around Cocoa problem where certain notification sounds wouldn’t play.
• Made the Purchase window easier to understand, and added a button for looking up lost serial numbers.
• Trims the text in the serial number field so people don’t accidentally paste the number in twice.
• Software updater is better at checking whether the computer can connect to the Internet.
• SpamSieve now tries to parse Eudora messages according to RFC822, even though this will sometimes fail, as many Eudora messages are not RFC822-compliant.
• Adjusted the list of headers that SpamSieve ignores.
• Added keyboard shortcuts for Apple Mail scripts.
• Improved the training tips.
• Updated to SQLite 2.8.13.
• Updated to eSellerate SDK 3.5.5.
• The Send Report button in the crash reporter is no longer a default button, so there’s no longer confusion about entering returns in the comment field.
• No longer prints fragments of spam messages to the console when it gets confused.
• Replaced the copy of the manual outside the app with a read-me.

2.1.2—January 26, 2004

• SpamSieve can now move Apple Mail POP messages to the Spam folder. Thus, it now fully supports Apple Mail on Jaguar and Panther.
• Honor Habeas headers is now off by default.
• Fixed regression where blocklist and whitelist rules got deselected after editing their text.
• When loading addresses from Entourage, SpamSieve now picks up addresses that are not associated with any contact (that is, they appear only in a group).
• The default date shown in the Statistics window is now the date that SpamSieve was first launched, rather than September 2002.
• The Apple Mail Add Good script is better at finding the proper inbox when moving false positives out of the Spam folder.
• The Apple Mail Mark If Spam script can mark the spam messages as read.
• The Purchase window now makes it more clear when a serial number has been accepted.
• In the Statistics window, Set… is now Set Date… and Copy is now Copy Stats.
• Fixed crash that could happen when processing messages in Japanese encodings.
• Added Japanese localization.

2.1.1—January 8, 2004

• Much faster at processing messages when there are many blocklist and whitelist rules. Also improved the speed of loading, deleting, and sorting rules.
• Improved accuracy tracking with the Panther version of Apple Mail; previously, SpamSieve couldn’t always tell when it was being corrected.
• Catches more spam because it knows about more spammer obfuscation tricks and also which headers it should ignore.
• Fixed bug (introduced in 2.0) where the Bayesian engine didn’t work if Mac OS X’s default language was set to Japanese.
• The SpamSieve Eudora Plug-In is better at launching the SpamSieve application if it is not already running.
• Loading Entourage addresses now adds to the addresses that were previously loaded, rather than replacing them. This makes it possible for Entourage users who have more than one Entourage identity to give SpamSieve the addresses from all their address books (by loading once for each identity). Hold down Option when clicking Load to get the old behavior of replacing the previously loaded addresses.
• The sound pop-up menu in the Preferences window now immediately notices when new sounds are installed; previously, it would only check when updating the rest of the preferences window.
• You can now add a rule without a the Blocklist or Whitelist window being frontmost. SpamSieve will ask which type of rule to add.
• Regex rules can now start with an options modifier such as (?-i).
• Copying rules to the clipboard now just copies the text to match (typically an e-mail address), not all the columns. To get all the columns, you can print to PDF.
• The Entourage Add Good script now finds localized inboxes, rather than creating a folder called Inbox.
• The Entourage Add Spam script can now remove spam messages from the server.
• The Statistics window now shows percentages instead of ratios.
• SpamSieve will now quit at launch if another copy of the application is already running.
• Re-targeted broken Habeas URL.
• Added the following menu commands: Close All Windows, Minimize All Windows, and Zoom.

2.1—December 9, 2003

• Added support for Apple Mail POP accounts. POP messages can be marked as junk and colored, but (due to limitations in the present version of Apple Mail) they cannot be moved to another mailbox.
• Added a Training Tip window that gives advice on how to improve SpamSieve’s accuracy, based on the current state of the corpus and preferences.
• Rules in the whitelist and blocklist are no longer limited to just matching sender addresses. They can now match a variety of message fields (To, CC, Subject, etc.), as well as the message body. In addition to exact matches, rules now support the following match styles: contains, starts with, ends with (useful for matching domains), and Perl-compatible regular expressions. You can now edit rules and add new rules manually (as opposed to automatically, as a result of training SpamSieve with a message).
• When trained with a good message from a mailing list, SpamSieve will automatically create a whitelist rule based on a mailing list header, if present.
• SpamSieve can now read in the Entourage address book and use it as a whitelist. Thus, the Entourage rule can now give SpamSieve all the messages, not just the ones that were from unknown senders. This means that SpamSieve can now accurately notify the user when non-spam messages are received. Also, the statistics it keeps will be more complete.
• Improved the accuracy of the Bayesian classifier when the corpus is unbalanced.
• Made a variety of low-level changes to improve SpamSieve’s accuracy, for instance: adjusted the list of headers that are analyzed and how words are tokenized.
• The Apple Mail Add Spam script now has an option to control whether the messages are moved to the Spam folder.
• The Entourage Add Good script now moves messages to the inbox if they’re located in the Spam folder.
• Mailsmith users can now auto-train using only spam or good messages by turning off training in Mailsmith and turning on one of the auto-train checkboxes in SpamSieve.
• Improved the importing of mbox files that do not have blank lines between the messages, such as some Eudora mailboxes. Fixed a bug where the the mbox parser could crash if a message had length zero. Also, SpamSieve now shows a progress bar while counting the number of messages that will be imported.
• Improved the corpus and rule list displays. You can now enter and leave editing mode by typing Return. Type-ahead works better; for instance, if you type “g” and there are no rows that start with “g,” it will look for one that starts with “f.” When you delete a word or rule, you can cancel out of the confirmation sheet by typing Escape. To avoid the confirmation sheet entirely, you can delete using Command-Delete instead of Delete. When a word or rule is deleted, SpamSieve selects a nearby rule so that you don’t lose your place. When deleting many words at once, SpamSieve no longer shows a progress window for deletions that will not take very long.
• Entering the name and serial number to personalize SpamSieve is now more foolproof: SpamSieve strips leading and trailing whitespace, and it detects when you enter a coupon code in the serial number field. Fixed regression where SpamSieve rejected names containing non-ASCII characters. In addition, there’s a new button for quickly redeeming coupons.
• Updated to the latest eSellerate SDK so that purchasing SpamSieve from within the application is faster.
• SpamSieve now requires Mac OS X 10.2.6 or later.
• Fixed bug where dates entered in the Statistics window were sometimes parsed in GMT instead of the local time zone, thus causing the date to be off by a few hours.
• Improved the reliability and user interface of the crash reporter.
• No longer crashes when parsing certain non-RFC822-compliant Eudora messages.

2.0.2—October 1, 2003

• Now works with Apple Mail (IMAP and .Mac only, not POP).
• The message count in the Dock icon now resets when an e-mail client becomes active (rather than just when SpamSieve became active). You can also control the size and position of the number in the Dock icon.
• Much faster at deleting lots of rules at once.
• Replaced the message store database with custom code that’s faster and more reliable.
• Improved accuracy for HTML messages containing links.
• Importing mbox files is faster.
• Fixed bug where you couldn’t use Web registration after the demo period had expired.
• The log records which addresses matched the whitelist or blocklist.
• The log records corpus imports.
• Auto-training is faster.
• The Entourage Add Spam script can close the frontmost window if it’s spam.
• Fixed bug where the date in the Statistics window could get cut off if you changed it to use a more verbose format.
• Worked around OS bug that caused dates like “01.09.2003” to be interpreted as January 9 in German-style locales.
• Added Copy button to the Statistics window.
• Fixed problem updating certain history databases from 1.3.1.
• More resilient to minor corpus file corruption.
• Fixed crash that could happen with improperly formed multi-part messages.
• Shows the number of blocklist or whitelist rules in the title bar.
• The whitelist now contains some c-command.com addresses by default.
• Fixed crash when opening the Statistics window while adding messages.
• The Statistics window shows ratios, where applicable.
• Assorted minor performance improvements.
• The modification dates of the AppleScripts are now the actual modification dates, not the date the distribution was built.

2.0.1—September 17, 2003

• Replaced the database engine that was being used to store the corpus with some custom code. This should be much faster and more reliable.
• Loading and saving the rules is faster, due to a better file format.
• The rules and corpus message counts are now saved to disk during idle time rather than when quitting. This should prevent data loss in the event that SpamSieve doesn’t quit normally.
• The whitelist and blocklist are more memory-efficient.
• Plugged memory leak in EDMessage.
• Fixed crash involving certain really long header lines.
• Fixed bug where the Whitelist and Blocklist windows weren’t always up to date.
• Table views are smarter about not scrolling unnecessarily to maintain their selections.
• The Whitelist and Blocklist windows now secondary sort by sender.
• Changes to the preferences are saved to disk immediately.
• Fixed bug where tables saved their sorted columns but didn’t restore them.
• When SpamSieve gets a fatal error, it now quits like it says it will.

2.0—September 10, 2003

• SpamSieve now extracts a lot more information from each message. This makes it much more accurate and also makes it learn faster.
• Now integrates with Eudora 6 (Sponsored or Paid) via a plug-in. It can now process every incoming Eudora message and can be trained using the Junk and Not Junk commands in Eudora’s Message menu.
• SpamSieve now has a blocklist and a whitelist. These are automatically maintained based on the senders of messages that SpamSieve is trained with. The blocklist makes sure that all messages from known spammers are caught and speeds processing for these messages. The whitelist lets you be sure that certain messages will never be marked as spam; this was possible before, but now you don’t have to clutter your address book with addresses from online retailers, etc.
• You can now control how conservative or aggressive SpamSieve is at catching spam.
• SpamSieve can now play a sound or bounce its Dock icon after a batch of non-spam messages has arrived. This is meant to replace your e-mail client’s new mail notification, which you don’t want going off if all the new messages are spam.
• Shows the number of new good messages in the Dock icon.
• Now parses HTML so that it can better extract relevant information from HTML messages, and also handle various HTML-based tricks that spammers use to fool filters.
• New method of calculating word probabilities makes SpamSieve better at discerning which words in the message are important.
• Includes a corpus of seed spam, to jump-start spam recognition for users who do not have many saved spam messages.
• The corpus is now stored in databases rather than in a property list. This makes it launch faster and use much less memory, as the corpus doesn’t have to be all in RAM at the same time.
• The statistics file format (for History.db) has changed in order to enable performance improvements and more statistical displays in future versions.
• Handles more types of plain text obfuscations, and is much faster at undoing them.
• Added option for the address book whitelist to only use other people’s addresses, so that spam messages from your own address don’t match the whitelist.
• Can mark all messages with Habeas headers as good.
• Can mark all messages with some variant of “ADV” at the start of the subject as spam.
• Can mark all base64-encoded HTML messages as spam.
• New probability combiner increases accuracy.
• Uses stop words to speed processing and reduce false negatives.
• When filtering a message, considers the number of occurrences of the words, not just which words are present.
• Can import messages from mbox files.
• Can import the corpus from and export it to an XML property list (the same format used by 1.x).
• SpamSieve can now check for updated versions of itself.
• Added crash reporter.
• Added Dock menu containing frequently used commands.
• The entries in the log are more detailed.
• The corpus now stores the date at which each word was last accessed.
• Fixed bug where storing statistics would fail on systems that didn’t know about GMT.
• Fixed bug where SpamSieve could throw away long runs of HTML thinking they were attachments.
• Added button for opening the Mac OS X Address Book from inside SpamSieve.
• The Statistics window now has a contextual menu item for copying the displayed information.
• SpamSieve no longer wastes cycles updating the Statistics window after it’s been closed.
• The Statistics window is smarter about updating only the portions that could have changed.
• No longer shows Good Words and Spam Words stats.
• Logging has less overhead.
• Updates the history asynchronously, resulting in faster message processing.
• Checks for mistakes in a background thread.
• False negatives are now written to disk in a background thread.
• Re-arranged the Corpus window.
• Pruning the corpus now works by access date rather than by word counts. Of course, you can manually prune the old way by sorting the Corpus window by Total.
• Updated to SQLite 2.8.6 and tuned it for speed.
• Updated to PCRE 4.3.
• Updated to eSellerate 3.5, which should fix crashes some people saw after registering on 10.2.6.
• Now looks at headers of subparts of messages from Mailsmith.
• Time-consuming operations now either have a progress bar or a progress spinner.
• Better at extracting malformed e-mail addresses from headers.
• Copying rows from the Corpus window to the clipboard now uses the order of the columns in the window rather than the default column order.
• Fixed regression where the Entourage scripts no longer created the Spam folder if it didn’t exist.
• Fixed potential crash with regex replacements at the end of a string.
• The history and the corpus files can now be aliases.
• Automatically trims carriage returns and other illegal characters when you paste in your name and serial number.
• Now saves the name and serial number to disk as soon as they’re entered.
• The Spam folder in Entourage no longer has to be top-level.
• Entourage can mark good messages as unread.
• Type-selecting in table views is quicker.
• No longer nags constantly when unregistered.
• Fixed bug where it could look as though SpamSieve had hung if it started up in the background with an empty corpus.

1.3.1—June 18, 2003

• Added direct integration with Mailsmith 2.0 and later. Enabling SpamSieve is as easy as clicking a checkbox. You can train SpamSieve directly from Mailsmith’s Message menu. Bare Bones Software has seamlessly integrated it with Mailsmith’s powerful filtering system, and Mailsmith knows not to bounce its Dock icon after receiving a batch of messages that are all spam.
• Fixed crashing bug triggered by incorrectly encoded headers.
• Regex substitutions are faster and much more memory efficient.
• When adding spam messages to the corpus, the default is now for SpamSieve to move them to the Spam folder.
• The PowerMail Move If Spam script now changes the color of spam messages.
• The Emailer scripts now pass text and HTML attachments on to SpamSieve for analysis.
• Added instructions for using the Entourage and PowerMail address books as whitelists.
• Compacted the ED frameworks to reduce application size and memory use.
• Disabled SQLite’s file locking so that SpamSieve’s data folder can now be located on an AppleShare volume.
• Caches the Address Book to speed whitelist lookups 100 fold.
• The statistics database is faster due to an updated version of SQLite.
• Fixed bad pointer in header extractor that caused unnecessary fallbacks to the secondary parser (reducing accuracy).
• Added experimental support for moving Entourage messages on IMAP accounts to the (local) Spam folder. This can be enabled by editing the scripts with Script Editor.
• For clarity, the names of AppleScripts that ask SpamSieve to predict the category of a message now contain the word “if.”
• Added lots of minor clarifications to the documentation.

1.3—February 11, 2003

• More resilient to spammers’ tricks for obfuscating words.
• Can use e-mail addresses in the system Address Book as a whitelist. Messages sent from those addresses will never be marked as spam.
• Greatly reduced overall memory usage as well as launch and quit times.
• Can save false negatives to disk for later reporting to SpamSieve’s developer.
• You can edit the spam and good counts associated with a word, remove selected words from the corpus, and reset the corpus entirely.
• Type-ahead navigation in the Corpus window. Type the first few letters of a word or number to select it (and scroll to it).
• You can hide statistics from before a set date, to better see the current accuracy and spam reception rate.
• Improvements to the Corpus window: Shows all words rather than only those considered statistically significant. Re-sorting by numeric columns is twice as fast. You can copy the selected rows to the clipboard or drag them to another application. The selection is preserved when you change the sort column, you can sort in descending order, and the sorted column is remembered between launches. The Home and End keys work.
• The Prune Corpus command now tells you how many words it would remove and asks for confirmation.
• The statistics tracking is smarter about handling duplicate messages.
• The statistics have tooltips explaining what they mean, and you can copy all of the statistics to the clipboard at once.
• Improved accuracy tracking of PowerMail and Emailer messages.
• Eudora Integration: Can mark spam messages as read and/or mark them for removal from the server.
• Expanded the AppleScript dictionary, to enable better integration with mail and news clients.
• Entourage Integration: Creates Junk category if there isn’t one, and can mark spam messages as read.
• Mailsmith Integration: The adding scripts now set the appropriate message properties.
• Better parsing of messages with illegal characters in the headers.
• SpamSieve’s Info.plist file contains an LSUIElement entry. Change the 0 to a 1 to hide the application’s Dock icon. (You’ll need to change it back to access the preferences.)
• The message count display has moved from the Corpus window to the Statistics window.
• Better error message when the corpus couldn’t be saved.
• Added tooltips to preferences.
• The registration window gives better feedback when you personalize.
• Better recovery from errors in the corpus file.
• The secondary parser is better at handling DOS linebreaks.

1.2.2—November 20, 2002

• Fixed bug in the PowerMail Add Good script.
• Added uninstaller for Eudora users.
• Better handling of errors while adding messages to the corpus.
• Removed bloat from the Entourage Mark Spam script.
• The application icon now has an alpha channel, so it doesn’t appear with a white halo when viewed on a colored background.
• Minor changes to the manual.

1.2.1—November 18, 2002

• Modified Info.plist to work around a bug in Mac OS X 10.1 that could cause the Finder to crash when launching SpamSieve.

1.2—November 18, 2002

• Added support for Emailer 2.0v3 and Eudora (5.2 and later).
• Decodes base64 and quoted-printable text parts, thus finding words that spammers try to hide from anti-spam software.
• Decodes subjects that use different character sets (e.g. big5).
• Adds special tokens for MIME entities such as part boundaries and uninterpretable message parts.
• Keeps track of the messages added to the corpus, and can optionally prevent you from adding the same message more than once (biasing the counts). Thus, you no longer have to remember which messages you’ve already added.
• You can now “undo” adds to the corpus, e.g. if you added a message as good when you meant to add it as spam.
• Can now add messages to the corpus as they are filtered, so after the initial training you only have to add messages when SpamSieve makes a mistake.
• When filtering a message, SpamSieve can optionally check whether the message is in the corpus. If it is, SpamSieve looks up the answer rather than trying to predict. One use of this feature is that if SpamSieve makes a mistake, you can Add Spam and then Label/Move If Spam and be sure that the message will be labeled/moved.
• Keeps a log of additions to the corpus, filtering results, and errors.
• Mailsmith: If SpamSieve thinks a message is spam, it sets the deleted property of the message to true; otherwise it sets the flagged property of the message to true. Therefore, if SpamSieve has classified the message then exactly one of the properties will be true, and if it hasn’t they’ll both be false. (Normally, neither of these message properties is used by Mailsmith itself.)
• Entourage and PowerMail: If you tell SpamSieve to move spam messages to a spam folder and the spam folder doesn’t exist, the script will create the spam folder for you.
• When you add spam messages to the corpus, can optionally move them to a Spam folder.
• Added status indicators in the Dock icon (like Norton DiskLight).
• The spam probability of unknown words is now 0.4 instead of 0.2.
• The Corpus window uses less memory and sorts much faster.
• Accuracy tracking is faster and uses less memory and disk space.
• Fixed bug where accuracy tracking didn’t work for some Mailsmith messages with multiple parts.
• Improved the manual’s instructions for e-mail client integration.
• Compiled with GCC 3 for greater speed.
• Uses the latest version of the eSellerate SDK, which eliminates a crash at startup under certain circumstances.
• No longer shows the “Upgrading From 1.0” message when starting with a blank corpus.

1.1—September 19, 2002

• E-Mail Client Integration
  • Added support for PowerMail.
  • Added instructions and an AppleScript for making Mailsmith download and filter mail faster.
  • Added an AppleScript for Entourage that moves spam into a Junk folder.
• Performance
  • Launches about 60% faster than 1.0.
  • You can now prune the corpus to remove words that are taking up memory without contributing to spam recognition. This can also dramatically decrease SpamSieve’s launch time.
  • Recalculating spam probabilities is about 10% faster and uses less memory.
  • Quitting is faster because SpamSieve now writes corpus changes to disk during idle time.
  • Saving the corpus is slightly faster.
• Displays statistics about the number of messages filtered, SpamSieve’s accuracy, and the types of words in the corpus.
• SpamAssassin’s X-Spam-Status headers are now treated as single words. This means that if SpamAssassin is running on your mail server, SpamSieve will learn to respect (or ignore) its judgment.
• Does a better job of ignoring e-mail attachments, thus reducing corpus bloat.
• Installs the eSellerate Engine if it’s not present, thus enabling “Instant Registration” for more users.
• Asking SpamSieve to categorize a message now forces an update of all the word probabilities. Previously, the update only happened during idle time.
• Highlights the sorted column in the Corpus window. The columns themselves have shorter names. There’s a new “Total” column. Auto-resizing of the columns works better. You can now manually resize any column, and manual resizings and reorderings are saved between launches.
• Shows fatal errors as alert panels rather than just printing them on the console.
• The Corpus.plist data file is now sorted by word. This makes it easier to examine the corpus manually, and to compare it to other users’ corpora.

1.0—September 10, 2002

• First public release.