[Assp-user] HMMdb empty in analyze report?

[Jay <he...@he...>]

Alright this is kind of puzzling to me. We are using ASSP version 
2.4.5(15162) and also using MYSQL for our database backend. When I send 
a request to ASSP for analyzing an email I get a weird response back in 
the email. I get the Bayesian analysis back just fine, but the HMM is 
blank. DoBayesian and DoHMM are both set to score in my config. Under 
the section for Hidden-Markov-Model Spam probabilities the results come 
back as follows:

*combined HMM spam probability*: 	got no result because the HMM database 
is empty
*HMM confidence*: 	0.00000000
*corpus confidence*: 	1.00000000


Which is really odd, here's the last section of my rebuild from this 
morning:

Oct-28-15 07:15:58 Spam Weight:	   8,312,860
Oct-28-15 07:15:58 Not-Spam Weight:   8,314,034

Oct-28-15 07:15:58 Corpus norm:	0.9999 - (very good - balanced)
Oct-28-15 07:15:58 Corpus confidence:	1.00000000

Oct-28-15 07:16:03 Start populating Hidden Markov Model. HMM-check is disabled for this time!
Oct-28-15 07:16:03 start populating Hidden Markov Model with 4,282,658 records!
Oct-28-15 07:16:46 Finished populating Hidden Markov Model with 4,282,658 records!
Oct-28-15 07:16:46 Finished populating Hidden Markov Model. HMM-check is now enabled again!

We recently switched our rebuild to use the BerkleyDB for rebuilding the 
spamdb. Here's a snippet from the top of my rebuilddebug.txt file:

Oct-28-15 06:00:00 rebuild debug output is enabled to 
c:/assp/rebuilddebug.txt
Oct-28-15 06:00:00 RebuildSpamDB uses BerkeleyDB for temporary hashes
Oct-28-15 06:00:00 RebuildSpamDB uses BerkeleyDB-ENV with 50.00 MByte
Oct-28-15 06:00:00 RebuildSpamDB-thread rebuildspamdb-version 7.11 
started in ASSP version 2.4.5(15162)
Oct-28-15 06:00:00 RebuildSpamDB will create a Hidden Markov Model

So is there something I am missing here? I seem to remember that before 
we switched to the BerkleyDB for rebuild the HMM section populated 
information just fine. Now the report claims the HMMdb is blank. Is 
there something wrong with the BerkleyDB rebuild?

Here's the version we are using for the BerkleyDB: (Directly from the 
ASSP email interface)
BerkeleyDB     0.51 / 0.42     enabled
BerkeleyDB_DBEngine     5.3 / 4.5     enabled