Re: [Mailman-Developers] Future of pipermail?

chuqui@plaidworks.com said:
Does mailman have to an an integrated archiver? Isn't this another variant of the "integrated MTA" discussion?
Maybe. There are times when I would really love to have archive message id or URL references in messages for example - ie when a particularly great pearl of wisdom comes from you folks which I want to reference on another list it would be great if I could easily grab an archive reference from the original message (as opposed to going to the archives and hunting out the original message then copying the URL) to send on.
I'd prefer, honestly, splitting out pipermail (or it's successor) into a separately tracked project, and building a standard interface that will work with it and with other archivers, like Mhonarc. That way, a separate team can be built to work on Pipermail, and releases of each piece don't have to be wedged into the same schedule, and you simplify the complexity of each project to improve focus....
However my general gut feel does strongly agree with Chuq here.
I would also be keen on the idea of a MIME reprocessor front-ended onto Mailman - sort of like demime but more controllable, and particularly with the ability to strip unwanted MIME from the message but save the parts onto the MLM server, adding URLs to the processed message to allow the extracted parts to be retrieved. This is not really the archiver function, but has some ideas in common.
Nigel.

At 9:20 AM +0000 11/17/00, Nigel Metheringham wrote:
chuqui@plaidworks.com said:
Does mailman have to an an integrated archiver? Isn't this another variant of the "integrated MTA" discussion?
Maybe. There are times when I would really love to have archive message id or URL references in messages for example
But does that imply it has to be integrated into mailman? Or just available.
The only reason I see for it to be fully integrated is if we want to add a header pointing to the article in the archive -- that would require archive processing during delivery. Other than that, it can be post -processed, so it wouldn't need to be part of hte main MLM code, it simply has to interface with it. That'd allow both pieces to be managed separately.
I would also be keen on the idea of a MIME reprocessor front-ended onto Mailman - sort of like demime but more controllable,
I'm toying with that, actually.
participants (2)
-
Chuq Von Rospach
-
Nigel Metheringham