spamassassin-dev September 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6633] new functionality: limiting bayes e

[Bug 6633] new functionality: limiting bayes engine to mail not larger than...

From: <bugzilla-daemon_at_nospam>
Date: Wed Sep 21 2011 - 09:44:54 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633

--- Comment #7 from AXB <axb.lists@gmail.com> 2011-09-21 09:44:54 UTC ---
(In reply to comment #6)
> Yes, i know this messages is huge. I've to scan such big emails (second option
> is to use diffrent spamd for big emails but it's not always possible). I'm
> using postgresql-9.0 as backend for bayes.

ok.. *possible* bottleneck #1 : SQL
if this not a central Bayes DB for many machines, pls try local SDBM as bayes
backend

for example:

bayes_path /var/bayes/bayes
# EXAMPLE ONLY!!!!#
bayes_file_mode 0777
##
bayes_store_module Mail::SpamAssassin::BayesStore::SDBM

make sure you don't auto expire bayes - this can also help the bottleneck.

> Please notice: spamd scans this email through ~2 minutes then idles but spamc
> doesn't return results of scan. Spamc timeouts after 10 minutes. This is main
> problem for me now because exim connects to spamd and waits for report, doesn't
> receive results then timeouts.

spamc cannot timeout after ten minutes when the default is 5

http://spamassassin.apache.org/full/3.3.x/doc/spamc.txt

-t *timeout*, --timeout=*timeout*
        Set the timeout for spamc-to-spamd communications (default: 600, 0
        disables). If spamd takes longer than this many seconds to reply to
        a message, spamc will abort the connection and treat this as a
        failure to connect; in other words the message will be returned
        unprocessed.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.