Mailman 3 August 1999 - Mailman-Developers

Re: [Mailman-Users] Virtual Hosts -- can mailman handle them better?
by Harald Meland 16 Aug '99

16 Aug '99

[Tauren Mills] > I just installed Mailman and love it! Great work! Thanks, glad you like it! > But the /mailman/admin page shows all of the lists on the server > whether they are for that domain or not (unless the lists are not > publicly displayed). Not so good. Yup -- the admin CGI script hasn't been made aware of virtual domains yet. Doing so would probably be quite easy, but I think the current support for virtual domains is a bit shoddy, so I've been putting it off... > Also, if I send an email to clientlist-request(a)clientdomain.com with > the command "help", the response email comes back from > clientlist-request(a)mydomain.com. This can be configured -- see the "Host name this list prefers" setting on the general options page. However, if you have several lists with the same localpart name in different domains (i.e. "foobar(a)dom1.com" and "foobar(a)dom2.org"), you'll have to assign them different Mailman-internal names. I'd like to allow full email addresses as Mailman-internal list names to alleviate this. Then, the site admin could maintain some sort of a webserver<->maildomain cross reference (available to Mailman), and two settings on the general options page would no longer be needed. This would increase the need for easy internal renaming of a list, as domain changes would essentially be a change in the internal list name. Opinions, anyone? > It also has links and email addresses throughout the email that > point to http://www.mydomain.com/mailman/listinfo/clientlist See the "Base URL for Mailman web interface" setting in the general options page. > Lastly, when I execute the "newlist" command, the email that gets > automatically sent to the administrator refers to URLs at > mydomain.com. I would love to have a way to have that email refer > to URLs at clientdomain.com. I'm not aware of any easy solution to that problem. Sure, we could add another option to the "newlist" script for specifying the list's default URL (and another for it's mail domain), but I don't think that's a particularly neat solution... > I'm sure there are all sorts of other little things that could be > done to make Mailman support VirtualHosts better. Are there ways to > deal with these issues? If not, do people think that they are worth > adding to the product? I think better support for virtual hosts (or multiple domains, or whatever this kind of feature really /should/ be called :) are important, so my answer would definitely be yes. -- Harald

3 2

Re: [Mailman-Developers] Bug in Mailman 1.0, newlist
by Harald Meland 15 Aug '99

15 Aug '99

[Christian Tismer] > This is new. In earlier versions, I was allowed to use decorated > email names. True. However, this also allowed site admins to create lists with bogus admin addresses, which could lead to all kinds of more or less subtle trouble -- so I changed things to have Mailman do the same address checks on list admins as is done when considering new subscribers. The right thing to do would probably be to allow (all kinds of) email address comments in both admin and member addresses, but that has it's problems too -- for one, it could make the process of automatically correlating failed delivery reports to subscribed member addresses more difficult. -- Harald

1 0

Virtual Hosts -- can mailman handle them better?
by Tauren Mills 14 Aug '99

14 Aug '99

I just installed Mailman and love it! Great work! However, I have a question about how to make it work better with VirtualHosts. I am hosting numerous client web sites using Apache VirtualHosts. I have been able to make it so that my client's web sites can each bring up the /mailman/listinfo and /mailman/admin pages from their own domain. The /mailman/listinfo page only shows the lists that are part of that domain. Excellent. But the /mailman/admin page shows all of the lists on the server whether they are for that domain or not (unless the lists are not publicly displayed). Not so good. Also, if I send an email to clientlist-request(a)clientdomain.com with the command "help", the response email comes back from clientlist-request(a)mydomain.com. It also has links and email addresses throughout the email that point to http://www.mydomain.com/mailman/listinfo/clientlist and clientlist-admin(a)mydomain.com rather than http://www.clientdomain.com/mailman/listinfo/clientlist and clientlist-admin(a)clientdomain.com. I expect that most of the email-based commands are going have responses that look like they come from the main server rather than the customer's domain, but I'm hoping there is a workaround I'm not aware of. Lastly, when I execute the "newlist" command, the email that gets automatically sent to the administrator refers to URLs at mydomain.com. I would love to have a way to have that email refer to URLs at clientdomain.com. I'm sure there are all sorts of other little things that could be done to make Mailman support VirtualHosts better. Are there ways to deal with these issues? If not, do people think that they are worth adding to the product? Thanks, tauren(a)servlets.net

1 0

Bug in Mailman 1.0, newlist
by Christian Tismer 13 Aug '99

13 Aug '99

Hi Developers, yesterday we upgraded to Mailman 1.0 (thanks to Jimbo Titsler). There is a new bug when creating new lists: I tried to supply this email when creating the pyxie list: [root@starship bin]# ./newlist Enter the name of the list: pyxie Enter the email of the person running the list: Sean Mc Grath <sean(a)digitome.com > Initial pyxie password: Traceback (innermost last): File "./newlist", line 146, in ? raise SystemExit(main(sys.argv)) File "./newlist", line 93, in main newlist.Create(list_name, owner_mail, pw) File "/home/mailman/Mailman/MailList.py", line 720, in Create Utils.ValidateEmail(admin) File "/home/mailman/Mailman/Utils.py", line 296, in ValidateEmail raise Errors.MMHostileAddress Mailman.Errors.MMHostileAddress This is new. In earlier versions, I was allowed to use decorated email names. When I changed to sean(a)digitome.com, it worked as expected. ciao - chris -- Christian Tismer :^) <mailto:tismer@appliedbiometrics.com> Applied Biometrics GmbH : Have a break! Take a ride on Python's Kaiserin-Augusta-Allee 101 : *Starship* http://starship.python.net 10553 Berlin : PGP key -> http://wwwkeys.pgp.net PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF we're tired of banana software - shipped green, ripens at home

