Notes below... > -----Original Message----- > From: Bret Miller [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 28, 2006 8:51 AM > To: users@spamassassin.apache.org > Subject: RE: Any windows users try the new Active Perl with SA? > > > 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,
Whose sink are you running? My sink processes in no more than 5 seconds on a P4 with adequate memory.. And similar results (no more than 6-7 seconds) on a underpowered P3. Truth be told, I only upgraded to the P4 because I was paging constantly with my wimpy P3 (maxxed at 768MB physical RAM) > 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. > > That's the Exchange Sink's fault, not SA's. I use SA with > CGPSA on CommuniGate Pro and it forks just fine on Windows. > Convincing the Sink author to not single-thread the requests > might be the hardest part... Exchange Event sinks by nature of the model are single-threaded.. In order to get a multi-threaded Exchange sink, you have to write some serious C code (and I'm not up for that task), and haven't found anyone that is. And even then, I'm not sure if it's possible, because my research into that aspect of it was over 2 years ago, and iffy at best on that particular area since I couldn't write that C-code to begin with. Steven > It's not very efficient to fork on Windows, but it's better > than single-threading the requests if you've got the hardware > to handle multiple SA processes. > > Bret > > > > >> 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? > > > > >
