Matt Kettler <mkettler_sa <at> comcast.net> writes: > > martin wrote: > > using spamassassin-3.0.4-2, spamass-milter-0.3.0, clamav-0.88, > > clamav-milter-0.88, sendmail-8.13.1 under FC3. All parts seem work fine, but > > found some mails had dropped to mbox directly and seem not scanned > > by sa (X-Spam header had not added, spam.log can't found related message). > > > The system (P4,512M ram) seem not too busy. > How big were the messages? By default most tools bypass scanning of > large messages because they bog SA down, and rarely turn out to be spam. > By default, spamc does this at 250k, and spamass-milter probably has a > similar threshold. thx info, that seem the cause, becoz the email att. with a image around 250k in size. just wonder, can this parameter tuneable from config file? And SA had any ruleset to due with a image spamming email?
> > another problem is, i found that at spam.log, some message id of > > message (e.g "processing message <unknown> for spamass:59") show "unknown" > > rather than the related msgid at maillog. > Check the timestamp in the Received: header against the timestamp of the > log message? but without the msgid info, how can i related mail at maillog? coz the spam.log just log spamc its pid, connection and scoring info. I just found the msgid info related to maillog. thx again