1 0

why not make archive into coference
by Andy Heath 12 Aug '99

12 Aug '99

Sorry if this has been asked/suggested before but I can find no trace of it in the archives. My point is this - if it were possible for subscribers to use a web form to post to archives (as well as the usual email method) it would be nice. Users could then choose to use a service as a conference or via email. For myself, there are times when I like to receive everything by email so I don't miss anything and times things are busy enough that I would prefer the conference idea. Often I want to switch from one to the other depending on how busy things are. The point about doing this with the archives is that this functionality is almost there already - it just needs a way of "on-server" posting to be developed. Since this could be limited to subscribers and can only go to the list then it is safe. There are other products that do this sort of thing - I think bscw does, but non so "clean" and simple to use as mailman. Also, the same thing *could* be done with gating to newsgroups but doing so involves much unneccessary complexity. Why has no-one combined the list-server and conference functions before (rhetorical). Please COPY replies to a.k.heath(a)shu.ac.uk as I'm not a subscriber Andy -- ---------------------------- Andy Heath a.k.heath(a)shu.ac.uk

3 2

tech docs?
by Ricardo Kustner 11 Aug '99

11 Aug '99

Hi, is there some information/docs/draft on the structure in the Mailman source code? Since the moderate function is an important feature in the mailinglist we're running, i have a lot of ideas for things that could make the moderate page more powerfull and easy to work with... i can make my own little hacks in the source but i could also offer my patches in here... so i can share my code plus i wont have to put it back everytime i upgrade mailman to a new version ;) one thing i really wanted to fix fast was stripping a lot of the headers you see on the moderated posts page... this is what i made for it (this it my first piece of python ever so it can be probably made much more efficient ;) ) It's just a function a call in admindb.py before it outputs the message on the screen with Preformatted() ideally this could be a config option and one should be able to choose which headers to show in the output. ==== def stripheaders(msg): found = 0 emsg = '' # define which headers to keep headers = ['From:', 'To:', 'Date:', 'Subject:'] for i in string.split(msg, "\012"): if not found: for j in headers: if i[:len(j)] == j: emsg = emsg + i + "\012" # the first empty line means we're done with the headers part if i == "": found = 1 emsg = emsg + "\012" else: # we've had the header part so every line can be added back emsg = emsg + i + "\012" return(emsg) ==== Ricardo. --

1 1

draft end-user doc
by Christopher Kolar 11 Aug '99

11 Aug '99

The first draft of an end user (subscriber) document for Mail Man is available for view at http://www.aurora.edu/~ckolar/mailman. A second document for list managers (own the list, but are not the sysadmin) will be available shortly. Feedback appreciated. --chris

1 0

More on bad dates
by Ron Jarrell 11 Aug '99

11 Aug '99

I found a second date that blows arch out of the water: Date: Tue, 10 Aug 1999 17:39:26 -0400 (EDT) Deleting the (EDT) solves this one.

1 0

Ok, what's wrong with this header...
by Ron Jarrell 11 Aug '99

11 Aug '99

This is related to a bug that's appeared on mailman-users... I'm trying to port old mbox archives into a new mailman list that's replacing and old listproc list. This message is causing arch, while processing my 9704 file, to think it needs to create an 1999-August archive and file it there; shortly there after it explodes... It appears to be the comma before the timezone. When I edited the file by hand to loose the comma suddenly the archive processed fine, and the article made it intot he April 97 archive. (Oh, yea, archiving is set for monthly volumes, if that wasn't obvious from the previous discussion). I tried switching to "when resent" instead of sent, thinking what that *meant* was that it'd use the From header time instead of the Date header, but as far as I can tell, it didn't affect article processing at all; same error. Here's the header:

1 0

Re: [Mailman-Developers] why not make archive into coference
by Steven Hazel 10 Aug '99

10 Aug '99

Sorry if this has been asked/suggested before but I can find no trace of it in the archives. It's there -- I proposed to start working on it a few weeks ago. The point about doing this with the archives is that this functionality is almost there already - it just needs a way of "on-server" posting to be developed. Since this could be limited to subscribers and can only go to the list then it is safe. Actually, I administrate a web-based forum, and we have stronger needs -- user accounts on a per-system basis, for example, are crucial, and seem to be a popular wish-list item for Mailman already. (For those who have been discussing these, my co-conspiritor and I have been listening. A simple interface to Mailman accounts will be provided for easy integration with existing site accounts, and we're working on allowing logins under email addresses as well as user names.) I've already got a simple web-based posting CGI script written -- I'm cleaning up the formatting and error reporting before I submit it. My friend has a user account system in place, but integration with the list subscription info is still too crude to submit. (BTW, what's the best way for me to submit significant code changes? Since this is a GNU project, I imagine there are some legal papers to be exchanged. Also, do you prefer frequent submissions of sort-of-working code, or infrequent submissions of clean, working code?) If you're interested in helping, let me know. -S

1 0