Christopher Faylor <[EMAIL PROTECTED]> wrote:
> Can I point out that it is probably possible to use spamassassin on
> Windows, if you run it under Cygwin (www.cygwin.com)?  Although, I sort
> of run the cygwin project, I have never actually tried it.

Just for grins I saw how far I could get without much effort on a Windows
2000 machine I have that has Cygwin installed.

This is a current Cygwin, installed with Perl v5.6.1 fairly recently.

I started with SpamAssassin source pulled from CVS.

I had to change one thing to make it: In Makefile.PL I changed every
occurrence of 'spamc' that referred to the file to be 'spamc.exe'.

Make test had a bunch of failures but make install was fine. spamassassin -t
on the two samples worked ok.

spamd would not run until I commented out line 663 in SpamAssassin.pm which
says

  return $ENV{HOME} if $ENV{HOME} =~ /\//;

The error message I got was

Use of uninitialized value in pattern match (m//) at
/usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin.pm line 663.

echo $HOME does show that it is set.

After I commented out the line I ran spamd in one window, not using the -d
option, and tried spamc in another. spamc passed through the input unchanged
as if it did not receive any results from spamd. However the -D option in
spamd revealed that it did receive and process the message from spamc and
did produce the correct results.

That's pretty close to working, and spamd/spamc solves the problem of the
overhead of firing up perl. If anyone can explain the few problems, I'll be
happy to continue playing with fetchmail, etc., to see how that goes. Now
I'll boot back into Linux and wash my hands.

 -- sidney



_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to