On Fri 2026.07.03 at 16:02 +0100, Stuart Henderson wrote: > On 2026/07/02 23:43, Daniel Dickman wrote: > > > > > > On Thu, 2 Jul 2026, Stuart Henderson wrote: > > > > > On 2026/07/01 17:21, Daniel Dickman wrote: > > > > > > mailman2 and mailman3 need to be installed in parallel to manage the > > > migration. when I read your earlier mail "porting mailman 2 to 3" I > > > thought you were talking about porting it to python 3... (there is > > > also https://github.com/jaredmauch/mailman2-python3 which while > > > still labelled 'alpha' is very active). > > > > > > mailman2 and mailman3 are not really comparable anyway, mailman3 is > > > a very different beast and most list admins seem to move to other > > > software (mlmmj etc) rather than to mailman3. > > > > so let me know which route you'd like to go and I'll try to do the work > > for it as time permits. I don't really have a preference as long as we > > remove the Python 2 dep which is my only goal. > > I honestly don't know. Maybe a better option would be to remove it > from ports. Is anyone reading that actually uses mailman from OpenBSD > ports/packages? Any comments?
Yes, and I'm sure djm@ has it on mindrot as well; however installing and/or maintaining it outside of ports is not a huge deal if that needs to happen; however the seeming intent is to remove python2, which would make any install, ports or otherwise, of mailman (2.x) impossible. I do believe mlmmj is a likely migration candidate (though missing stuff), and of course mailman 3.x (but that's an entire beast). If this needs to happen, I think maybe a shot over the bow at the very least. Is mailman 2.x the remaining barrier to removing python2?
