Your message dated Thu, 25 Jul 2013 14:35:10 +0300
with message-id <20130725113510.gd4...@kludge.henri.nerv.fi>
and subject line update
has caused the Debian Bug report #631537,
regarding mailscanner: broken by perl tainting update
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 ow...@bugs.debian.org
immediately.)
--
631537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailscanner
Severity: grave
Justification: service does not start up
----- Forwarded message from Dominic Hargreaves <d...@earth.li> -----
Date: Wed, 22 Jun 2011 22:26:48 +0100
From: Dominic Hargreaves <d...@earth.li>
To: Junior Gamez Aguilera <junior.ga...@bucanero.com.cu>
Cc: p...@packages.debian.org, Florian Weimer <f...@deneb.enyo.de>,
debian-secur...@lists.debian.org
Subject: Re: [SECURITY] [DSA 2265-1] perl security update
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED
autolearn=unavailable version=3.3.1
X-Urchin-Spam-Score-Int: -41
[adding perl maintainers to CC]
On Wed, Jun 22, 2011 at 02:49:02PM -0400, Junior Gamez Aguilera wrote:
> after applying this upgrade mailscanner stop working, it start to enter
> in a continuous cicle of restart. please could you verify this?
> I have to go back to previous version in order to put mailscanner to work.
This looks like mailscanner is indeed broken by the tainting fixes;
see the thread starting at
<http://lists.mailscanner.info/pipermail/mailscanner/2011-April/097813.html>
Unfortunately mailscanner is orphaned so there was not much chance
of test coverage of mailscanner in unstable.
Can you confirm that the errors on that thread match what you're seeing?
Unfortunately there does not yet appear to be any sign of a real fix
upstream, but there are a couple of possible workarounds mentioned.
----- End forwarded message -----
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--- End Message ---
--- Begin Message ---
Squeeze is not affected.
---
Henri Salo
signature.asc
Description: Digital signature
--- End Message ---
