On Tue, 12 Jul 2005, CaT wrote:
> On Mon, Jul 11, 2005 at 01:58:36PM +0200, Santiago Vila wrote:
> > severity 317598 normal
> > thanks
> >
> > I reiterate that I can't take this report seriously unless you tell me
> > a way to reproduce it. In particular, you didn't tell me about your
>
> Have we
On Mon, Jul 11, 2005 at 01:58:36PM +0200, Santiago Vila wrote:
> severity 317598 normal
> thanks
>
> I reiterate that I can't take this report seriously unless you tell me
> a way to reproduce it. In particular, you didn't tell me about your
Have we spoken about this previously? I had a look at t
severity 317598 normal
thanks
I reiterate that I can't take this report seriously unless you tell me
a way to reproduce it. In particular, you didn't tell me about your
procmail.log file at all.
I'm downgrading the severity to normal, as I don't want to see a
non-reproducible bug in the periodica
On Sun, 10 Jul 2005, CaT wrote:
> Package: procmail
> Version: 3.22-11
> Severity: critical
> Justification: causes serious data loss
Please don't just show me your logs. I need a way to *reproduce* the
data loss, including a minimal .procmailrc showing such behaviour,
and an exact description of
On Sun, Jul 10, 2005 at 10:55:03AM +1000, CaT wrote:
> Package: procmail
> Version: 3.22-11
> Severity: critical
> Justification: causes serious data loss
>
>
> Tonight my /var/mail partition ran out of disk space (again) and
> procmail continued to allow delivery (again) despite of this. It
> oc
Package: procmail
Version: 3.22-11
Severity: critical
Justification: causes serious data loss
Tonight my /var/mail partition ran out of disk space (again) and
procmail continued to allow delivery (again) despite of this. It
occasionally rejected messages via return code 75:
Jul 10 10:35:09 their
6 matches
Mail list logo