On Tue, Feb 21, 2006 at 02:22:19PM +0000, Casey Allen Shobe wrote:
> On Wednesday 15 February 2006 05:47, AJ Prowant wrote:
> > Setting MaxMessageSize in dspam.conf to something like 2mb should
> > atleast let you get out of the house.
> >
> > MaxMessageSize 2097152
>
> Cheers for that, I completely overlooked it before. I've actually put a
> Nagios event handler in place which kills off dspam processes when it sees it
> eating CPU. I haven't seen it act up since the last time though, and hope I
> don't again. I've just upgraded to 3.6.4, and am using MaxMessageSize now
> (with a 4MB limit).
>
> The "don't bother with attachments" would be quite handy indeed. :)
Personally, I think people should review their needs in terms of what
size they should use.
In my collection of spam, the largest I can find is 87KB.
You *might* save some CPU (quite a bit :) by not scanning messages
over a specific size, and each 'users' size might be different.
'user' in this case means the system as a whole.
For me - I set it to 256KB.
-- Mike Horwath, reachable via drechsau@Geeks.ORGReceived on Sat Feb 25 13:49:27 2006
This archive was generated by hypermail 2.1.8 : Mon Feb 27 2006 - 00:00:02 EST