On Mon, 19 Dec 2005, Giovanni Biscuolo wrote:
> * Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2005-12-18 11:56:26 -0200]:
>
> > I cannot duplicate the bug. Plese send me a copy of *all* amavisd-new
> > configuration files, that might help me track down the bug.
>
> All? I use /etc/amavis/am
On Mon, 19 Dec 2005, Steve Langasek wrote:
> Yes, "critical" is the wrong severity, but why is "important" the wrong one?
I will assume you meant "why is 'important' the right one?"
> He seems to be describing a bug that makes amavisd unusable, which would
> still be "grave", yes?
If it was aff
On Sun, Dec 18, 2005 at 11:40:32AM -0200, Henrique de Moraes Holschuh wrote:
> severity 343854 important
> thanks
> On Sun, 18 Dec 2005, Giovanni Biscuolo wrote:
> > Package: amavisd-new
> > Version: 20030616p10-5
> > Severity: critical
> > Justification: breaks the whole system
> As in it destro
On Sun, 18 Dec 2005, Henrique de Moraes Holschuh wrote:
> > Starting amavisd: Insecure dependency in `` while running with -T switch
> > at /usr/share/perl5/Net/Server/Daemonize.pm line 67.
>
> I will check that in chroot later. Meanwhile, you can try the version in
I cannot duplicate the bug.
severity 343854 important
thanks
On Sun, 18 Dec 2005, Giovanni Biscuolo wrote:
> Package: amavisd-new
> Version: 20030616p10-5
> Severity: critical
> Justification: breaks the whole system
As in it destroyed your harddrive, stopped the entire boot process or
somesuch? I seriously doubt so. Don'
Package: amavisd-new
Version: 20030616p10-5
Severity: critical
Justification: breaks the whole system
After an "apt-get upgrade" amavisd-new daemon did not restarted with the
following error:
Starting amavisd: Insecure dependency in `` while running with -T switch at
/usr/share/perl5/Net/Serve
6 matches
Mail list logo
