[Spambayes] Rush of spam

[Gary Smith]

HI,

I just returned home and downloaded the latest email. I have one 
non-filtered email address that is work related and I can't miss any 
valid email due to ISP filtering. 

Normally I get several hundred spam/day with this email address but 
usually none get to the email program without being properly ID'd by 
Spambayes. Today was the exception and what came in over the last 5 
hours seemed to pass through the filters. Looking at the raw headers 
I see something from spambayes that I have not seen before.

Here is a copy of what came through:

X-Priority: 3 (Normal)
Message-ID: <769329319.20120119165831 at doctorgary.net>
To: ygary@>My_domain_name<.net
Subject: Need your help!
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------80555C1EBFDADA"
X-ME-Bayesian: 0.000000
Return-Path: <SharonCahalane at preiss85.de>
X-Antivirus: avast! (VPS 120120-0, 01/20/2012), Inbound message
X-Antivirus-Status: Clean
X-Spambayes-Exception: Traceback (most recent call last):
 .  File "sb_server.pyc", line 499, in onRetr
 .  File "spambayes\message.pyc", line 263, in setId
 .  File "spambayes\message.pyc", line 119, in _getState
 .  File "shelve.pyc", line 118, in __getitem__
 .  File "bsddb\__init__.pyc", line 116, in __getitem__
 .DBRunRecoveryError: (-30982, 'DB_RUNRECOVERY: Fatal error, run 
database
 recovery -- fatal region error detected; run recovery')
X-PMFLAGS: 570966400 0 65537 PC1U10EO.CNM   

And here is Spambayes x-header from another SPAM:

X-Spambayes-Exception: Traceback (most recent call last):
 .  File "sb_server.pyc", line 499, in onRetr
 .  File "spambayes\message.pyc", line 263, in setId
 .  File "spambayes\message.pyc", line 119, in _getState
 .  File "shelve.pyc", line 118, in __getitem__
 .  File "bsddb\__init__.pyc", line 116, in __getitem__
 .DBRunRecoveryError: (-30982, 'DB_RUNRECOVERY: Fatal error, run 
database
 recovery -- fatal region error detected; run recovery')
X-PMFLAGS: 570966400 0 65537 PX95HI1A.CNM

It appears the spambayes portion was experiencing an exception and 
with that 30+ SPAM made it through the filtering.

Any ideas what may be the cause of this glitch?

Thanks!