[EMAIL PROTECTED], > I'm using amavisd with SA. There is a directive there called > "sa_mail_body_size_limit = undef; # don't waste time on SA if mail is > larger". This was set to 1024*200 which would be 204800k. I've > actually just now set it to undef. Hopefully this is what you meant? I > don't have high hopes. But, we'll see.
> I just wish there was a way to look > at a log to see exactly what SA only is doing besides having to look at > the headers of each message. I've turned the logging on to 5 in amavisd, > but I'm not really sure what to look for as far as SA goes when I look at > the /etc/mail/log/info file. To get SA log written to STDERR when running amavisd, set $sa_debug to 1 (in amavisd.conf) and redirect STDERR to wherever you want when starting amavisd. A simple way to implicitly set $sa_debug=1 and to prevent amavisd from forking (so that stderr remains assigned to a terminal) is: # amavisd debug-sa Examining SA results obtained this way, and comapring this to results from: su vscan -c 'spamassassin -t -D <0.lis' usually suffices to explain why SA when invoked from amavisd behaves differently from when SA is invoked from a command line. Common problems are file permissions/ownerships and different paths. See also: http://www.ijs.si/software/amavisd/#faq-spam Mark
