[Spambayes] Installing Spambayes on Windows 2003

[Robert Neuschul]

Follow Up:

Notes on how to install SpamBayes on Windows 2003.

   The Windows Executable version of SpamBayes does not appear to  work 
correctly on 2003. One needs the platform independent version.

   Both Python.org and AS Python's latest Windows installable builds 
fail in the same manner due to changes in the SYSTEM account securities 
and in Active Directory. See below for details. Python.org 2.3.4 is a 
more reliable install, but both /will/ install if care is taken. If one 
gets it wrong then one is left with an uninstallable [I.E Windows 
Add/Remove Programs won't work] and corrupt version of Python which 
takes some messing about to get rid of.


1] To install Python.org 2.3.4 run the setup executable from a 
temporary folder on the local disk where the installed product will run 
- e.g. place the installer at c:\temp and install to c:\Python23

2] When asked whether to install as Administrator or for Each User DO 
NOT CHOOSE ADMINISTRATOR! An Admin install will fail with corrupt 
system environment issues.

3] Reboot the system. Check the environment to make sure that the 
python path is correctly initialised [open a CMD shell, type SET and 
check the last clause in the PATH variable is often the easiest way].

4] Use the platform independent ZIP version of SpamBayes. Expand the 
zip to a local temporary folder, and copy the core into a folder of 
your choice on the root drive.
Open a command session and CD to \%spambayes%\windows and run 

"python pop3proxy_service.py --interactive install" [without the "]

5] **IMPORTANT** 
Go to CP, Administrative Tools, Computer Management, Services; find the 
Spambayes service, open its properties, Log On and set it to use the 
Administrator account. IT WILL NOT RUN CORRECTLY OR AT ALL AS SYSTEM 
ACCOUNT. Apply the changes and start the service.

6] Open a browser and point it at localhost:8880 - select the 
configuration page; make the necessary changes to your configuration as 
required and save BUT DO NOT ALLOW THE CONFIG PAGE "SAVE" TO STOP THE 
SERVICE!
Note: if you are also runnning Exchange Server on the same machine then 
make sure to change the relevant default SMTP/POP3 ports [110/25] as 
required, otherwise POP3 clients' traffic from your lan will get 
intercepted by Exchange before reaching SpamBayes.

My next step: to test how SpamBayes can be made to work reliably with 
Exchange.

Hope this helps others.

Robert.