I tried this as a sink on an exchange box and it doesn't fork. It processes one emai at a time. It can take from 15-30 seconds per email depending on the size and speed of your system. So, it didn't take vary long before the incoming queue was getting backed up. I ended up disabling the sing and flushing the queue 2-3 times a day. Better to run it on a linux or bsd gateway box infront of your windows based email server.
Eric >> I am wondering if anyone running Windows and SA has tried the new >> ActivePerl with 3.1.1? > > Now running ActivePerl 5.8.8.816 with SA 3.1.1 on Windows Server 2003. > My SpamAssassin won't lint... Ugh. > > "EADDRINUSE" is not exported by the Errno module > Can't continue after import errors at > C:\Perl\site\lib/Mail/SpamAssassin/DnsResolver.pm line 45 > BEGIN failed--compilation aborted at > C:\Perl\site\lib/Mail/SpamAssassin/DnsResolver.pm line 45. > Compilation failed in require at C:\Perl\site\lib/Mail/SpamAssassin.pm > line 75. > BEGIN failed--compilation aborted at > C:\Perl\site\lib/Mail/SpamAssassin.pm line 75. > Compilation failed in require at spamassassin line 78. > BEGIN failed--compilation aborted at spamassassin line 78. > > > It doesn't have the same problem on Windows XP... Wonder what the > difference is? I used the same install procedure on both. The funny part > is that the module interface still works fine and it's running correctly > under CGPSA, so it works, but doesn't --lint. Go figure. I'll do some > more digging. Anyone else have an idea where to look? > > Bret > > > >
