Re: Call for testing: 2.0.0 is close to the doors

Hello Ron,

Chris recommendend your archiver to me and I really like the idea. The piper=
mail-style output is a lot less clunky and much faster than the modern repla=
cements. Especially for threads.=20

This should=E2=80=99t be too hard to implement, maybe you=E2=80=99ll have to=
 answer some questions when I try to set up the archiver first.=20

Maybe I cook something up on my fork in the near future.=20

Cheers,

Jona M=C3=BCller

> On 30. Mar 2026, at 03:51, Ron Guerin <[email protected]> wrote:
> =EF=BB=BFOn 3/29/26 4:26 AM, Baptiste Daroussin wrote:
>> Hello Everyone
>> In 2022, I took over the maintenance of mlmmj which I am using for the Fre=
eBSD mailing lists and more.
>=20
> mlmmj seems in a practical sense, to be "the last man standing", when it c=
omes to mailing list managers.  I've recently come over, as a refugee from M=
ailman 2, in despair of Mailman 3.  The SDLU successor to the old SPAM-L lis=
t recently shut down as it was running on Mailman 2, and I suspect there wil=
l be more of these this year as continuing to operate Python 2 things become=
s increasingly problematic.
>=20
> I offer my thanks to you for taking over mlmmj.
>=20
>> I am close to have delivered all the features I intended to add as such I=
 would like to stamp it with naming the next release: 2.0.0!
>=20
> Apologies if this is the wrong place to make a request.
>=20
> (And I realize it's too late for 2.0.0.)
>=20
> I would like to have a hook available, so that when mlmmj places a message=
 in the archive, it allows me to run some other program, specifically in my c=
ase, a web archiver script I've developed to produce web pages substantially=
 similar to those produced by Pipermail from GNU Mailman 2.  I would offer a=
 patch if I were capable of producing one. Having not written a line of C in=
 35 years, I haven't been able to do so.
>=20
> Vive la mlmmj!
>=20
> - Ron