[Spambayes] Help please - More detailed confiuration options needed

[Robert Neuschul]

Hi 

I sent this to the list a couple of weeks ago but haven't received any 
responses as far as I can tell.

**********************************************************************

I've just rebuilt our 2003 server [SP2] and done a clean install of the 
latest Windows binary version of SB, using only the POP3 proxy 
[SpamBayes Proxy Version 1.1a3 (August 2006)]. 

Having browsed the web site docs I can't find anything to explain the 
behaviour I'm seeing. Because we're not running the SMTP proxy, and 
don't use the redirect to SMTP there are no SMTP "train as" addresses 
set.

The ini file reflects the absence of the SMTP settings.

I also have the SB system configured to "notate to" for spam/unsure, 
and to classify subject headers only for spam.

Whatever settings I use SB insists on adding "unsure at spambayes.invalid" 
as a "To:" address in all messages about which it is unsure.

I'm fairly sure that the older [nonbinary] version I used to 
permit one to control what addresses [if any] were added on the To: 
line, and what wording was added to subject and X headers etc, via ini 
settings, but I can't find any documentation in the current version 
that supports this.  I'm probably being quite blind here. The FAQ 
suggests that one needs to look in options.py for details of the 
various configurable items, but in the binary version of Spambayes 
there is no such file.

I really need to a] prevent SB adding unecessary addresses to the To: 
headers and b] manage /what/ is added to the subject line. Suggestions 
or pointers welcomed.

Footnote on an issue you may want to know about: if one has a proxy 
service installed on a 2000/2003 server, with SB Tray Icon set to open 
on login, and one is using Windows Terminal Services or Remote Desktop 
to connect to the target machine then in most cases [unless one makes 
special effort to do otherwise] one is connecting to Console 1 rather 
than Console 0. That means that there's a new instance of the Tray Icon 
starting up as one logs in; the SB Tray app /really/ does not like a 
2nd instance of itself running and will report that the SB service is 
not running when it /is/ running correctly. If one mistakenly attempts 
to 'start' the service from the tray icon one gets a lengthy timeout 
eventually followed by an error that the service could not be started.

TIA

Robert