Understanding that my background is not Perl but other Win32 stuff,
and hence it's ironic that I was the first to post a HOWTO on Win32
ports (www.openhandhome.com/howtosa.html)...my comments below may be
inadvertently ignorant! Please forgive!
No particular order of priority:
1. SPAMD may be problematic
Both because "fork" is iffish on Win32, and because SYSLOG has to be
converted to Win32::EventLog. I've got some info on that in the
2. Base install of 2.50 mostly works. I have a draft HOWTO I wrote a
few months ago, that I'll dust off and check against the current.
It expects to build spamc from scratch. As most Win32 users do NOT
have a C compiler as a semi-standard setup., I'd recommend we provide
prebuilt binaries, with appropriate makefile and source in a subdir.
Installing rules always seems to get mucked up by various unixy
things. Hence, I've tended to comment this out and have users
manually replace it. It also made a new section in my draft HOWTO for
2.50 necessary on CLEAN upgrades.
3. Plugins (tend to assign low priority to this)
a. Razor 1 - sort of works, but because it relies on ALARM is
b. Razor 2 would probably have the same issue, but as it relies on
compiling stuff I couldn't get to compile on my lowly Win32 box, I
never got that far.
c. Pyzor seems to have same issues as Razor 1.
d. DCC again would need to be specially compiled for Win32
4. I am perfectly happy to release my (ugly, VB) code for SACONF [gui
spamassassin configuration) (which is slightly oldish) to this
project under dual GPL/PAL if people think it would be helpful.
5. Databases - these work so far, but I wonder how likely this is to
break under Bayes and newer stuff that is database reliant.
6. I find some aspects of layered user config files confusing with
Win32, but admit I haven't spent a lot of time trying to sort it out.
7. SPAMPROXYD. Havent tested this in a long time. At the time there
were two issues
a. The Net::SMTP::Server didn't work too well from PPM or CPAN and
had to be downloaded/installed directly. Not a biggie, but...
b. There was a bug (or so it looked): (excerpted from HOWTO)
"You can run Spamproxyd by typing:
spamproxyd listenaddr:port destaddr:port mailaddress
I did find one problem: Unless I manually set "my $spamddr" to a
value, it never seems to see the argument, and complains about the
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.