Package: mailscanner Severity: grave Justification: service does not start up
----- Forwarded message from Dominic Hargreaves <[email protected]> ----- Date: Wed, 22 Jun 2011 22:26:48 +0100 From: Dominic Hargreaves <[email protected]> To: Junior Gamez Aguilera <[email protected]> Cc: [email protected], Florian Weimer <[email protected]>, [email protected] 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) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
