>If so, I think that it's a waste of memory; it would imVHo be a
better idea setting up a common, shared "pool" containing all
those data and allow all the threads to access it; such a thing
All data that could be shared are shared between the threads. But there
are some data structures that coul
Contrary to your results, I tested 14.02 on my W2K3 server, and it
died with the IO Poll error within 5 minutes, however it was the
Main_Thread that died, not one of the worker threads. It was OK
running under low "Sunday night" load and ran without problems, but
when I ran it under Monday morn
>1.5.1 RC12.1 still has problems with email interface for analyze-spam
>which I reported before.
Sorry, I did not see a report.
>
>
>Also report spam appears to process senders signatures as if they
>were part of the spam.
1.5.1 does not recognize "sender signatures". There is no difference
t
1.5.1 RC12.1 still has problems with email interface for analyze-spam
which I reported before. Mail to analyze-spam does not properly
complete causing mail clients to timeout and not complete the rest of
the sending queue. SInce the queue is not complete the request for
analyze-spam is repeate
As for subject I downloaded the above version and
gave it a spin; the platform is:
win2k3, Intel Xeon 2.8 Ghz, 2Gb RAM
Active Perl 5.8.8; all needed modules installed (or at least
the ASSP logged an "all ok"); ASSP running as a service
Started up the ASSP, it took some seconds to startup
all t
The technical minimum is one thread, but I've never tried this. This will
cause to many interrupts - I recommend a minimum of three workers! Using
less workers will result in less memory usage, the CPU load will be the
same. Using to less workers will cause to many interrupts to the workers
and
