[spambayes-bugs] [ spambayes-Bugs-796351 ] server on review messages

Thu Aug 28 16:57:03 EDT 2003

Bugs item #796351, was opened at 2003-08-28 12:06
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=796351&group_id=61702

Category: pop3proxy
Group: None
>Status: Closed
>Resolution: Later
Priority: 5
Submitted By: Tim Murphy (msolutions)
Assigned to: Nobody/Anonymous (nobody)
Summary: server on review messages

Initial Comment:
I have a new install of spambayes and think I've set it 
OK but after receiving some messages I now get the 
following when attempting to review messages:

500 Server error
Traceback (most recent call last):

  File "C:\PROGRA~1\Python23\Lib\site-
packages\spambayes\Dibbler.py", line 398, in 
found_terminator
    getattr(plugin, name)(**params)

  File "C:\PROGRA~1\Python23\Lib\site-
packages\spambayes\ProxyUI.py", line 369, in onReview
    keyedMessageInfo[judgement].append((key, 
messageInfo))

KeyError: 'jdgandia at hotmail.com'

==============================

My bayescustomize.ini is as follows:

[html_ui]
display_to: True

[pop3proxy]
listen_ports: 110,11002
remote_servers: pop3server,mail.optusnet.com.au

[smtpproxy]
listen_ports: 25,2502
remote_servers: smtpserver,mail.optusnet.com.au

[Hammie] 
# The name of the header that hammie adds to an E-
mail in filter mode 
# It contains the "classification" of the mail, plus the 
score. 
hammie_header_name: To 

# The three disposition names are added to the header 
as the following 
# Three words: 
header_spam_string= spambayes_is_spam
header_ham_string= spambayes_is_ham
header_unsure_string= spambayes_is_unsure

================================

The following is the email I suspect that is causing the 
problem.

Return-Path: <luvenia_makte52 at cs.com>
Received: from eex2.Experteilag.no ([193.212.211.162])
	by mail016.syd.optusnet.com.au 
(8.11.6p2/8.11.6) with ESMTP id
	h7RFDaF29195
	for <msolutions at optusnet.com.au>; Thu, 28 
Aug 2003 01:13:36 +1000
Received: from smtp0371.mail.yahoo.com 
([200.90.104.92]) by
	eex2.Experteilag.no with Microsoft SMTPSVC
(5.0.2195.5329); 
	Wed, 27 Aug 2003 17:16:45 +0200
Date: Wed, 27 Aug 2003 15:06:34 GMT
From: ""<luvenia_makte52 at cs.com>
X-Priority: 3
To: jdgandia at hotmail.com
Subject: .WS (WebSite) Domains Still 75%+ Available 
(But Going Fast).
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: 
<EEX26vhSaRM4vNQXzkN00001d27 at eex2.Experteilag.no>
X-OriginalArrivalTime: 27 Aug 2003 15:16:48.0929 (UTC)
	FILETIME=[3C5C3110:01C36CAE]
To: spambayes_is_unsure

----------------------------------------------------------------------

>Comment By: Tony Meyer (anadelonbrin)
Date: 2003-08-29 10:57

Message:
Logged In: YES 
user_id=552329

Well, yes, that was always going to work because, as I said, 
it's the interface that uses "_", not anything in the options 
themselves.  By this can I assume that you don't care 
whether the interface works in this particular case?  If not, 
please reopen.

BTW, you need to re-read Richie's comment.  Using the CC 
header will end up causing you strife.  You will probably loose 
any information that is previously in the CC header (i.e. 
people that the message was CC'd to).  You need to use a 
header that doesn't previously exist - like X-SpamBayes-
Classification.  If you want the notatation in a standard 
header (perhaps you can only work with those), then you 
need to use the notate_to or notate_subject options, as 
Richie said.  If you want a notate_cc option, then please 
open a feature request.

BTW, your options will break in the 1.0a6 release, as you are 
using deprecated names.  These options should all be in 
the "Headers" section, and the hammie_header_name option 
should be classification_header_name.

----------------------------------------------------------------------

Comment By: Tim Murphy (msolutions)
Date: 2003-08-29 10:07

Message:
Logged In: YES 
user_id=853728

I seemed to have fixed the problem. It seems to me that if 
you use SpamBayes before updating the hammie section of 
bayescustomize.ini you run into the problem. So I did the 
following and all seems fine now:

1. Close pop3proxy.py
2. deleted contents of pop3proxy-ham-cache, pop3proxy-
spam-cache & pop3proxy-unknown-cache folders.
3. Deleted spambayes.messageinfo.db and hammie.db. 
4. Updated bayescustomize.ini as required
5. All seems great now.

I've change the hammie section of bayescustomize.ini to:

[Hammie] 
hammie_header_name: CC 
header_spam_string: spambayes_is_spam
header_ham_string: spambayes_is_ham
header_unsure_string: spambayes_is_unsure

================================

Thanks for the help. Great product once you work out how to 
install it.

 Great product once you get it going.

----------------------------------------------------------------------

Comment By: Richie Hindle (richiehindle)
Date: 2003-08-28 19:04

Message:
Logged In: YES 
user_id=85414

Another problem is this:

hammie_header_name: To

The hammie_header_name is intended to be a *new*
header that gets added to the message, not an existing
header name.  If you want the To header to tell you
whether a message is spam or not, you should set the
'notate_to' option to a comma-separated list of any of the
classification values (in your case, 'spambayes_is_spam'
and family).  For instance:

notate_to: spambayes_is_spam, spambayes_is_unsure

----------------------------------------------------------------------

Comment By: Tony Meyer (anadelonbrin)
Date: 2003-08-28 12:19

Message:
Logged In: YES 
user_id=552329

I believe this could be as a result of having "_" in your 
disposition names.  The UI currently uses "_" to fudge 
together section/option names.  It's a bit of a hack (and it 
says so in the code), but it works, for the most part.

Could you try it without having any "_"s in your disposition 
names?  If this fixes it, then either we need to come up with 
a new method for the interface, or you need to use 
something else for the names.  Is there a reason that you are 
using non-standard names?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=796351&group_id=61702