On 05/04, smallrat wrote:
> I already solved that problem. It was really in the memory. So thanks for
> help.
How did you solve it?
It's probably appropriate (and more productive) to post any questions
about mass-check to the dev list.
Will you be sharing your new rules with us?
--
"If you wa
an anyway,
> that could be deleted (or, if you still want the effects of SA scanning
> the MIME attachment headers, that could have the majority of their base64
> removed)?
>
I already solved that problem. It was really in the memory. So thanks for
help.
--
View this message in conte
On Tue, 3 May 2011, smallrat wrote:
John Hardin wrote:
Trivial answer: don't put messages that large into your corpus.
Are you sure it's frozen? What's your CPU usage? How long did you wait?
Did your box start swapping?
If you're going to feed messages >1.5MB or so to SA, assuming your box h
upose it can be caused by this, can't it?
--
View this message in context:
http://old.nabble.com/issue-with-mass-check---reuse---all-tp31530043p31534074.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
On Tue, 3 May 2011, smallrat wrote:
I try to mass-check my email database, with the parameters --reuse --all.
But there is an issue, when it comes to the big emails (size more than 15
MB), the computer simply freezes and the mass-check stops.
Trivial answer: don't put messages that large into
://old.nabble.com/issue-with-mass-check---reuse---all-tp31530043p31530043.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.