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. > 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. > so, how can i sure that message had been scanned by spamassassin and found > related record from spam.log to maillog? thx > Check the timestamp in the Received: header against the timestamp of the log message? > > > >
