Mike Jackson wrote on Wed, 21 Dec 2005 11:27:08 -0800: > This is totally off the cuff, but would it be possible to install > ActiveState Perl and all the required SpamAssassin Perl modules on a single > workstation, then use something like Inno Setup to bundle them all together > into something that could be deployed with...well, more than one mouse > click, but I'll bet my three-year-old could click through a standard Windows > installer.
I think you still don't have a native win32 API for hooking in then. As I understand you still need to code some perl "stub" that can link in the SA Perl libraries and call those routines for spam scanning. I would also be somewhat "scary" about Perl daemons running on Windows. The only one I have running constantly on a Windows platform is bigsister and although it seems to run just fine I'm not able to stop it the normal way you stop services on Windows, I have to kill them. So, there's still not everything perfect between Perl (yes, ActivePerl) and Windows (Win2k3). I think the proposed solution of putting a MailScanner box in front of the Exchange box is just the best way. Hundreds of shops do it this way. It's also got the advantage that you then can remove the Exchange box from public net (or at least refuse any email with the exception of mail coming from the MailScanner box), so none of the bugs or misconfiguration options Microsoft offers can be exploited. A Linux box in front of mail also offers other better options for spam/virus protection, f.i. greylisting. AFAIK there's no greylisting solution for Exchange or Microsoft SMTP at all. And, last not least, the process of upgrading the MS/SA bits is probably less painless than on Windows. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
