Hi! I've looked through the documentation available and was unable to find anything about this issue, so I apologize if it has been covered somewhere already. If you can point me to that place, I would appreciate it. I have been running SpamBayes for a long time and it has been amazing! Lately however, it seems to "lock" Outlook (shows the "Not Responding" message) for a number of seconds while it filters the message. During that time, if I am in the middle of typing a new message, it will stall and not allow me to type (if I keep typing, I'll see the typed text when the message is filtered and Outlook is "released"). If I try to access another folder or try to access a message in my Inbox, I won't be able to. Even when I go to open SpamBayes, everything gets locked up until the interface opens, which takes between 10-15 seconds, sometimes longer. Changing between tabs in the SpamBayes manager "locks" up the interface, releasing it after 10+ seconds and opening the contents of the clicked tab. Closing out of SpamBayes manager behaves the same. With SpamBayes disabled, I do not experience these "locking" issues with Outlook. I have no other intensive applications running and the memory only spikes when Outlook/SpamBayes locks up. I do have a warning in the SpamBayes manager that tells me that I have much more spam than ham (382 ham vs. 5255 spam). The SpamBayes database, located in AppData\Roaming\SpamBayes, is over 10MB. I am running Vista Business 32 bit OS with Intel Core 2 CPU, 2046MB RAM. I am running Outlook 2007. Exchange 2003. SpamBayes 1.0.4. I have restarted both Outlook and my computer numerous times. I have also deleted all messages from my Junk email folder.
Please let me know what I could do to get SpamBayes back to behaving "normally". I appreciate your help Irena Suput
_______________________________________________ SpamBayes@python.org http://mail.python.org/mailman/listinfo/spambayes Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html