2013-05-27 Michi asked me to set up a discussion mailing list for him. Boris mentioned that discussions between two persons are likely useful for others too. [0] I was already thinking about reviving the discussion list, we once had. In summary: We need mailing lists! Fine, this matches well with my plans to rework the mailing list setup of my server. Currently, I use minimalist, but it's not smooth enough. I want truly simple mailing list support. Thus, I've worked on a mailing list manager that bases on mmh, already weeks ago. Today, I've continued to do so. I't only about 250 SLOC in sh plus 20 SLOC in sh for the archiving backend! Of course, it is not finished yet and will likely grow a bit more, but this is a truly small amount of code, even compared to the 1500 Perl-SLOC of minimalist. Installing new lists should require no more than adding aliases to the MTA (list, -request, -owner) and creating a list directory with only a plain-text file with the list members. Config files and text templates are optional. The prototype is mostly working as expected but it needs more testing and some securing. I am highly motivated to finish it quickly to be able to use it for the mailing lists as soon as possible. While working with the mmh tools, I disovered a programm abort that wasn't really necessary. I've fixed it. I should definitely spend more time working on mmh. While we're talking about mmh, it's tools are not really tools in the more narrow sense: They don't behave the same everytime nor can they be used right out of the box. Actually, they are pretty much developed with focus on interactive use. (Well, ``pretty much'' in contrast to tr, wc, cut, etc of course. They are still very toolish in comparison to many other programs.) What I am talking about is their demand for a profile. You cannot use most of the mmh tools without running mmh(1) first to create ~/.mmh/profile and a mail storage somewhere. That's bad. [0] https://entropia.de/~krt/2013-05-27T21:41:18.00Z.txt http://marmaro.de/lue/ markus schnalke