Mailman 3 March 1998 - Mailman-Developers

Next Release
by W T Hewitt March 28, 1998

March 28, 1998

On Tuesday, March 24, 1998 4:46 PM, Ken Manheimer [SMTP:klm@cnri.reston.va.us] wrote: > On Tue, 24 Mar 1998, W T Hewitt wrote: > > > I got the latest versions of mailman from ftp.python.org: > > > > klm.p1 > > mailman-1.0b1.tar.gz > > > > unpacked. When I tried to apply the patches I gave a significant number > > of rejects!! > > The patches should apply with no problems if you run the patch from the > same directory where you untarred the mailman package - ie, in the > directory where the single 'mailman' dir was created. I finally figured out the problem. I'd ftp'ed the file to a PC then to an SGI O2, and the klm.p1 had extraneous <CR>s in it! I've been using mailman on an SGI, and my problems/suggestions/fixes for the next release. I'm willing to do some of them if somebody will tell me which ones to do: 1) in mailman/src/*.c put UID and GID in a .h file so I Only need to edit one file 2) Make /home/mailman a configuration variable 3) Make the logging files /tmp* world writeable (when debugging I had problems running as nobody and mailman) and make the names consistent 4) Use HTMLgen for creating HTML 5) On SGI you can't add aliases to programs in /etc/aliases You do it through a .forward file for /home/mailman All names in /etc/aliases are therefore aliased to mailman, and I have a mailwrapper script that does what aliases used to do. 6) Add archive more frequently (e.g., daily, hourly, now) to mm_archive volume_frequency I have a fix for this 7) crontab on SGI complains about blank lines in crontab.in 8) Put all the files associated with a list in one subdirectory, that is independent of mailman code. Best wishes Terry W T Hewitt Manchester Visualization Centre Telephone: +44 161 275 6095 Manchester Computing Fax: +44 161 275 6800 University of Manchester Email: w.t.hewtt(a)mcc.ac.uk Manchester M13 9PL URL: http://info.mcc.ac.uk/MVC United Kingdom (Formerly Computer Graphics Unit)

3 2

Re: [Mailman-developers] Help please.
by Janne Sinkkonen March 24, 1998

March 24, 1998

Ken Manheimer <klm(a)cnri.reston.va.us> writes: > The patches should apply with no problems if you run the patch from the > same directory where you untarred the mailman package - ie, in the > directory where the single 'mailman' dir was created. The patches installed cleanly and I was even able to create a list. mm_cfg.py or some such however lacked a lot of DEFAULTs and I was never able to subscribe to a test list. I tracked it down to the cgi module returning an empty FieldStorage to cgi/subscribe and the gave up. There was no signs of problems in server (apache) logs, and I did change the UIDs and GIDs in wrapper code. Also, the scripts in cgi/ have their suid bit set, although I guess that's not necessary, at least not in Linux where suid scripts do not suid at all. Just FYI. -- Janne Sinkkonen <janne(a)iki.fi> <URL: http://www.iki.fi/~janne/ >

1 0

Help please.
by W T Hewitt March 24, 1998

March 24, 1998

I got the latest versions of mailman from ftp.python.org: klm.p1 mailman-1.0b1.tar.gz unpacked. When I tried to apply the patches I gave a significant number of rejects!! Would somebody please email me the latest version, or email where it is, or perhaps, let me know the trick to doing the patches.... -- Best wishes Terry W T Hewitt Telephone: +44 161 275 6095 Manchester Visualization Centre Fax: +44 161 275 6800 Manchester Computing Electronic mail: w.t.hewitt(a)mcc.ac.uk University of Manchester http://www.man.ac.uk/MVC Manchester M13 9PL United Kingdom (formerly the Computer Graphics Unit)

2 1

Re: [Matrix-SIG] Testing transition to mailman list processor
by Ken Manheimer March 17, 1998

March 17, 1998

On Tue, 17 Mar 1998, Charles G Waldman wrote: > Ken Manheimer writes: > > The Matrix-SIG mailing list has just been migrated to mailman, a > > python-based maillist management system. > > Hi Ken - this is off-topic for the Matrix-SIG - more of a "mailman" > question. I've been meaning to mention this to someone, I'm not sure > who the maintainer is of the Mailman package - is it you? Anyway, > your message provides me with the excuse to write you.... :-) At the moment i'm carrying the ball, basically in order to get mailman in full gear at python.org. As you may know, we're using a version that's the most recent one recovered after loss of the server where john viega was developing and running mailman, and basically several months of work were lost. John is around and interested in continuing to work w/mailman, but deep in a grad school thesis, so it'll a little while before he gets to concentrate on it again. However, his intention is to come back to it, especially now that several people have also expressed interest. Towards the end of collaborating on mailman, we've set up a mailman-developers(a)python.org maillist - see http://www.python.org/mailman/listinfo/mailman-developers . I recommend joining that list, right off - it's not yet particularly active (i, for one, am too busy scrambling just to get the system shipshape and in production at this moment to do planning), but i expect we will be using it in earnest as time goes by. In addition, barry warsaw and i are setting up a mechanism (which barry devised) which should enable cvs sharing of the mailman sources across the internet, so we can do widely distributed coordinated development - at least have a convenient way to share modifications. We'll be pursuing this eventually, as time allows. > I recently set up "mailman" at my company, for our internal use. I > grabbed the distribution from python.org as well as the klm patches. > It basically works fine, but I noticed one oddness. > > If there is a line in a mail message that starts with "From ", > preceded by a blank line, the message is truncated in the message > archives. For instance: > > >From where I'm sitting, it looks like a very simple bug to fix. > > (This part of the message won't be archived) > > Has anybody fixed this yet? I don't want to waste time on this if > it has already been fixed. My work on the version here has diverged from the adapted version of pipermail that john was shipping with mailman - andrew kuchling is working here (handily enough!), so we're using a newer version of pipermail. We should be packaging up the whole shebang, pipermail and mailman, for use by others within the next few/several weeks, but in the meanwhile you're sorta on your own re the internal pipermail. That said, i do have an idea about what is needed. I am pretty sure that the line starting with "From " is being treated as the start of a new message, which probably is unarchivable and dropped on the floor, or perhaps getting put at some random place in the archive. The easy thing to do would be to preprocess the messages before they're put in the archive file so lines in the body starting with "From ", and following a blank line, have ">" prepended. I think the place to do this is in mailman/modules/mm_archive.py, Archiver.ArchiveMail(), but you'd have to scope it out a bit. Phew! This may be a bit more than you bargained for. I hope you don't mind that i'm cc'ing this to mailman developers - the info may well be useful for someone else. Ken Manheimer klm(a)python.org

1 0