Mailman 3 June 1999 - Mailman-Users

Wrapper error
by Tom Hallewell Aug. 29, 1999

Aug. 29, 1999

Mailman has been working great for several months until I made a couple of changes on the server. I had been getting tons of mail errors because the hostname was actually an ALIAS according to DNS, so I changed the hostname to the CNAME and stopped getting the errors. Around that same time, I upgraded to RedHat 6.0. Somewhere along the line, I started getting this error everytime anyone tries to post to any of our lists: ----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper post be-install" (expanded from: <be-install(a)techops.rfa.org>) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/home/mailman/mail/wrapper post be-install"... Service unavailable Reading between the lines :), it appears that for some reason sendmail is no longer allowing wrappers. Any ideas? -- Tom Hallewell Lead Technical Engineer Radio Free Asia (202) 530-4976 2025 M St. NW Suite 300 Washington, DC 20036 USA

5 5

Disabling passwords altogether.
by Joseph Leaver Aug. 17, 1999

Aug. 17, 1999

Hi! I run a joke-a-day list and have received several complaints about the need to use passwords to subscribe and unsubscribe. Is there any way to disable this feature? Thanks, Joe

2 1

Authentication/cookies question
by Matthew Darwin July 13, 1999

July 13, 1999

Is there any particular reason why there is no option (that I can find) to configure the web interface to use basic authentication instead of cookies? I am just setting up a mailman site, and I know that I will have some admnistrators connecting from a web browser that supports basic authentication, but not cookies. Background: The local FreeNet uses a very old version of lynx that does not support cookies, and I want to allow those FreeNet users to use mailman.... However, when using lynx they are constantly prompted for the admin password, which makes the whole thing fairly unusable.

2 1

Performance problems and MailMan
by J C Lawrence July 9, 1999

July 9, 1999

I believe I've found out how to reliably reproduce the performance problemsI've noticed here at VA and at Kanga.Nu, and which Barry and another (forget name, sorry) have observed as well: 1) Create a moderated list. 2) Subscribe 200 addresses to the list (can be bogus addresses but the local MTA must accept them) 3) Post at least 30 messages of an average of at least 2K size to the list. 4) Go to the moderation page, approve every message, and hit submit. 5) Watch your system load peg and stay there for an obscenely long time. -- J C Lawrence Home: claw(a)kanga.nu ---------(*) Linux/IA64 - Work: claw(a)varesearch.com ... Beware of cromagnons wearing chewing gum and palm pilots ...

3 4

[ANNOUNCE] Mailman 1.0rc2
by Harald Meland July 8, 1999

July 8, 1999

Hi there, Mailman 1.0 release candidate 2 (1.0rc2) is now available for download from <URL:http://www.list.org/mailman.tar.gz> This is a bugfix release -- most notably, a security flaw in Mailman's cookie authentication mechanisms have been fixed. As the security flaw could be used to obtain access to any Mailman admin page, EVERYONE using Mailman are urged to upgrade AS SOON AS POSSIBLE. One word to everyone who has reported bugs, submitted patches, given suggestions for improvements, or in other ways helped making Mailman the product it is today: Thanks! Se the NEWS file for some more info on what this release fixes. Enjoy, -- Harald

5 5

Subject Line Munging
by Roy Rapoport June 30, 1999

June 30, 1999

Looks like my lists are correctl prepending a TAG to the subject line when configured to do so. But it looks like when people respond to email, mailman doesn't bother to filter out the old occurances of the TAG. So in other words: Someone sends an email to the list titled 'foo'. List gets subject 'TAG foo' Someone responds with 'Re: TAG foo' List gets 'TAG Re: TAG foo' etc. Is this correct behavior? Am I missing a config switch or something? -roy

6 6

'Failed to access config info' error
by Jeff Barger June 30, 1999

June 30, 1999

Ok, I compiled up the latest mailman yesterday and set up a test list. Got the 'new list' email ok and tried to configure the list and got the following error message: Traceback: Traceback (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "/home/mailman/Mailman/Cgi/admin.py", line 65, in main lst = MailList.MailList(list_name) File "/home/mailman/Mailman/MailList.py", line 60, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 771, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info Hmmm. I do see the list in the 'lists' directory. Permissions seem to be correct. Any hints? This is on a Redhat 5.2 box. Python is 1.5.2. -Jeff

1 0

Bug in Mailman version 1.0rc2?
by e.d.j.m. eskes June 30, 1999

June 30, 1999

Hi, I have installed mailman and I'm really impressed but also a little bit disappointed because I hit a bug and have no idea what's the reason. This errormessage pops up when the list administrator try to add a member to a mailinglist. Can anybody give me a hint? Best regards, Bob Bug in Mailman version 1.0rc2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "/home/mailman/Mailman/Cgi/admin.py", line 167, in main ChangeOptions(lst, category, cgi_data, doc) File "/home/mailman/Mailman/Cgi/admin.py", line 850, in ChangeOptions lst.DeleteMember(user) File "/home/mailman/Mailman/MailList.py", line 1062, in DeleteMember self.DeliverToOwner(msg, self.owner) File "/home/mailman/Mailman/Deliverer.py", line 129, in DeliverToOwner self.LogMsg('deliverer', TypeError: call of non-function -- +---------------------------------------------------------------+ | Name :Bob Eskes Email:eskes@signaal.nl | | Org :Hollandse Signaalapparaten B.V. Phone:+31-74-2484341 | | Dept :ASR (ZA-J12) FAX :+31-74-2484018 | | Adres:P.O.box 42, 7550 GD Hengelo, The Netherlands | +----------------------------------------------[ Unclassified ]-+

1 0

Wishlist
by Bek Oberin June 30, 1999

June 30, 1999

Things I'd find useful: - A global post_ok list. This would typically contain the email addresses for the admins at that site, so they could always post to any list without needing approval. - An option to merge admin requests. Two possible ways: Using the site admin password would let you look at all the admin requests pending on all lists at the site; and/or using some special password and your admin email address would show you pending requests for all lists with that admin email address. Either would make adminning multiple lists, or a whole site, much easier. bekj -- : --Hacker-Neophile-Eclectic-Geek-Grrl-Queer-Disabled-Boychick-- : gossamer(a)tertius.net.au http://www.tertius.net.au/~gossamer/ : What you do instead of your work is your real work. : -- Roger Ebert

1 0

Footer and MIME broken
by Bernhard Reiter June 30, 1999

June 30, 1999

Hi, just wanted to add this jitterbug report, but got an error message (see below): GNU/Linux; mailman 1.0rc2 Sending a MIME multipart-message (I tested it with a simple plain text body and a PGP/MIME rfc2015 signature) the footer is simply added to the mail after the mime ending and therefore will probably not be displayed by mime conforming MUA. Mutt e.g. doesn't display it. Hmm I'm not sure, what the best solution is here. Adding it to the main text body is a bad idea, because it will break the pgp-mime signature. (eGroup does that. :( ) Adding it as another MIME attachment might make sense. Bernhard Error when submitting with Jitterbug: | The system encountered a fatal error | | After command: | Received: | | The last error code was: Connection refused Bernhard -- Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard) Association for a Free Informational Infrastructure (ffii.org)

1 0