Geraint Edwards wrote:
> We have exim-4.52 too (exim ports on FreeBSD 4 and 5). We're now
> getting timeouts since upgrading to spamassassin 3.1.0. Didn't
I also had scantimes above 60s after upgrading. I played a little bit
with the database (compressing etc., the usually ), suddenly it dropped
> notice these timeouts with 3.0.x (checked several months of logs,
> too). It seems restricted to large e-mails here (we don't get so
> many of these) - the following example is a 5.7MB spam mail.
I have a size limit of 200k for spam scanning. Scanning large always
takes ages.
> 2) exim seems to timeout waiting for spamd after 2mins (i.e. while
> in the first "warn ... spam = spamu:true" statement) but
> both exim and SA carry on(!), exim appearing to fall
> through to the next "spam = spamu:true" line (because of
to avoid this, I have only one spam = nobody:true/defer_ok (which sets
acl_m variables I need later in the system filter), all the other spam
ACL stanzas use the $spam_ variables. If the spam scanning failed or
didn't happen (size limit, whitelisting), they are empty.
> I suspect increasing SA's 5min timeout will not resolve exim's
> apparent 2min timeout, so that might have to be increased too.
Would make more sense to decrease the spamd timeout to 2min.
