Re: [Mailman-Developers] Requirements for a new archiver

Barry Warsaw wrote: trim FWIW, I think all this competition in replacement archives is a good thing. What I really want though, is a standard interface/API/protocol between Mailman and the archives. Here's why: trim Yes!!! An API lets us have choices. What does it take to get the standard inte

Re: [Mailman-Developers] "@" in mail **text** gets replaced inarchives

FWIW: We have Mailman archive recent email and then use MHonArc to build our 'permanent' archives. I'm happy as long as I can get a copy of the original email. I may put up an edited version of some messages but keep the original - just in case. Gary John A. Martin wrote: trim I am not as con

Re: [Mailman-Developers] Way into the future -- XML and Mailman?

I poked around with XMLizing email a while ago. I did a bit of testing with using J2EE's JavaMail to read email and turning headers and the various mime parts into xml. I also did a bit with making MHonArc XHTML. My feel was that if email were XML, it would simplify parsing and that software that

Re: [Mailman-Developers] The Life Cycle of Mailing Lists.

My wife includes it in the unsubscribe messages. Gary Chuq Von Rospach wrote: a friend passed this to me today. I thought some of you might find it interesting. ___ Mailman-Developers