[Spambayes] .db files

[Adam Walker]

Kenny Pitt wrote:

>cweisbrod at cogeco.ca wrote:
>  
>
>>Hi there,
>>
>>I've recently started using SpamBayes and have had great success in
>>finally avoiding unsolicited email. The only problem I have with
>>SpamBayes is the significant overhead required to get the code
>>running. Installing the Python binaries first and then having a
>>process that consumes 10-15 Mb of runtime memory is less than optimal.
>>
>>    
>>
>If this is the type of implementation you're looking for, you might be
>better served by the K9 filter here: http://keir.net/k9.html.  It is not
>open source but it is freeware, and the executable is only about 70k and
>uses very little memory.
>
>  
>

I just downloaded and installed K9. The exe is small but it's memory 
footprint on my system is  4388K right after startup.
Spambayes pop3proxy_tray footprint is 7236K after its been running all day.

>>The best implementation would make use of existing
>>spambayes.messageinfo.db and hammie.db files so that any existing
>>training is not lost. However, I need to know how these files are
>>organized. Short of studying the Python source for answers, is there
>>any specific documentation on the organization of these files? If
>>not, would somebody involved with this project be willing to provide
>>me with this information? 
>>    
>>
>
>The .db files use the Berkeley DB engine from Sleepy Cat, and IIRC the
>actual data records are stored in a python-specific format.  Your best
>bet would be to use the sb_dbexpimp script to export your training data
>into a flat file, from which it would be easy to parse and convert to
>any format you want.
>  
>
The format depends on which db is install on your system. But it is most 
likely Berkeley DB.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 261 bytes
Desc: not available
Url : http://mail.python.org/pipermail/spambayes/attachments/20031113/79d3e38f/attachment.bin