--On Thursday, December 20, 2001 8:21 AM -0800 Steve Eckert wrote:
> At 02:33 PM 12/19/01, Tom Neff wrote:
>> Related: I am somewhat curious to know why MJ2 does nothing to identify
>> itself
>
> You should ask on mj2-dev@csf.colorado.edu, where the developers are.
Well, I had looked at the mj2-dev archives and didn't see the subject
previously brought up. I'm sure I'd get some kind of answer if I did so
myself. :)
Looking at the mj2 install docs showed me that there is a post-install
configuration option you can set:
configshow-merge-append DEFAULT:rfc2369 LISTNAME
that will add all the List-XXXX headers. And you could easily add your own
message_headers value to identify the list processor as mj2, but I was
struck by the fact that this isn't done by default.
> I have a few dozen lists running under Mj2, and for the most part
> it's great. It's not designed by consensus, so unless you get one
> of the two authors to write it for you, changes you suggest or
> actually implement will probably be ignored or removed from CVS.
> (I'm not whining about it - just warning you from experience.)
I have played with a couple of mj2 snapshots over the past 12 months (not
enough to notice that header behavior before!), but I find myself using
Mailman 2 for most of my new lists. It's also a work in progress but it
works out of the box and gives you a lot of functionality.
For anyone else interested, Majordomo 2's home page is at
http://www.hpc.uh.edu/majordomo/
and Mailman's is at
http://www.list.org/
References:
|
|
