severity 375988 important
thanks
* Santiago Vila ([EMAIL PROTECTED]) [061208 16:42]:
> I did not manage to make procmail to crash, but using top I have seen
> *spamassassin* to use very large amounts of memory (more than the
> 512MB I have) and finally crash. (Note: Deactivating swap helps :-)
>
severity 375988 serious
clone 375988 -1
tags 375988 help
reassign -1 spamassassin
retitle -1 spamassassin needs more than 512MB to process innocent 2.5MB email
found -1 3.1.7-1
thanks
In this report, the submitter says that some messages make procmail to crash.
He also says to be using spamassassi
On Thu, 29 Jun 2006, saf wrote:
> Package: procmail
> Version: 3.22-11
> Severity: grave
> Justification: renders package unusable
>
> When I check my kernel messages with the dmesg command I see this
> errors some times:
> procmail[6099]: segfault at rip 2adc5570
> rsp 0
On Fri, 30 Jun 2006, saf wrote:
> procmail recrashed with Segmentation fault on my machine.
> I wrote a wrapper to detect when procmail fails, and then I saved
> the data to try to reproduce the error. Now I sent you a dump
> of my mail which has made procmail to crash.
>
> Here is the output of
severity 375988 normal
thanks
On Thu, 29 Jun 2006, saf wrote:
> Package: procmail
> Version: 3.22-11
> Severity: grave
> Justification: renders package unusable
>
> When I check my kernel messages with the dmesg command I see this errors some
> times:
> procmail[6099]: segfault at 00
Package: procmail
Version: 3.22-11
Severity: grave
Justification: renders package unusable
When I check my kernel messages with the dmesg command I see this errors some
times:
procmail[6099]: segfault at rip 2adc5570 rsp
7f8c6ac8 error 4
procmail[6106]: segfault
6 matches
Mail list logo
