[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#856067: marked as done (unblock: amavisd-new/1:2.10.1-4)

Your message dated Mon, 06 Mar 2017 08:55:03 +0000
with message-id <E1ckoQ3-0007Df-RN@respighi.debian.org>
and subject line unblock amavisd-new
has caused the Debian Bug report #856067,
regarding unblock: amavisd-new/1:2.10.1-4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
856067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856067
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Request dialog concerning amavisd-new situation.

amavisd-new has a release critical bug. #847311. The justification given
was "causes non-serious data loss" presumably because emails were being
incorrectly classified as SPAM. This only happened for people using the
mysql functionality which is an optional feature of amavisd-new. I do
not agree this makes it RC, however I have not tried to change it,
however an earlier attempt to change it to important resulted it in
being changed back to grave.

The bug is not a bug in amavisd-new. It is a bug in libdbd-mysql-perl.
I have opened a bug #856064 (grave). There is an upstream patch:

https://github.com/perl5-dbi/DBD-mysql/pull/102

It has been proven to fix the problem:

https://github.com/perl5-dbi/DBD-mysql/issues/78#issuecomment-282270330

So question is, where do we proceed from here? I guess first step would
be to wait for a response for #856064.

I am also guessing tha since amavisd-new has already been removed from
testing, there is no chance of getting it back in. If this is the case,
is there any chance of getting it back into a future point release?

I believe amavisd-new is a somewhat popular package, not including it in
the next release is going to inconvenience a large number of people.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Unblocked amavisd-new.

--- End Message ---
Reply to: