Bug#746592: [Pkg-mailman-hackers] Bug#746592: Upgrade/backport mailman as package has been made unusable by DMARC
Hi Faidon, Yes, my apologies, I should have worded my initial post clearer along the lines of what you have just written. I still feel relatively new to Debian, but getting there. I don't seem to have received an email about your post, but luckily I checked back. To move this along, I enclose information on the current status received from Thorsten to give you an idea of current status. Many thanks, and hopefully one day I'll have the skills to do something like this myself :). Best, Jack PM From Thorsten Glaser 8 May: 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.)
Bug#746592: Upgrade/backport mailman as package has been made unusable by DMARC
On Thu, May 01, 2014 at 07:21:27PM +0100, juichenieder-deb...@yahoo.co.uk wrote: http://wiki.list.org/display/DEV/DMARC The way I see it, this bug report is for two different things: 1) Package a new upstream release. The current one is 2.1.18, a minor update to 2.1.16 (released on October, 2013; followed by 2.1.17 in the meantime) that unstable currently has. 2.1.18 provides a better solution to the DMARC problem, a problem that affects the vast majority of the mailman users running public mailing lists (as they're bound to have e.g. Yahoo! subscribers) and is going to affect even more of them as the time passes. The package update seems trivial and the fact that it hasn't been done since November 2013 (2.1.17 release date) suggests to me to that the package is poorly maintained. Dear maintainer, have you thought about RFHing the package? Would you be okay with me NMUing the package outside the regular NMU rules to update to a new upstream release? 2) A backport of the current jessie version to wheezy-backports. As far as I know, it's highly unusual for backport requests to be tracked in the main BTS, but if the maintainer doesn't mind, I won't :) Anyone can do the backport, as long the maintainer is okay with it. I'd be happy to do it, but I'd like to see (1) done first as to not waste my time with backporting an 9-month old piece of software. Thanks, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746592: [Pkg-mailman-hackers] Bug#746592: Upgrade/backport mailman as package has been made unusable by DMARC
severity 746592 important thanks On Thu, 1 May 2014, juichenieder-deb...@yahoo.co.uk wrote: The introduction of DMARC by certain email-clients has severely crippled the use of mailman, making the current version in wheezy, virtually unusable Only for Yahoo users, certainly not “grave”. bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746592: Upgrade/backport mailman as package has been made unusable by DMARC
Package: mailman Version: 1:2.1.15-1 Severity: grave The introduction of DMARC by certain email-clients has severely crippled the use of mailman, making the current version in wheezy, virtually unusablewith numerous accounts getting critical bounced with a single email. See the following link for more information. http://wiki.list.org/display/DEV/DMARC To solve this problem for users of debian-stable, I suggest adding a more recent version of mailman (as noted within the link) to backports, either: a) 2.1.16-2 (the easiest as it already exists in jessie) or b) 2.1.18 as this gives a better fix of the problem according to the above link. -- System Information: Debian Release: wheezy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
