SB> Yes, SA does use a lot of memory - about 20MB, but the amount of memory SB> doesn't really change based on the message size, which was why I was SB> expressing surprise. It takes *longer* to scan a larger message, but SB> compared to the static overhead of 18MB for the libraries and regex's the SB> size of the message is insignificant, at least up to 256KB....
Well, maybe it's a time out problem, then. The error message is "Out of Memory!" .... but bottom line, it was caused by large files. I really don't worry about it very much, because I pre-filter for common worms before the email ever reaches SA, and I simply wrote a post-SA filter to run some tests on the unfiltered files with attachments, so basically I had a problem and I fixed it. Again, it probably really depends on the environment. There's a lot happening on the particular server where I run SA, and the memory errors probably coincide with other events using up server processes. -Abigail ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
