I received a note from Arik. He has not investigated how to change the code to work with the new changes to spamd.raw in the 3.1.4 release. He made several suggestions. But it just got deeper and deeper with layer after layer of additional error messages after each change.
Bottom line... I uninstalled 3.1.4 and downloaded an older 3.0.x release from SpamAssassin that still had the Sys::Syslog statement in spamd.raw. I made all of the changes again, and everything worked. So PLEASE NOTE: I strongly recommend you don't move up to SpamAssassin 3.1.4 if you have intentions of running spamd on Windows. On the other hand, if someone successfully gets it running with this release on Windows, please post your solution to the wiki. Thanks. Jerry -----Original Message----- From: JWM [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 11:27 AM To: 'James Users List' Subject: RE: SpamAssassin on Windows? Noel, Thanks for the info. However, it looks like SpamAssassin has made some changes to spamd.raw in the later releases, and the referenced wiki instructions are no longer completely correct. I sent the following email to Arik, the writer of the wiki entry. But in the meantime, if anyone knows the fix, please provide info. ================================= I downloaded and installed v 3.1.4 yesterday. I made all the changes as described in your wiki page with one exception: >>>> 5. Further down, comment out the following line by adding a # in front of it: use Sys::Syslog qw(:DEFAULT setlogsock); This line no longer exists in the spamd.raw file. They've obviously changed it to something else. I am an experienced programmer. But I am not familiar with Perl. I know about the syslog problems with windows. I normally can figure out how to tweak instructions for a later release. But I'm lost on this one. I figure I still need to make some change to get rid of syslog. But I can't figure out what to do. Running it without any other change, I get missing library messages. I tried running spamd -s null, and get: [C:\Perl\bin]spamd -s null [3952] info: rules: meta test DIGEST_MULTIPLE has undefined dependency 'DCC_CHECK' [3952] warn: No such signal: SIGUSR2 at spamd.bat line 765. [3952] info: spamd: server started on port 783/tcp (running version 3.1.4) [3952] info: spamd: server pid: 3952 [3952] warn: Use of uninitialized value in pack at C:\Perl\site\lib/Mail/SpamAssassin/SpamdForkScaling.pm line 473. [3952] error: Can't call method "syswrite" on an undefined value at C:\Perl\site\lib/Mail/SpamAssassin/SpamdForkScaling.pm line 613. [3952] error: Undefined subroutine &main::logmsg called at spamd.bat line 811. Undefined subroutine &main::logmsg called at spamd.bat line 811. Can you tell me what change to make with the latest version now that the Sys::Syslog line is no longer there? Thank you. Jerry -----Original Message----- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: Monday, August 28, 2006 8:53 PM To: James Users List Subject: RE: SpamAssassin on Windows? See http://wiki.apache.org/spamassassin/SpamdOnWindows That's about as good as you'll get for MS-Windows, apparently. Alternatively, you could install VMware and run spamd in a VM. You run JAMES inside the VM, too. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
