Date: Tue, 28 Apr 2020 22:43:36 -0400 From: Greg Veldman <freebsd@gregv.net> To: Chris <portmaster@bsdforge.com> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: mail/mailman v3? Message-ID: <20200429024336.GT1068@aurora.gregv.net> In-Reply-To: <eec989d7f0083b21b5f2d9f2438261fc@udns.ultimatedns.net> References: <8684b670-d968-7457-231e-720ab8449190@gmx.de> <eec989d7f0083b21b5f2d9f2438261fc@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 28, 2020 at 01:02:14PM -0700, Chris wrote: > It also wouldn't be that difficult to simply modify mailman(2) > to adopt the py3.x language changes. To simply make it work, perhaps not. To make it work well and be reliable... might be more difficult than you think. A large chunk of what a mail handler of any variety does is text processing, and there are significant differences in that area in Python2 vs Python3. E.g. ASCII vs Unicode. You'd likely be opening a Pandora's box of corner cases and workarounds when $STUPIDLY_FORMATTED_MAIL_MESSAGE_OF_THE_HOUR comes through. The effort would probably be better spent enhancing Mailman3, since that's the future of the project anyway. Also, as someone that's been a Mailman site admin on installs of various sizes for about the past 20 years, I'm sort of looking forward to the promises of some of the little quirks of Mailman2 getting some love. ;-) -- Greg Veldman freebsd@gregv.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200429024336.GT1068>