Troubleshooting the SpamBayes Outlook addin

This is a list of common problems, and hopefully their solutions.  Please feel free to suggest additional topics.  Currently, we have the following problems listed:
There is also an online FAQ for SpamBayes which may have additional information of use.  You may also wish to see the latest online version of this document for problems added since release.  If you must send someone a mail about SpamBayes, please read this first.

Toolbar items appear, but fail to work

If the toolbar items fail to work, we are faciing one of two problems.
First we will try deleting the toolbar, and if that fails, completely reset all Outlook toolbars.  Perform the following steps.
If all else fails, you can completely reset the Outlook toolbars by removing the file \Documents and Settings\{username}\Application Data\Microsoft\Outlook\outcmd.dat.  Although this is undocumented by Microsoft, we have never heard reports of problems.  If you are paranoid, simply rename this file so that you have a copy.  This has solved all toolbar problems for everyone who has reported one!

Addin loads with an error message

In this case, when you start Outlook you receive a message indicating that SpamBayes could not be initialized.
This means that SpamBayes has loaded, but struck an error during initialization.  If the information in the error message does not indicate the nature of the error, please report a bug (making sure you attach the log file)

Addin doesn't load

If you start Outlook but there was no error message, the SpamBayes toolbar items do not work and new messages have no Spam score or filtering applied, then the plugin has probably become disabled.
    1. Start Outlook, and select Tools->Options to display the main Options dialog.
    2. Select the tab labelled Other, then click on the Advanced button.
    3. Click on the COM Add-Ins button.
    4. If the SpamBayes addin is not listed, then SpamBayes should be reinstalled (Note that running regsvr32.exe spambayes_addin.dll from the SpamBayes directory may also solve this problem)
    5. If the SpamBayes addin is listed but not checked, then simply check it and close the dialog.
    1. Go to Help->About Microsoft Outlook
    2. Click the Disabled Items button.
    3. Select SpamBayes. 
    4. Click Enable.
    5. Restart Outlook 2002.
If you are running from source code, the addin will not appear in the above steps.  Please re-register the addin, as per the README.txt file. If none of that works, I am stumped!

Messages fail to filter

This is when messages arrive, but have no Spam field.  Note that this is different from a message having an incorrect or unexpected Spam value - that case is covered next.  This is for messages that have a completely blank spam score.  To resolve this:

Messages have incorrect or unexpected Spam values

This is when filtering appears to work OK, except that the spam values are wrong.  To resolve this

All other problems

If you are simply unsure about what SpamBayes is doing, please send a mail to the SpamBayes mailing list with as much information as possible.  If you are fairly sure you have struck a bug, then please report it.  Please do not mail any of the contributors directly.

Process Descriptions

This explains some of the processes above in more detail.

Determine your installation type.

If you are running from Python source code, and installed Python, plus SpamBayes as seperate components, then you are running the source code version.  If you downloaded an installer .EXE file, then you are running the binary version.

Check the log file

Determine your installation type.  If you are running the source code version, then please see README.txt in the Outlook2000 directory.
If you are running the binary version, then the SpamBayes addin writes a log in your Windows temp directory.  This directory is generally \WINDOWS\TEMP for Windows 9x, or \Documents and Settings\{username}\Local Settings\Temp for Windows 2000/XP.

Note that by default, in Windows 2000 and XP, Windows Explorer will not show the Local Settings directory, as it is hidden.  You can convince Windows Explorer to show this directory (and therefore allow you to see the Temp directory under it by doing either:
or The log file for the most recent execution of Outlook is named spambayes1.log, the second most recent is named spambayes2.log, and so on for the four previous runs.  You can view this file with notepad.  Usually, you will simply see messages which indicate that SpamBayes is doing its job; however in some cases there will be errors in this file.  If there are errors, please report a bug.

If the log file is very large

This probably means that SpamBayes failed to process a large number of (or a few, large) emails.  In that case, please perform the following steps:
You should have a new log file containing the error when classifying the test message.  If no error occurs processing the test message, the previous large log file will still exist (see above).  Either edit the file using a text editor to extract just the error information, or zip it up.  If you don't know what that means, please send a mail.

Report a bug

All SpamBayes bugs are maintained in this page at sourceforge.  Please have a check of the bugs already reported to see if your bug has already been reported.  If not, open a new bug, making sure to set the Category to Outlook.  Please ensure you attach the log file to the bug.
If you are unsure about the bug, or need any assistance, please send a mail.

Send a mail

If all else fails, you may want to send someone a mail.,  Please make sure you have read this document thoroughly before doing do.
Your mail should be sent to the SpamBayes mailing list (spambayes@python.org)  Please do not mail any of the contributors directly (see "good karma" below).
Please ensure this mail contains:
If you also mention that you read this trouble-shooting guide and are still stuck, then you will be more likely to get answered!  (And if you can subscribe to this mailing list and help answer other questions, good karma will come your way!)