> Yes, a size limit is *required*. It's very important to limit
> the size of messages scanned by SpamAssassin.
Well, we're limiting the size of emails that spamd sees now, maybe
that will "solve" the problem, and of course it's generally sensibly to
do this, as there isn't really much spam larg
It seems, that for us at least, this is caused by Spamassassin scanning
larger (>1mb) mails containing uuencoded files, without mime attachment
headers
or anything.
But this only seems to happen sometimes or when spamd has been running
for a little while, for if we feed an email that appears to ha
> It randomly happens after an hour or so of use. Next time it happens I
> will try both and send it to the list.
To follow up on the Debian thread with the same problem:
Since seems to happen for several people, during the last days, could it
be that this is not in fact exim/exiscan related, but
> Now we changed from Gentoo based systems (which did not use
> sa > 3.02) to Debian based systems (with 3.03 initially), still using
> the same version/config of exim/exiscan. When used in combination with
> Spamassassin 3.03, we got the said memory problems. Since we downgraded
> to 3.02 yesterda
ith
Spamassassin 3.03, we got the said memory problems. Since we downgraded
to 3.02 yesterday, the problems have disappeared.
--
___
Thomas Jacob
-Softwareentwickler-
IMS Internet-Media-Service GmbH
Bärensteiner Straße 7
01277 Dresden
Fon: +49 351 2112033
Fax: +49 351 21
> I was wondering if anyone had noticed a possible memory leak with SA
3.0.3
> (under Linux/Debian)?
> I upgraded SA from 3.0.2 to 3.0.3 on a Debian server about 7 days ago
and today
> twice the load sky-rocketed followed by the server seizing up. In the
logs were
> lots of 'kernel: __alloc_pag
