[Pkg-mailman-hackers] Bug#746592: (no subject)

[Thorsten Glaser]

On Thu, 8 May 2014, juichenieder-debbie at yahoo.co.uk wrote:

> As I explained in the original report, this has been fixed
> (not-idealy, but workable) in testing

Ah, okay. In that case, this will of course not result in such thing.

But on the other hand, this is no security issue, so mailman in
stable will not be updated. Backporting the current one might
work, though; it “just” needs someone experienced to do the work.

> 1) (When) will 2.1.18 enter ftp?

When someone does the work. I have no idea if Thijs has any
plans related to this. I have few time unfortunately, and
supporting broken services such as Yahoo’s is definitely not
on my priority list (in fact, my own mailserver blocks incoming
messages from them), although I may be able to allocate some
$dayjob time to it eventually. But that’ll take a while.

(In fact, there’s still more of our current “fork” of the
Debian mailman package that needs to be fed back into Debian,
*and* some issues with it to resolve. I really need to manage
to allocate some time towards working with mailman.)

> 2) Depending on the answer to 1), should a backport request go in now

A request to whom? ;-) (Although, our mailman server does
run stable, so when/if I get the time, the package will,
most likely, run on wheezy as-is, so backporting it would
be trivial, using backports.debian.org mechanism.)

> for 2.1.16, or wait for 2.1.18?  As the reworking of the workaround

Backports are only possible for versions in testing, which
will be frozen in a few months, so if it’s not before that…

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg