Mailman 3 June 2006 - spambayes-dev

sb_imapfilter: bad FETCH response
by David Abrahams Aug. 7, 2006

Aug. 7, 2006

FYI, with the CVS HEAD as of 18 January: Loading state from /usr/home/dave/hammie.new.db database /usr/home/dave/hammie.new.db is a new database Loading database /usr/home/dave/hammie.new.db... Done. Account: www.stlport.com:993 Training Training ham folder HamBox Traceback (most recent call last): File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 1283, in ? run() File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 1261, in run imap_filter.Train() File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 1004, in Train num_trained = folder.Train(self.classifier, is_spam) File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 888, in Train for msg in self: File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 799, in __iter__ yield self[key] File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 831, in __getitem__ data = self.imap_server.extract_fetch_data(response_data) File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 455, in extract_fetch_data msg_data = self._extract_fetch_data(msg) File "/usr/home/dave/src/spambayes/scripts/sb_imapfilter.py", line 428, in _extract_fetch_data raise BadIMAPResponseError("FETCH response", response) __main__.BadIMAPResponseError: The command 'FETCH response' failed to give an OK response. (' UID 1967)',) Rolling back to the last released version of spambayes makes this problem go away. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 1

My ongoing problems with tte.py
by skip＠pobox.com June 30, 2006

June 30, 2006

I figured out what was going wrong. Maybe. ZODB generates multiple files, the database itself, an index file, a tmp file and a lock file. The shell script I use to drive tte.py creates the database in a temp directory then moves the file(s) into their rightful place. I did this to avoid problems with the anydbm-style database. I tried modifying my driver script to mv the various files into their correct location, but that didn't work. I finally gave up and update the file in place. SpamBayes now tells me I have an existing database with nonzero ham and spam when I open it: >>> from spambayes import storage >>> dbname, usedb = storage.database_type([]) >>> store = storage.open_storage(dbname, usedb, mode='r') Loading state from /Users/skip/hammie.db (hammie.db) database hammie.db is an existing ZODB, with 92 ham and 272 spam >>> store.close() Closed hammie.db database If I open the file with mode='c' (the default) in tte.py, will the old ham and spam be seen by other processes until I commit/close the database? Skip

1 0

tte.py not working with zodb - no spam/ham counts
by skip＠pobox.com June 29, 2006

June 29, 2006

I'm trying to finish switching from bsddb to zodb. I tweaked the shell script I use to drive contrib/tte.py: python .../contrib/tte.py \ --ratio=<whatever> \ -g <hammbox> \ -s <spammbox> \ -R \ -o Storage:persistent_use_database:zodb \ -o Storage:persistent_storage_file:<zodbfile> \ -c .cull \ -v The only change from the bsddb days was the addition of the two -o flags. Seems to work fine (it spits out all the usual chattiness about number of messages trained and missed), but when I run sb_dbexpimp.py on the result it shows 0 ham and 0 spam and generates a csv file with just 0,0 I suspect the spam and ham counts aren't being written to the zodb file. I see lots of promising clues in the file when I read it into a text editor though, stuff like "url:listinfo" and "received:207.8.226.3". Any idea what I might be missing in contrib/tte.py to force writing the counts? Thx, Skip

2 1

Out of desperation: Help! The (SPAM) enemy is overrunning my position!
by Jeff Hunter June 23, 2006

June 23, 2006

Tony, et al.; You were kind enough to help me out once before, and I am hoping you will do so once again. I am having the same problem as before. However, it is now compounded by the fact that the link on the http://spambayes.sourceforge.net/docs.html <http://spambayes.sourceforge.net/docs.html> to the <http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/spambayes/spa mbayes/Outlook2000/docs/troubleshooting.html?rev=HEAD> "Troubleshooting Guide" responds with: The page cannot be displayed :-( :-( :-( :-( :-( (Try the link above and see what you get.) Here is my problem in a nutshell: Whom it may concern, I have been using SpamBayes for a while and think it is great, but recently it quit working properly. It is no longer filtering emails (they just go into my Inbox, and sit there. I cannot even manually 'delete as spam' them.), nor can I access any way of trying to control SpamBeyes. The file download I used to install it contains only an exe., and does not have any separate documentation file. I have tried uninstalling and reinstalling it several times to no avail. Although, there is still a SpamBayes button at the top left of my Outlook window, I cannot click on it and get any response, nor are there still buttons to move messages to, or recover them from the spam folder. I would really like to get SpamBayes working again, but I am at a loss as to how to go about this. Could you please let me know of any suggestions you might have for doing this. I am running Windows XP Media Center, and Outlook XP client fed from and Exchange server. Please let me know if you know how to resolve this problem! Thanks for your urgently needed help! Best Regards, Jeff Hunter PinPoint Professionals, Inc. (816) 347-8002 (Option #3 for Voice Mail) ***************************************** Confidentiality Notice ************************ The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person) you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing PinPoint Professionals, Inc. (PPI) client engagement letter. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. ************************************************************************ *****************

2 1