[Spambayes] Spambayes 1.1a1 too many problems?

[Dick H]

Hi,

After I upgraded from 1.04 to 1.1a1 I had several problems that I had to decide to go back to 1.04.

Some of the problems I had were:

1) Spam/Ham training through the online server did not cause any change in the statistics but all messages ended up in the pop3proxy-ham-cache or pop3proxy-spam-cache directory depending whether the messages were trained as ham or spam.

2) Once all the training messages ended up in the cache directories, it took ages to start the Spambayes server.

3) Intermittently, I saw e-mail message headers with the following errors:
X-Spambayes-Exception: Traceback (most recent call last):
 .  File "sb_server.pyc", line 564, in onRetr
 .  File "spambayes\message.pyc", line 452, in addSBHeaders
 .  File "spambayes\message.pyc", line 401, in RememberClassification
 .  File "spambayes\message.pyc", line 377, in modified
 .  File "spambayes\message.pyc", line 181, in store_msg
 .  File "shelve.pyc", line 130, in __setitem__
 .  File "bsddb\__init__.pyc", line 218, in __setitem__
 .DBRunRecoveryError: (-30978, 'DB_RUNRECOVERY: Fatal error,
 run database recovery -- PANIC: Invalid argument') 

4) Error messages in the logfile like:
C:\Program Files\SpamBayes\lib\spambayes.modules C:\Program Files\SpamBayes\lib\spambayes.modules\spambayes\languages
Service not available. Using thread.
Loading database... Listener on port 8110 is proxying mail.runbox.com:110
Listener on port 8111 is proxying mail.bluebottle.com:110
Listener on port 8112 is proxying pop.unlimitedmail.org:110
Listener on port 8113 is proxying mail.prettel.nl:110
User interface url is http://localhost:8880/
Loading database... Listener on port 8110 is proxying mail.runbox.com:110
Listener on port 8111 is proxying mail.bluebottle.com:110
Listener on port 8112 is proxying pop.unlimitedmail.org:110
Listener on port 8113 is proxying mail.prettel.nl:110
error: uncaptured python exception, closing channel <spambayes.Dibbler._HTTPHandler connected at 0x98437b0> (socket.error:(10053, 'Software caused connection abort') [asynchat.pyc|handle_read|89] [asyncore.pyc|recv|343])
Almost immediately after this error, the Page File increased to over 1.3GB!!! and my system slowly died. 

The above mentioned problems made the behavior of SB too unreliable for me so I decided to delete both .db files, empty the cache directories and started from scratch with version 1.04, which was very stable for me. After I trained 1.04 with ham and spam messages, there were no messages in the cache directories and the statistics were updated properly. 

Am I the only one suffering from these problems or is this 1.1a1 or Python version unstable?

Note that I'm using the pop3 interface only, no Outlook.  

Best regards,
 Dick
-- 
____________________________________________________________________
You wake me up early in the morning to tell me I am right? Please wait
until I am wrong.-- John von Neumann, on being phoned at 10 a.m.