From jlewis at prospace.org Thu Oct 1 02:40:17 1998 From: jlewis at prospace.org (John Lewis) Date: Wed, 30 Sep 1998 20:40:17 -0400 Subject: [Mailman-Users] HELP! Really like mailman, need help getting it to work. Message-ID: <199810010026.UAA20274@python.org> Greetings all, I'm REALLY excited about mailman, and am dying to get it up and running. I followed the very well written instructions (except for the mail archiver section), and am running into the following problem. Firstly, I am running Redhat 5.1 on an Intel box. Python 1.5 is installed. I skipped the mail archiver step as I could not make heads or tails of the recommended software. I created a new list without a problem, and was able to access it with a web browser. However, when trying to submit changes, I would get the below response. Please, I am not exactly a UNIX guru, but desperately need to get a mailing list system up and running for our non profit organization, and really would love to get mailman working rather than having to wrestle with majordomo. ANY help anyone can offer to get this going would help extremely. Thanks. John Lewis -------------------- 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback. Please report this to the Mailman administrator at this site. From murdock at psych.ucsb.edu Thu Oct 1 03:36:10 1998 From: murdock at psych.ucsb.edu (Larry C. Murdock) Date: Wed, 30 Sep 1998 18:36:10 -0700 Subject: [Mailman-Users] Mailman Installation Problem?? Message-ID: <3612DC89.36DF4C8E@psych.ucsb.edu> I have recently installed mailman package (mailman-1.0b5/Python-1.5.1) and with some minor tweeking have gotten it up and running. I have created the test list and have run into some problems with the feature of allowing only list members to be able to post. I have no problems with members posting, however, I have run into errors from the scripts when a non user attempts to post. As administrator, I receive two copies of the email notification to permit the post and one copy from the mailer daemon indicating an "unknown mailer error 1". As a bit of backgroound information, I had to open up the data directory (777) to get the posting to work (otherwise receiving permission problems). The installation is on a Solaris 2.6 system. The following is the output from ~mailman/logs/error. Any help would be greatly appreciated. Larry Murdock UC Santa Barbara - - - - - - Sep 30 17:42:19 1998 contact_transport: Traceback (innermost last): contact_transport: File "/home/mailman/scripts/contact_transport", line 52, in ? contact_transport: OutgoingQueue.processQueue() contact_transport: File "/home/mailman/Mailman/OutgoingQueue.py", line 38, in processQueue contact_transport: Utils.TrySMTPDelivery(recip,sender,text,full_fname) contact_transport: File "/home/mailman/Mailman/Utils.py", line 204, in TrySMTP Delivery contact_transport: OutgoingQueue.dequeueMessage(queue_entry) contact_transport: File "/home/mailman/Mailman/OutgoingQueue.py", line 25, in dequeueMessage contact_transport: os.unlink(msg) contact_transport: os . error : (2, 'No such file or directory') - - - - - - From conlinbp at SLU.EDU Tue Oct 6 05:46:26 1998 From: conlinbp at SLU.EDU (Brian Conlin) Date: Mon, 05 Oct 1998 22:46:26 -0500 Subject: [Mailman-Users] nancies Message-ID: <000901bdf0db$e5198180$60b186a5@conlinbp.slu.edu> if one of you run the nancies mailing list I need help removing my name from the list, everytime I try they say my file has gone astray, please help Thank you, Brian Conlin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-users/attachments/19981005/5c84a639/attachment.htm From cestluk at polyu.edu.hk Tue Oct 6 10:55:35 1998 From: cestluk at polyu.edu.hk (LUK ShunTim) Date: Tue, 06 Oct 1998 16:55:35 +0800 Subject: [Mailman-Users] Re: HELP! Really like mailman, need help getting Message-ID: <3619DB07.F89C4A16@polyu.edu.hk> Hi, I installed mailman in my Debian 2.0 machine and I ran into exactly the same problem as John Lewis, whose posting I found in the mailman list archive. (And I shared his feeling towards majordomo.) In configurating the Makefile, default values coming with the source are used. The MTA is smail (Debian default), not sendmail and I've added the required aliases in /etc/aliases and ran newaliases. One more observation: When I tried the administration page, in the General Options Section, there are a numbers of links named "Details" which should be pointing to some topic specific explanation but they all gave the Administrative Authentication page although a look at the HTML source show that that are indeed pointing to different locations. Any suggestions on how to solve the problem? ST -- From peter at unica.co.uk Tue Oct 6 16:01:33 1998 From: peter at unica.co.uk (Peter Bowyer) Date: Tue, 6 Oct 1998 15:01:33 +0100 Subject: [Mailman-Users] Mailman with Exim? Message-ID: <057b01bdf131$d37fc6e0$33b74bc2@mulder95.unica.co.uk> I've got the WWW interface working finally - after sorting the permissions and ownerships out as recommended in advice in the archives. But all main commands fail with this : Child process of address_pipe transport returned 69 from command: Any suggestions? I suspect it's permissions again - what user/group should I tell exim to run the command as? Thanks for any help. Peter From rob at alegria.com Tue Oct 6 22:02:37 1998 From: rob at alegria.com (Rob Lingelbach) Date: Tue, 6 Oct 1998 15:02:37 -0500 Subject: [Mailman-Users] former SmartList users? Message-ID: I've been using SmartList (3.11pre7) for many years and am interested in switching my list software to something more current. Are there any former SmartList users here on mailman-users who can tell me that I'll be making the right move? thanks. --Rob -- Rob Lingelbach | 6418 Velasco Ave., Dallas, TX 75214 rob at alegria.com |"I would give nothing for that man's religion whose rob at info.com | very dog and cat are not the better for it." rob at tele.com http://www.alegria.com --Rowland Hill, "Village Dialogues" From darren at jasper.somtel.com Tue Oct 6 22:07:32 1998 From: darren at jasper.somtel.com (Darren Henderson) Date: Tue, 6 Oct 1998 16:07:32 -0400 (EDT) Subject: [Mailman-Users] installing on freebsd 2.2.1 Message-ID: mailman configures just fine but when I try to make it I get.... for d in bin cron filters mail misc Mailman scripts src templates; do (cd $d; make); done for d in Cgi Logging; do (cd $d; make); done gcc -DSCRIPT="\"admin\"" -I. -DCGI_GID=65534 -g -O2 -DHAVE_STRERROR=1 -DSTDC_HEA DERS=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VPRINTF=1 common.o -o admin /usr/lib/crt0.o: Undefined symbol `_main' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. I'm gonna go start digging through the code but on the off chance someone has solved this already... ______________________________________________________________________ Darren Henderson darren at jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From rall at trema.com Wed Oct 7 21:10:51 1998 From: rall at trema.com (Jacques Rall) Date: Wed, 07 Oct 1998 21:10:51 +0200 Subject: [Mailman-Users] Mailman not sending out post Message-ID: <361BBCBA.BA03656B@trema.com> Hi all, We've recently installed mailman here to evaluate it, but ran into a brick wall: mailman does not redistribute any post. It seems that mailman is receiving the post with no problems but it is not sending it out to any of the subscribed users. We've run all the commands in the crontab to no avail. What shall we do? Thanks in advance, Jacques From darren at jasper.somtel.com Fri Oct 9 04:51:07 1998 From: darren at jasper.somtel.com (Darren Henderson) Date: Thu, 8 Oct 1998 22:51:07 -0400 (EDT) Subject: [Mailman-Users] Re: installing on freebsd 2.2.1 In-Reply-To: Message-ID: To answer my own question.... Ok, I don't quite understand why but using gmake instead of make results in a successful instillation. All looks good now. On Tue, 6 Oct 1998, Darren Henderson wrote: > > mailman configures just fine but when I try to make it I get.... > > > for d in bin cron filters mail misc Mailman scripts src templates; do > (cd $d; > make); done > for d in Cgi Logging; do (cd $d; make); done > gcc -DSCRIPT="\"admin\"" -I. -DCGI_GID=65534 -g -O2 -DHAVE_STRERROR=1 > -DSTDC_HEA > DERS=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VPRINTF=1 common.o -o > admin > /usr/lib/crt0.o: Undefined symbol `_main' referenced from text segment > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > > I'm gonna go start digging through the code but on the off chance someone > has solved this already... > > ______________________________________________________________________ > Darren Henderson darren at jasper.somtel.com > > Help fight junk e-mail, visit http://www.cauce.org/ > > ______________________________________________________________________ Darren Henderson darren at jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From John at list.org Fri Oct 9 05:01:49 1998 From: John at list.org (John Viega) Date: Thu, 8 Oct 1998 20:01:49 -0700 Subject: [Mailman-Users] Mailman not sending out post In-Reply-To: <361BBCBA.BA03656B@trema.com>; from Jacques Rall on Wed, Oct 07, 1998 at 09:10:51PM +0200 References: <361BBCBA.BA03656B@trema.com> Message-ID: <19981008200149.A6245@viega.org> Generally the first thing to do is to check the mail log. It does sound like you're probably getting father than that, so the next thing to do would be to check the error log, in $mailmandir/logs/errors or something like that. Let us know what you see, then give us info about your OS, etc... John On Wed, Oct 07, 1998 at 09:10:51PM +0200, Jacques Rall wrote: > Hi all, > > We've recently installed mailman here to evaluate it, but ran into a > brick wall: mailman does not redistribute any post. > > It seems that mailman is receiving the post with no problems but it is > not sending it out to any of the subscribed users. > > We've run all the commands in the crontab to no avail. > > What shall we do? > > Thanks in advance, > Jacques > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users From rall at trema.com Fri Oct 9 11:17:41 1998 From: rall at trema.com (Jacques Rall) Date: Fri, 09 Oct 1998 11:17:41 +0200 Subject: [Mailman-Users] Mailman not sending out post References: <361BBCBA.BA03656B@trema.com> <19981008200149.A6245@viega.org> Message-ID: <361DD4B5.4D6C@trema.com> Hi all, FTF: Solaris 2.6; Sendmail 8.8.8 The file $mailmandir/lists/mylist/next-digest does contain the messages sent to the list. Yesterday - out of the blue - I received a message I had sent to the list a while ago. I've replied to the message yesterday and it has not been sent out to the list users; it's in the next-digest file. The following is in our error file: ### Error File Start Here Oct 07 20:24:45 1998 contact_transport: Traceback (innermost last): contact_transport: File "/etc/mailman/scripts/contact_transport", line 52, in ? contact_transport: OutgoingQueue.processQueue() contact_transport: File "/etc/mailman/Mailman/OutgoingQueue.py", line 38, in processQueue contact_transport: Utils.TrySMTPDelivery(recip,sender,text,full_fname) contact_transport: File "/etc/mailman/Mailman/Utils.py", line 204, in TrySMTPDelivery contact_transport: OutgoingQueue.dequeueMessage(queue_entry) contact_transport: File "/etc/mailman/Mailman/OutgoingQueue.py", line 25, in dequeueMessage contact_transport: os.unlink(msg) contact_transport: os . error : (2, 'No such file or directory') Oct 07 20:24:45 1998 contact_transport: Traceback (innermost last): contact_transport: File "/etc/mailman/scripts/contact_transport", line 52, in ? contact_transport: OutgoingQueue.processQueue() contact_transport: File "/etc/mailman/Mailman/OutgoingQueue.py", line 38, in processQueue contact_transport: Utils.TrySMTPDelivery(recip,sender,text,full_fname) contact_transport: File "/etc/mailman/Mailman/Utils.py", line 204, in TrySMTPDelivery contact_transport: OutgoingQueue.dequeueMessage(queue_entry) contact_transport: File "/etc/mailman/Mailman/OutgoingQueue.py", line 25, in dequeueMessage contact_transport: os.unlink(msg) contact_transport: os . error : (2, 'No such file or directory') Oct 07 20:44:52 1998 post: Traceback (innermost last): post: File "/etc/mailman/scripts/post", line 69, in ? post: current_list.Post(msg) post: File "/etc/mailman/Mailman/MailList.py", line 799, in Post post: sender = msg.GetSender() post: File "/etc/mailman/Mailman/Message.py", line 113, in GetSender post: return string.lower(mail_address) post: TypeError : read-only buffer, None Oct 07 20:45:13 1998 post: Traceback (innermost last): post: File "/etc/mailman/scripts/post", line 69, in ? post: current_list.Post(msg) post: File "/etc/mailman/Mailman/MailList.py", line 799, in Post post: sender = msg.GetSender() post: File "/etc/mailman/Mailman/Message.py", line 113, in GetSender post: return string.lower(mail_address) post: TypeError : read-only buffer, None Oct 07 20:45:46 1998 post: Traceback (innermost last): post: File "/etc/mailman/scripts/post", line 69, in ? post: current_list.Post(msg) post: File "/etc/mailman/Mailman/MailList.py", line 799, in Post post: sender = msg.GetSender() post: File "/etc/mailman/Mailman/Message.py", line 113, in GetSender post: return string.lower(mail_address) post: TypeError : read-only buffer, None Oct 08 12:00:02 1998 contact_transport: Traceback (innermost last): contact_transport: File "/etc/mailman/scripts/contact_transport", line 52, in ? contact_transport: OutgoingQueue.processQueue() contact_transport: File "/etc/mailman/Mailman/OutgoingQueue.py", line 38, in processQueue contact_transport: Utils.TrySMTPDelivery(recip,sender,text,full_fname) contact_transport: File "/etc/mailman/Mailman/Utils.py", line 204, in TrySMTPDelivery contact_transport: OutgoingQueue.dequeueMessage(queue_entry) contact_transport: File "/etc/mailman/Mailman/OutgoingQueue.py", line 25, in dequeueMessage contact_transport: os.unlink(msg) contact_transport: os . error : (2, 'No such file or directory') ### Error File Stop Here Thanks, Jacques John Viega wrote: > > Generally the first thing to do is to check the mail log. It does > sound like you're probably getting father than that, so the next thing > to do would be to check the error log, in $mailmandir/logs/errors or > something like that. Let us know what you see, then give us info > about your OS, etc... > > John > > On Wed, Oct 07, 1998 at 09:10:51PM +0200, Jacques Rall wrote: > > Hi all, > > > > We've recently installed mailman here to evaluate it, but ran into a > > brick wall: mailman does not redistribute any post. > > > > It seems that mailman is receiving the post with no problems but it is > > not sending it out to any of the subscribed users. > > > > We've run all the commands in the crontab to no avail. > > > > What shall we do? > > > > Thanks in advance, > > Jacques > > > > > > ------------------------------------------------------ > > Mailman-Users maillist - Mailman-Users at python.org > > http://www.python.org/mailman/listinfo/mailman-users From bwarsaw at cnri.reston.va.us Fri Oct 9 15:50:39 1998 From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw) Date: Fri, 9 Oct 1998 09:50:39 -0400 (EDT) Subject: [Mailman-Users] Re: installing on freebsd 2.2.1 References: Message-ID: <13854.5295.741617.730096@anthem.cnri.reston.va.us> >>>>> "DH" == Darren Henderson writes: DH> To answer my own question.... DH> Ok, I don't quite understand why but using gmake instead of DH> make results in a successful instillation. All looks good now. Some GNU make-isms may have crept in, and I'll check for that, although my only alternative is Solaris make. Thanks, -Barry From darren at jasper.somtel.com Fri Oct 9 20:40:23 1998 From: darren at jasper.somtel.com (Darren Henderson) Date: Fri, 9 Oct 1998 14:40:23 -0400 (EDT) Subject: [Mailman-Users] archiving and piper Message-ID: Does anyone have any pointers to info on configuring/installing piper and getting it working with mailman. Perhaps I'm overlooking it in the distributions I pulled in or perhaps I'm looking to hard and its simpler then I'm thinking it should be:) ______________________________________________________________________ Darren Henderson darren at jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From John at list.org Fri Oct 9 20:56:16 1998 From: John at list.org (John Viega) Date: Fri, 9 Oct 1998 11:56:16 -0700 Subject: [Mailman-Users] archiving and piper In-Reply-To: ; from Darren Henderson on Fri, Oct 09, 1998 at 02:40:23PM -0400 References: Message-ID: <19981009115616.A11902@viega.org> Darren, The version of Mailman in the CVS tree has integrated archiving support again, finally, thanks to Dragon and Scott. It'll be in the next release. I think that's going to be the easiest path to archives, to upgrade when that release comes out. There's a new release around the corner; we need to integrate some patches from Nagy, and then test it to make sure it works out of the box to some reasonable degree. I've got time dedicated to that this weekend, and during the week next week. So I'd say there'll be a new release with archiving in it by the middle of next week, perhaps earlier. John On Fri, Oct 09, 1998 at 02:40:23PM -0400, Darren Henderson wrote: > > Does anyone have any pointers to info on configuring/installing piper and > getting it working with mailman. Perhaps I'm overlooking it in the > distributions I pulled in or perhaps I'm looking to hard and its simpler > then I'm thinking it should be:) > > ______________________________________________________________________ > Darren Henderson darren at jasper.somtel.com > > Help fight junk e-mail, visit http://www.cauce.org/ > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users From michael at spconnect.com Mon Oct 12 17:54:25 1998 From: michael at spconnect.com (Michael Ghens) Date: Mon, 12 Oct 1998 08:54:25 -0700 (PDT) Subject: [Mailman-Users] Mail Precidence Message-ID: Neet list! Anyway. I noticed that mail is sent out as normal mail instead of Precidence bulk or list. Also, is there a switch for just queueing the mail. On large systems, this is at times, desireable. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Michael Ghens Small Planet Connections Internet: michael at spconnect.com Santa Barbara, CA http://www.spconnect.com/~michael ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Unix is user friendly. It's just selective about who its friends are. From grin at tolna.net Thu Oct 15 00:21:35 1998 From: grin at tolna.net (Peter Gervai) Date: Thu, 15 Oct 1998 00:21:35 +0200 Subject: [Mailman-Users] Configuration under EXIM and Debian v2.0 Message-ID: <19981015002135.G5403@mail.tolna.net> Hello, Browsing the list revealed that no real how-to is present on using mailman with exim and/or debian. There is actually a deb package for sendmail, but it won't work for exim. I tried to install it and it works, more-or-less. I'd like to share that what I've done and raise some still not resolved questions. I'd like to comment that trying beta4 made python process to start allocating all available virtual memory (and beyond), rendering the machine unusable... I'm sure it was because some mistakes on my part but maybe it's possible to stop wild allocations caused by bad permissions, illegal mail headers, etc. Reinstalled beta5 from scratch and now it works. Either the bug got fixed, or I made config right this time, or most probably pure magic. My most important question: please anyone tell me which files, directories must have different permissions from chown mailman.mailman and 0775 (dir) or 664 (file)! I suspect log/ and files inside, and list/ maybe with its full content, but I don't know all possible files, and maybe missed some, and I have to KNOW it and not to guess, which gets used (needs to be written) as "mailman", which as "www-data", and which as both (probably requires some common groups then). This is my most important problem. The other is some actual minor one: mailman web interface cannot unlock a list, when a user want to enter her options webpage: Error at Cgi/subscribe.py line 65 - Unlock... Probably permission problem but I can't figure it out. Remember, I don't speak Python AT ALL. TIA. Okay, thats about questions. Here's the "debian+exim install manual" v0.01 -----------------------------8<------------------------------- Installing MailMan (1.0b5) on Debian GNU/Linux v2.0 + Exim by gervai 'grin' peter , v0.01 98/10/14 Install python-base, python-net. Install mailman user and group. I advise you to use 'lists' user and group id. (You can play and compile the whole stuff to lists.lists, probably not a big speciality, but I'm in kind of hurry. And a bit easier for me...) Compile very carefully to use correct mailman uid for the mail, and www-data uid for the cgi programs. (I have put stuff into /var/lib/mailman, but hardcore Debian file system standard gods may tell me otherwise. YMMW.) ./configure --prefix=/var/lib/mailman --with-mail-gid='mailman' \ --with-cgi-gid='www-data' Compile. Install. After installed, the following modifications were installed: - Fix up directory permissions, enable logging (even after that I ain't sure whether all logging will be allright...) chgrp lists /var/lib/mailman/* chmod 775 /var/lib/mailman/* chmod 3777 /var/lib/mailman/{logs,locks} - Enable web configuration interface chown www-data /var/lib/mailman/lists -R - Enable scripts for running them from the pipe transport later chmod +x /var/lib/mailman/scripts/{post,mail}* - Base Exim setup for lists. We create a separate alias file for the lists in /etc/mailman/aliases, and we insert lists there. We run everything uid,gid=mailman. Insert into /etc/exim.conf: into TRANSPORTS (place isn't important) mailman_pipe: driver = pipe; current_directory = /var/lib/mailman into DIRECTORS (immediately after system_aliases: section) mailman_list: driver = aliasfile; file = /etc/mailman/aliases search_type = lsearch user = mailman group = mailman pipe_transport = mailman_pipe - Create a list as usual. 'su - www-data' before creating... When creating, newlist tells you what to insert. Twist it a little, such as: test: "|/var/lib/mailman/scripts/post test" test-admin: "|/var/lib/mailman/scripts/mailowner test" test-request: "|/var/lib/mailman/scripts/mailcmd test" the other two alias is just okay. Insert this stuff into /etc/mailman/aliases, then press ENTER to get the administrative mail about the new list. - Several file gets created uid.gid I don't like, and had to fix afterwards. I can't python, so anyone see the light can help me... or us. - /var/lib/mailman/logs/* (esp: error and subscribe) chown them to www-data or touch/chown them beforehand. ------------------------------->8---------------------------- All comments are welcome, of course. If I made a mistake by list netiquette, just correct me. MOst of the time I'm in hurry so writing's first, thinking's afterwards. :-)) regards, grin (grin at tolna.net) From Harald.Meland at usit.uio.no Thu Oct 15 00:46:27 1998 From: Harald.Meland at usit.uio.no (Harald Meland) Date: 15 Oct 1998 00:46:27 +0200 Subject: [Mailman-Users] Configuration under EXIM and Debian v2.0 In-Reply-To: Peter Gervai's message of "Thu, 15 Oct 1998 00:21:35 +0200" References: <19981015002135.G5403@mail.tolna.net> Message-ID: [Peter Gervai] > - Create a list as usual. 'su - www-data' before creating... > When creating, newlist tells you what to insert. > Twist it a little, such as: > test: "|/var/lib/mailman/scripts/post test" > test-admin: "|/var/lib/mailman/scripts/mailowner test" > test-request: "|/var/lib/mailman/scripts/mailcmd test" This one stung me, too. Is the sendmail aliases syntax different from the Exim syntax here? Exim interprets the alias test: |"/var/lib/mailman/scripts/post test" as "when mail resolved via the alias key "test" arrives, try piping it to the space-containing command name '/var/lib/mailman/scripts/post test' with no arguments" If both sendmail and Exim are happy with the following syntax: test: |/var/lib/mailman/scripts/post test , I propose changing the current "newlist" output. -- Harald From Harald.Meland at usit.uio.no Thu Oct 15 01:09:35 1998 From: Harald.Meland at usit.uio.no (Harald Meland) Date: 15 Oct 1998 01:09:35 +0200 Subject: [Mailman-Users] Mailman for use in large installation wishlist Message-ID: I am considering switching all our nearly 4000 mailing lists over to Mailman (eventually, there's no hurry for most of the lists (I'm only halfway through the Python tutorial yet :)), but with that many lists being involved, I'm having second thoughts due to some issues in the current Mailman implementation. First, some of our list administrators have admin rights for as many as 50 lists. That amounts to rather a lot of list passwords to keep track of for the poor admin, which is undesirable to say the least. Currently, our mailing list interface is a UNIX shell command, and determines whether to allow administration or not based upon the callers UID. That way, all the passwords any admin has to remember, is their standard UNIX password. Of course, it also means that only local UNIX users are able to administrate our lists (which means it is sometimes a bit of a pain to find new admins for old lists). Second, very many of our lists have several admins. Implementing multiple list admins by means of "share this one admin password between the lot of you" seems to me to be rather an ad hoc way of doing it. So, I was thinking: Would it be possible to have a Mailman-global database of administrators' (more-or-less canonical) email addresses and their passwords, and require both email address and password when authenticating for list administration? That way, each admin would only have to remember _one_ password (and their email address :), no matter how many lists she administrates, and multiple admins would authenticate using separate passwords. Mailman would still not have the restriction of allowing only local users to do administration. Any thoughts? Are anyone using Mailman for large lists/huge numbers of lists? PS: Is there any way of turning list archiving off entirely for any particular list? Archiving all of our nearly 4000 lists would need a lot of disk pretty fast... :) -- Harald From tomas at euronetics.se Thu Oct 15 15:18:55 1998 From: tomas at euronetics.se (Tomas Fasth) Date: Thu, 15 Oct 1998 15:18:55 +0200 Subject: [Mailman-Users] Configuration under EXIM and Debian v2.0 Message-ID: <001f01bdf83e$5c6055c0$f6d52dc1@bishop.twinspot.net> From: Harald Meland To: Mailman users Date: den 15 oktober 1998 06:32 Subject: Re: [Mailman-Users] Configuration under EXIM and Debian v2.0 >This one stung me, too. Is the sendmail aliases syntax different from >the Exim syntax here? Exim interprets the alias > >test: |"/var/lib/mailman/scripts/post test" AFAIK, sendmail applies standard RFC822 syntactical rules on aliases. Hence the quotation to deal with white spaces. Another thing; There is no wrapper involved in your example. Like this: test: |"/home/mailman/scripts/wrapper post test" According to my understanding the wrapper is needed to set user id / group id accordingly, among other things. At least when using sendmail as MTA. How does exim handle the if not through a wrapper? On the other hand, I notice the path to be /var/lib/mailman. Does this mean you're running mailman as root? Isn't that kind of dangerous? >, I propose changing the current "newlist" output. Better up, if the current output isn't portable, make the newlist output configurable at installation time (by setting type of MTA). -- Tomas From Harald.Meland at usit.uio.no Thu Oct 15 17:40:00 1998 From: Harald.Meland at usit.uio.no (Harald Meland) Date: 15 Oct 1998 17:40:00 +0200 Subject: [Mailman-Users] Configuration under EXIM and Debian v2.0 In-Reply-To: Tomas Fasth's message of "Thu, 15 Oct 1998 15:18:55 +0200" References: <001f01bdf83e$5c6055c0$f6d52dc1@bishop.twinspot.net> Message-ID: [Tomas Fasth] > From: Harald Meland > > >test: |"/var/lib/mailman/scripts/post test" > > AFAIK, sendmail applies standard RFC822 syntactical rules on > aliases. Hence the quotation to deal with white spaces. OK, but does test: "|/var/lib/mailman/scripts/post test" do the same thing as the above alias? Or does sendmail rely on the first non-whitespace character to be `|' in the value of a pipe alias (thereby making use of `"' as the first character inappropriate for Mailman)? > Another thing; There is no wrapper involved in your example. Like this: Well, it wasn't really my example -- I just snipped the alias described by Peter Gervai to explain the Exim/sendmail problem. In my Exim setup, I have set up things to use the wrapper: Alias file entry: ----------------- test: "|/local/Mailman/mail/wrapper post test" test-admin: "|/local/Mailman/mail/wrapper mailowner test" test-request: "|/local/Mailman/mail/wrapper mailcmd test" owner-test: test-admin test-owner: test-admin Relevant parts of my Exim configuration: ---------------------------------------- # My Mailman transport config: mailman_list_pipe: driver = pipe allow_commands = /local/Mailman/mail/wrapper user = mailman return_output # ... and the corresponding director config: local_lists: driver = aliasfile search_type = lsearch # This is not in production use yet, so don't mind the odd placement # of my alias file :) file = /local/Mailman/data/MTA_aliases pipe_transport = mailman_list_pipe > According to my understanding the wrapper is needed to set user id / > group id accordingly, among other things. On my system the wrapper is only setgid, not setuid. As you can see from the transport configuration above, I set the uid to run the pipe as explicitly in the "user = mailman" line. > How does exim handle the if not through a wrapper? I guess that if all the wrapper does is to change UID and GID, Exim should be able to do without it entirely (by setting them in the transport config). I haven't bothered to find out yet, though. > Does this mean you're running mailman as root? I don't know for sure, but I wouldn't think so. > >, I propose changing the current "newlist" output. > > Better up, if the current output isn't portable, make the newlist > output configurable at installation time (by setting type of MTA). Maybe this will be needed eventually. However, if there is any chance of making the output portable between MTAs, that would be less of a hassle (to the installing admin) than having to specify which type of alias to use. -- Harald From John at list.org Thu Oct 15 21:24:25 1998 From: John at list.org (John Viega) Date: Thu, 15 Oct 1998 12:24:25 -0700 Subject: [Mailman-Users] Mailman for use in large installation wishlist In-Reply-To: ; from Harald Meland on Thu, Oct 15, 1998 at 01:09:35AM +0200 References: Message-ID: <19981015122425.E20205@viega.org> That's a good idea. I'm out of town this week, unexpectedly, but I'll personally work on this next week. John On Thu, Oct 15, 1998 at 01:09:35AM +0200, Harald Meland wrote: > I am considering switching all our nearly 4000 mailing lists over to > Mailman (eventually, there's no hurry for most of the lists (I'm only > halfway through the Python tutorial yet :)), but with that many lists > being involved, I'm having second thoughts due to some issues in the > current Mailman implementation. > > First, some of our list administrators have admin rights for as many > as 50 lists. That amounts to rather a lot of list passwords to keep > track of for the poor admin, which is undesirable to say the least. > > Currently, our mailing list interface is a UNIX shell command, and > determines whether to allow administration or not based upon the > callers UID. That way, all the passwords any admin has to remember, > is their standard UNIX password. Of course, it also means that only > local UNIX users are able to administrate our lists (which means it is > sometimes a bit of a pain to find new admins for old lists). > > Second, very many of our lists have several admins. Implementing > multiple list admins by means of "share this one admin password > between the lot of you" seems to me to be rather an ad hoc way of > doing it. > > So, I was thinking: Would it be possible to have a Mailman-global > database of administrators' (more-or-less canonical) email addresses > and their passwords, and require both email address and password when > authenticating for list administration? > > That way, each admin would only have to remember _one_ password (and > their email address :), no matter how many lists she administrates, > and multiple admins would authenticate using separate passwords. > Mailman would still not have the restriction of allowing only local > users to do administration. > > > Any thoughts? Are anyone using Mailman for large lists/huge numbers > of lists? > > PS: Is there any way of turning list archiving off entirely for any > particular list? Archiving all of our nearly 4000 lists would > need a lot of disk pretty fast... :) > -- > Harald > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users From klm at python.org Thu Oct 15 22:31:55 1998 From: klm at python.org (Ken Manheimer) Date: Thu, 15 Oct 1998 16:31:55 -0400 (EDT) Subject: [Mailman-Users] Changing admin address for "umbrella" list subscribers Message-ID: <13862.21703.306671.729249@glyph.cnri.reston.va.us> A while back i implemented a mailman feature to facilitate having "umbrella" lists to which other lists could be subscribed. I would like to change it slightly, and want to see if i'd be messing anybody up with the change. I'm not even sure if anybody but me uses the feature, so first i'll explain what it's about, and then i'll explain the problem. The idea is to enable maillists that are composed of only other maillists, as "subscribers". That way, announcements of interest to groups of lists could be sent to the encompassing list. This may sound peculiar, but it actually makes sense in the context of, for example, activities that have regional groups doing their regional thing, but also occasionally collecting together for, eg, national conclaves, or for discussions of common issues across the regions, etc. (In fact, i'm establishing a network of lists for people who do something i'm part of, contact improvisation, and this arrangement looks really pretty good for us.) The only special provision i had to make for this arrangment is an admin setting so that the members administrative stuff, like the monthly password reminders, are _not_ posted to the subscribed lists, but to their administrators. I created the 'reminders_to_admins' option, and set it so that the reminders would go to the 'list-admin at host.domain' account, rather than 'list at host.domain'. (I'm pretty sure this was pre 1.0b4, so it's been there for a while, probably unnoticed by most people.) The problem is that it may be that '-owner' is a more prevalent suffix for list administrator addresses than '-admin'. At least, that's what makelist.com seems to use, and from my probing they don't seem to support the '-admin' alias, while the policy for mailman is to support both. So i'm considering changing the option to go to '-owner' address instead of '-admin', but before i do that i wanted to find out whether (1) anyone already depends on the '-admin' option, and (2) whether anyone has objections to making the switch, in any case. (We could add *another* option to designate the suffix, but that doesn't strike me as a good solution - we'd be better off striving for some standard, than encouraging fragmentation here. What good would one choice or another be if some of the subscriber lists within the umbrella have one and some have the other?) Any clear feelings, one way or the other, from anyone? I plan on making the change within the next few days, but can still be dissuaded by solid arguments... Ken Manheimer klm at python.org 703 620-8990 x268 (orporation for National Research |nitiatives # If you appreciate Python, consider joining the PSA! # # . # From davroc at hplb.hpl.hp.com Fri Oct 16 12:13:17 1998 From: davroc at hplb.hpl.hp.com (David Rocher) Date: Fri, 16 Oct 1998 10:13:17 +0000 Subject: [Mailman-Users] Re: Mailman for use in large installation wishlist In-Reply-To: ; from Harald Meland on Thu, Oct 15, 1998 at 01:09:35AM +0200 References: Message-ID: <19981016101317.B5989@hplb.hpl.hp.com> The problem with the administrators is the same for subscibers. In fact web interface of mailman is lists oriented and not human oriented ( list -> email/passwd and not email/passwd -> lists ). Perhaps 2 databases (users & administrators) should be created which contain email/passwd. this is also help when you want to send a mail to all your mailman users. Next release of majordomo will include such feature. Another more ambitious thing could be 2 views on the web interface. lists oriented (like now) human orinted: 1/ email/passwd and all the subscribed lists or 2/ email and list A list B passwd: list C passwd: (this one is general and 1/ is one special case) David. From jbaddor at sca.uqam.ca Fri Oct 16 15:04:21 1998 From: jbaddor at sca.uqam.ca (Jean-Bernard ADDOR) Date: Fri, 16 Oct 1998 09:04:21 -0400 (EDT) Subject: [Mailman-Users] Human orinted interface In-Reply-To: <19981016101317.B5989@hplb.hpl.hp.com> Message-ID: Hy! Human oriented interface would be very appreciated. We have not finished the installation yet and I don't know what happen if a message is crossposted on many lists, but I strongly hope it will be send to a multiple subscriber only once. Such human oriented behaviour is very appreciated. A bientot, Jean-Bernard On Fri, 16 Oct 1998, David Rocher wrote: > The problem with the administrators is the same for subscibers. In > fact web interface of mailman is lists oriented and not human oriented > ( list -> email/passwd and not email/passwd -> lists ). > > Perhaps 2 databases (users & administrators) should be created which > contain email/passwd. this is also help when you want to send a mail > to all your mailman users. Next release of majordomo will include such > feature. > > Another more ambitious thing could be 2 views on the web interface. > lists oriented (like now) > human orinted: > 1/ email/passwd and all the subscribed lists > or > 2/ email and > > list A > list B > passwd: > > list C > passwd: > > (this one is general and 1/ is one special case) > > David. > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users > From Harald.Meland at usit.uio.no Fri Oct 16 16:21:13 1998 From: Harald.Meland at usit.uio.no (Harald Meland) Date: 16 Oct 1998 16:21:13 +0200 Subject: [Mailman-Users] Human orinted interface In-Reply-To: Jean-Bernard ADDOR's message of "Fri, 16 Oct 1998 09:04:21 -0400 (EDT)" References: Message-ID: [Jean-Bernard ADDOR] > We have not finished the installation yet and I don't know what > happen if a message is crossposted on many lists, but I strongly > hope it will be send to a multiple subscriber only once. I doubt it. In order for that to work, Mailman would have to have: * a way of detecting when a message is posted to several Mailman lists. Today the "post" commands for the various lists are started by the MTA, and lead entirely separate lives. * a way of deciding _which_ of the MTA-started "post" commands should send the message to the multiple-subscribed address. A way of doing this would be to have a global database over what message-ids (a message-uniqe ID, not necessarily from the Message-Id: header. Determining this id is not necessarily trivial) that have been sent to what addresses. The first list to process a new message-id for anyt given address, enters the message-id/address pair into the database, thereby blocking any other "post" commands from sending that message to that address. Personally, I think this would be rather kludgy (to say the least). But, while we're on the subject of interprocess communication: I have some lists consisting of sublists, and I would like all of them to be moderated. Is there any (moderation-safe) way of saying "Once a message has been allowed onto the superlist, don't ask for confirmation from the sublists"? -- Harald From jbaddor at sca.uqam.ca Fri Oct 16 16:44:08 1998 From: jbaddor at sca.uqam.ca (Jean-Bernard ADDOR) Date: Fri, 16 Oct 1998 10:44:08 -0400 (EDT) Subject: [Mailman-Users] Human orinted interface In-Reply-To: Message-ID: Hy again! I have absolutly no idea about mailman implementation. I found great the interface and to use python to do the job. And now my system administrator install it. In the meantime I use a path with procmail to do the job in my personal account. Some users (multiple lists subscribers) suggested me that it is desirable to receive only once crosposted messages. So yesterday I organised my patch as a person list and for each person I have a list of subscribed list and I do the posting accordingly to that list. It is completly person oriented. But it is a simple provisional patch and I hope I'll be able to use mailman soon. I strongly hope one day mailman will be able to do the same. It sould work with one person database only without all the terrific staff you told me (sorry if I completly misunderstand how mailman works, I never imaginated it was so complex). It could be essential with an ombrella list organisation as suggested yesterday on this list. It is very desirable for user with poor internet link (I have a lot of subscribers in southern contries). I have a dream to install a e-mail to fax gateway so multiple posting of crossposted messages could be problematic. Thank you for information and special thanks to the programmers to allows people communicate with such a beautifull tool. See you, Jean-Bernard On 16 Oct 1998, Harald Meland wrote: > [Jean-Bernard ADDOR] > > > We have not finished the installation yet and I don't know what > > happen if a message is crossposted on many lists, but I strongly > > hope it will be send to a multiple subscriber only once. > > I doubt it. In order for that to work, Mailman would have to have: > > * a way of detecting when a message is posted to several Mailman > lists. Today the "post" commands for the various lists are started > by the MTA, and lead entirely separate lives. > > * a way of deciding _which_ of the MTA-started "post" commands should > send the message to the multiple-subscribed address. > > A way of doing this would be to have a global database over what > message-ids (a message-uniqe ID, not necessarily from the Message-Id: > header. Determining this id is not necessarily trivial) that have > been sent to what addresses. The first list to process a new > message-id for anyt given address, enters the message-id/address pair > into the database, thereby blocking any other "post" commands from > sending that message to that address. > > Personally, I think this would be rather kludgy (to say the least). > > But, while we're on the subject of interprocess communication: I have > some lists consisting of sublists, and I would like all of them to be > moderated. Is there any (moderation-safe) way of saying "Once a > message has been allowed onto the superlist, don't ask for > confirmation from the sublists"? > -- > Harald > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users > From bharding at admin.itol.com Sun Oct 18 05:16:00 1998 From: bharding at admin.itol.com (Brent Harding) Date: Sat, 17 Oct 1998 22:16:00 -0500 Subject: [Mailman-Users] (no subject) Message-ID: <1.5.4.32.19981018031600.00676cb8@admin.itol.com> put list.header dog dog newconfig shutdown serve ban From bharding at admin.itol.com Sun Oct 18 05:16:45 1998 From: bharding at admin.itol.com (Brent Harding) Date: Sat, 17 Oct 1998 22:16:45 -0500 Subject: [Mailman-Users] management of lists Message-ID: <1.5.4.32.19981018031645.0066522c@admin.itol.com> Is it possible to manage lists via email with mailman? From dlux at dlux.sch.bme.hu Mon Oct 19 01:35:12 1998 From: dlux at dlux.sch.bme.hu (Szabo, Balazs) Date: Mon, 19 Oct 1998 01:35:12 +0200 (CEST) Subject: [Mailman-Users] Exim patch Message-ID: Hi! I am using Exim, and I have problems with the aliases formt. This is a very simple patch, that swaps the '"' with the '|' in the newlist file: ------------------------- --- bin/newlist.orig Mon Oct 19 01:31:12 1998 +++ bin/newlist Mon Oct 19 01:31:15 1998 @@ -91,9 +91,9 @@ ## %(listname)s mailing list ## created: %(date)s %(user)s -%(list)s |"%(wrapper)s post %(listname)s" -%(admin)s |"%(wrapper)s mailowner %(listname)s" -%(request)s |"%(wrapper)s mailcmd %(listname)s" +%(list)s "|%(wrapper)s post %(listname)s" +%(admin)s "|%(wrapper)s mailowner %(listname)s" +%(request)s "|%(wrapper)s mailcmd %(listname)s" %(owner1)s %(listname)s-admin %(owner2)s %(listname)s-admin ''' % {'listname': list_name, ------------------------ This patch is for the b6 CVS version. dLux -- mailto:dlux at dlux.rulez.org From dlux at dlux.sch.bme.hu Mon Oct 19 01:50:27 1998 From: dlux at dlux.sch.bme.hu (Szabo, Balazs) Date: Mon, 19 Oct 1998 01:50:27 +0200 (CEST) Subject: [Mailman-Users] Some small problems Message-ID: Hi! I have one thing to add to the TODO: - If I subscribe a user with no email address (I added 3 empty line to the mass-subscribe list), it cannot be deleted dLux -- :wq From akuchlin at cnri.reston.va.us Mon Oct 19 22:20:11 1998 From: akuchlin at cnri.reston.va.us (Andrew M. Kuchling) Date: Mon, 19 Oct 1998 16:20:11 -0400 (EDT) Subject: [Mailman-Users] Some notes on upgrading to the current CVS tree Message-ID: <13867.40658.67588.457607@amarok.cnri.reston.va.us> Notes on upgrading to the current CVS tree of Mailman: * I ran configure and make as myself, su'ed to mailman, and then ran into some trouble on the "make install" because some files aren't world-readable: scripts/driver Numerous templates/*.txt files Mailman/Logging/*.py But it's much less error-prone to do everything as the mailman user... * The documentation should mention that you should alias /pipermail/ to /public_html/archives/ . * The mailbox-format archive is stored as a gzip'ped file, but referenced in the HTML in uncompressed form. Why? Are you expected to configure the Web server to automatically uncompress it? If so, how do you do that? * Is there any way to clear out my test e-mails from the archives? Since Mailman has just been set up, it would be fine with me if I could just blow away public_html/archives; would it be created again? -- A.M. Kuchling http://starship.skyport.net/crew/amk/ "Are you ready for me? Are you ready for my indifference? For my abysmal disinterest? Are you ready to have the lies and conceits of your life peeled away like so many layers of skin? Are you ready for the truth?" "Ahhh... No, I... I don't really think I am..." -- The Truth and Michael Smith, in ENIGMA #4: "And Then What?" From bwarsaw at cnri.reston.va.us Mon Oct 19 23:35:47 1998 From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw) Date: Mon, 19 Oct 1998 17:35:47 -0400 (EDT) Subject: [Mailman-Users] Some notes on upgrading to the current CVS tree References: <13867.40658.67588.457607@amarok.cnri.reston.va.us> Message-ID: <13867.45235.55332.909463@anthem.cnri.reston.va.us> >>>>> "AMK" == Andrew M Kuchling writes: AMK> Notes on upgrading to the current CVS tree of Mailman: AMK> * I ran configure and make as myself, su'ed to mailman, and AMK> then ran into some trouble on the "make install" because some AMK> files aren't world-readable: | scripts/driver | Numerous templates/*.txt files | Mailman/Logging/*.py I believe I've fixed all the permission problems for the files in the CVS repository. I'm probably the biggest culprit, my umask used to be set up bogusly and I haven't been able to get CVS to fix the permission on files in the repository automatically. We developers just need to be careful when we check stuff in. -barry From bwarsaw at cnri.reston.va.us Tue Oct 20 00:19:40 1998 From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw) Date: Mon, 19 Oct 1998 18:19:40 -0400 (EDT) Subject: [Mailman-Users] Some notes on upgrading to the current CVS tree References: <13867.40658.67588.457607@amarok.cnri.reston.va.us> Message-ID: <13867.47868.717103.26705@anthem.cnri.reston.va.us> >>>>> "AMK" == Andrew M Kuchling writes: AMK> But it's much less error-prone to do everything as the AMK> mailman user... I would like a guiding principle to be that the installation does not require you to be any special user (mailman or root). That may not be possible but so far it has been. If it really is not possible, then we'll have to add an extra step to the installation process -- one that you would execute after the main install, and which you would do as the special user. I'm looking into this. -Barry From bwarsaw at cnri.reston.va.us Tue Oct 20 00:40:26 1998 From: bwarsaw at cnri.reston.va.us (Barry A. Warsaw) Date: Mon, 19 Oct 1998 18:40:26 -0400 (EDT) Subject: [Mailman-Users] Exim patch References: Message-ID: <13867.49114.35920.454960@anthem.cnri.reston.va.us> >>>>> "BS" == Balazs Szabo writes: BS> I am using Exim, and I have problems with the aliases BS> formt. This is a very simple patch, that swaps the '"' with BS> the '|' in the newlist file: My Solaris sendmail (which appears to be derived from 8.8.8) doesn't seem to care, and neither does the RH Linux 5.1 system I tested, so I'm inclined to install this change. I don't have any other systems to try, so I'd like to know if anybody has any objections. -Barry From michael at spconnect.com Tue Oct 20 05:49:56 1998 From: michael at spconnect.com (Michael Ghens) Date: Mon, 19 Oct 1998 20:49:56 -0700 (PDT) Subject: [Mailman-Users] pipermail In-Reply-To: <13867.47868.717103.26705@anthem.cnri.reston.va.us> Message-ID: Been looking through the docs and the archives for getting pipermail to work with mailman. I am using mailman-1.0b5. Any links or hints on how to get it up and running??? TIA Michael From cklempay at acm.jhu.edu Tue Oct 20 05:55:17 1998 From: cklempay at acm.jhu.edu (Corbett J. Klempay) Date: Mon, 19 Oct 1998 23:55:17 -0400 (EDT) Subject: [Mailman-Users] pipermail In-Reply-To: Message-ID: I'm thinking that if you can, you might as well just hold off on it for a bit; Pipermail support was checked into the development CVS tree the week before last, and a new release (with Pipermail support) is in the works for the not-so-distant future. ------------------------------------------------------------------------------ Corbett J. Klempay Quote of the Week: http://www2.acm.jhu.edu/~cklempay "Keep your faith in all beautiful things; in the sun when it is hidden, in the Spring when it is gone." PGP Fingerprint: 7DA2 DB6E 7F5E 8973 A8E7 347B 2429 7728 76C2 BEA1 ------------------------------------------------------------------------------ On Mon, 19 Oct 1998, Michael Ghens wrote: > Been looking through the docs and the archives for getting pipermail to > work with mailman. I am using mailman-1.0b5. Any links or hints on how to > get it up and running??? > > TIA > Michael > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users > From frankwin at mrcyber.a2000.ml.org Fri Oct 23 14:31:04 1998 From: frankwin at mrcyber.a2000.ml.org (MrCyber) Date: Fri, 23 Oct 1998 14:31:04 +0200 Subject: [Mailman-Users] Installing Mailman Message-ID: <005701bdfe81$0035bd00$0500600a@frankwin.a2000.ml.org> Hi there, I installed Mailman on my Debian 2.0 machine, but I can't seem to get it running correctly.... I read the README file which said I need the INSTALL file to read how to install mailman.. but guess what ? No INSTALL file there... so... HELP! Who can send me the INSTALL file ? Thnx in advance MrCyber -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1648 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-users/attachments/19981023/f0be2d35/attachment.bin From mailman at shell.daaave.org Sat Oct 24 09:25:00 1998 From: mailman at shell.daaave.org (Mailman account) Date: Sat, 24 Oct 1998 02:25:00 -0500 (CDT) Subject: [Mailman-Users] Errors running mmsitepass Message-ID: [mailman] ~/bin 1:49 % ./mmsitepass ******** Traceback (innermost last): File "./mmsitepass", line 27, in ? from Mailman import MailList File "/home/owner/mailman/Mailman/MailList.py", line 43, in ? from Mailman.Logging.StampedLogger import StampedLogger File "/home/owner/mailman/Mailman/Logging/StampedLogger.py", line 18, in ? from Logger import Logger File "/home/owner/mailman/Mailman/Logging/Logger.py", line 57 raise ^ SyntaxError: invalid syntax [mailman] ~/bin 1:49 % -------------------------------------------------------- This is right after a clean installation. 1) ./configure --prefix=/home/owner/mailman --with-cgi-gid=nogroup 2) make install nogroup is a valid group name, the mailman user's home directory is /home/owner/mailman. Also, I'm getting lots of errors off the cron jobs that all seem to end with that "raise" error with the caret under the e...don't know if there's a connection. There's nothing in /var/log/syslog that looks like it has anything to do with this. Configuration: Slackware 3.5 Linux 2.0.34 pretty vanilla install except for contents of my user account's home directory. Python 1.5 ( /usr/lib/python1.5, not /usr/local/lib/python1.5 ) This looks like I'm sending to a mailing list that I'm not subscribed to...if this is true, could replies please be directed to arno at daaave.org (the owner of the machine which mailman at daaave.org is associated with, this is me). Thanks in advance for any help you can provide. From philippe_perrier at focal.fr Mon Oct 26 12:56:51 1998 From: philippe_perrier at focal.fr (PERRIER Philippe (MLN)) Date: Mon, 26 Oct 1998 12:56:51 +0100 Subject: [Mailman-Users] add my name to your mailing list Message-ID: thank in advance regards Philippe PERRIER ------------------------------------------------------------- Philippe PERRIER FOCAL Ingenierie 15, Chemin du vieux Chene BP103 ZIRST 38243 Meylan Cedex Email : philippe_perrier at focal.fr Tel : 0476908648 ------------------------------------------------------------ From gstein at lyra.org Mon Oct 26 13:19:53 1998 From: gstein at lyra.org (Greg Stein) Date: Mon, 26 Oct 1998 04:19:53 -0800 Subject: [Mailman-Users] add my name to your mailing list References: Message-ID: <363468E9.1A73378C@lyra.org> PERRIER Philippe (MLN) wrote: > > thank in advance > regards > > Philippe PERRIER > ------------------------------------------------------------- > Philippe PERRIER > FOCAL Ingenierie > 15, Chemin du vieux Chene > BP103 ZIRST > 38243 Meylan Cedex > Email : philippe_perrier at focal.fr > Tel : 0476908648 > ------------------------------------------------------------ > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users at python.org > http://www.python.org/mailman/listinfo/mailman-users You can easily add yourself to the list by following the URL above. -g -- Greg Stein (gstein at lyra.org) From grin at tolna.net Tue Oct 27 02:47:30 1998 From: grin at tolna.net (Peter Gervai) Date: Tue, 27 Oct 1998 02:47:30 +0100 Subject: [Mailman-Users] unlock? please help with the filename... Message-ID: <19981027024730.R16641@mail.tolna.net> Hello... PLEASE someone tell me which file this routine tries to lock and how, and the process that show me the information next time when there's nobody to answer... Unfortunately I don't know Python, and I really don't have the time to completely learn a new language. Please Python gurus take a look at the code to figure out the filename (because the error log never contains variable values); and if there's any SIMPLE way to print variables or by any means debug the program: tell me the secret... Thank you in advance! Oct 27 02:39:07 1998 admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/var/lib/mailman/scripts/driver", line 97, in run_main admin: main() admin: File "../Mailman/Cgi/subscribe.py", line 95, in main admin: call_script('options', [list._internal_name, member]) admin: File "../Mailman/Cgi/subscribe.py", line 65, in call_script admin: list.Unlock() admin: AttributeError: Unlock bye, peter ps: the error is because SOME file have different owner or permission from what mailman expect. I just can't guess which one! pps: STILL holding the question: Anyone can tell which config files have to be writeble to the WWW UID, which to MAILMAN UID, and which to BOTH? tia, g From farul at cuccfa.ccc.columbia.edu Tue Oct 27 17:54:00 1998 From: farul at cuccfa.ccc.columbia.edu (Farul Ghazali) Date: Tue, 27 Oct 1998 11:54:00 -0500 (EST) Subject: [Mailman-Users] Sun recommended patches breaks python/mailman, help! Message-ID: I posted this on comp.lang.python, but thought I should post here too. I recently installed the Sun Recommended patches on my Solaris 2.5.1 x86 box, along with the Sun Year 2000 fixes for it. Unfortunately, this broke my mailing list server and I didn't realize it until about 2 weeks later (very quiet mailing list :) At first it seemed as if all the mail was bouncing back, so I backed out of the sendmail patch from Sun's huge patch cluster. Then mail was getting out, but nothing else worked. I'm running Python 1.5, with mailman 1.0b4 over Apache 1.3.0. The second thing I tried doing was upgrading everything (apache 1.3.3, Python 1.5.1 and mailman 1.0b5), which was a big mistake, since mailman 1.0b4 and 1.0b5 doesn't seem to work with Python 1.5.1 at all ( something about a CRYPT error even though I did compile in the crypt module). So I reverted back to Python 1.5 with mailman 1.0b4, which so far seems to work from the command line. However, I'm still having problems with the web server, accessing the admin page gives the following error Traceback (innermost last): File "/export/home2/mailman/scripts/admin", line 836, in ? main() File "/export/home2/mailman/scripts/admin", line 149, in main lst = maillist.MailList(list_name) File "/export/home2/mailman/Mailman/maillist.py", line 64, in __init__ self.Load() File "/export/home2/mailman/Mailman/maillist.py", line 546, in Load self.Lock() File "/export/home2/mailman/Mailman/maillist.py", line 887, in Lock self._lock_file = posixfile.open( File "/usr/local/lib/python1.5/posixfile.py", line 216, in open return _posixfile_().open(name, mode, bufsize) File "/usr/local/lib/python1.5/posixfile.py", line 81, in open return self.fileopen(__builtin__.open(name, mode, bufsize)) IOError: (13, 'Permission denied') Exception exceptions.AttributeError: '_file_' in ignored Accessing the listinfo page gives an Apache internal server error. I'm going to revert back to Apache 1.3.0, and if that doesn't work, backout of the multiple patches I installed for y2k and security. This seems somewhat drastic so I'd really appreciate any tips from anyone before doing this. Thanks much. From gunkel at phoenix.marymount.edu Wed Oct 28 16:16:42 1998 From: gunkel at phoenix.marymount.edu (Alvin Gunkel) Date: Wed, 28 Oct 1998 10:16:42 -0500 Subject: [Mailman-Users] Bug Message Message-ID: <3637355A.EC6821E7@phoenix.marymount.edu> Hello, I have installed mailman and Python 1.5.1 per instructions. When trying to access the subscribe program I get the following: 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 "/u1/mailman/scripts/driver", line 97, in run_main main() File "../Mailman/Cgi/subscribe.py", line 30, in main path = os.environ['PATH_INFO'] File "/usr/local/lib/python1.5/UserDict.py", line 12, in __getitem__ def __getitem__(self, key): return self.data[key] KeyError: PATH_INFO Environment variables: Variable Value HTTP_CONNECTION Keep-Alive HTTP_ACCEPT_ENCODING gzip REMOTE_HOST valkyrie.marymount.edu GATEWAY_INTERFACE CGI/1.1 PATH /usr/sbin:/usr/bin SERVER_PROTOCOL HTTP/1.0 SERVER_PORT 80 HTTP_HOST phoenix.marymount.edu REQUEST_METHOD GET SCRIPT_NAME /mailman/subscribe SERVER_URL http://phoenix.marymount.edu SERVER_SOFTWARE Netscape-Enterprise/3.5.1G HTTP_ACCEPT_LANGUAGE en HTTPS OFF PYTHONPATH /u1/mailman REMOTE_ADDR 199.111.97.97 HTTP_COOKIE MajorCool_ListSorted=1; MajorCool_InfoWrap=1; MajorCool_Conf2Column=1; MajorCool_GenJavaScript=1; MajorCool_GenMenuMode=1; MajorCool_BrowseOwnerless=0; MajorCool_GenMenuStart=(no pref); MajorCool_GenFontIncr=+3; MajorCool_GenFontFace=Helvetica; MajorCool_GenSubmitImages=1; MajorCool_GenCache=1; MajorCool_ConfHelp=1; MajorCool_GenScreenWidth=550; MajorCool_ListMaxSize=25000; MajorCool_ConfAll=1 SERVER_NAME phoenix.marymount.edu TZ US/Eastern HTTP_USER_AGENT Mozilla/4.5 [en] (Win98; U) HTTP_ACCEPT_CHARSET iso-8859-1,*,utf-8 HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* -- ******************************************************************************* Alvin Gunkel Systems Administrator Voice (703) 284-5950 Marymount University 2807 N. Glebe Rd. Internet gunkel at marymount.edu Arlington, VA 22207-4229 ******************************************************************************* From tomas at euronetics.se Wed Oct 28 17:09:29 1998 From: tomas at euronetics.se (Tomas Fasth) Date: Wed, 28 Oct 1998 17:09:29 +0100 Subject: [Mailman-Users] Sun recommended patches breaks python/mailman, help! Message-ID: <000f01be028d$5a2b1610$f6d52dc1@bishop.twinspot.net> Farul, If you want us to help you, you should try to provide a more detailed description of your problems. For example, what did the bounced messages look like, what kind of problem did they report? I have experienced problems myself running latest Mailman (checked out from cvs repository) when switching from Python 1.5 to 1.5.1. But I haven't had time to dive into that more deeply just yet. I currently do not run any live lists, so no pressure on me ;-) A vague guess regarding the Solaris sendmail would be that Sun's patch might have disabled "pipe" aliases which is used by Mailman to redirect incoming mail for processing. I also suspect that Sun have made a major update of their sendmail codebase to the latest version available on the net. This might cause you extra headache because of substantial changes in the configuration file. Anyway, making Mailman to work with a new version of sendmail seem to be of lesser magnitude compared to your problem related to different versions of Python interpreter and it's environment. By the way, I have done some work on creating a mailman mailer definition in sendmail. This removes the need for piped aliases but would of course require a modified configuration file for sendmail. It kind of works, but I wouldn't recommend to go live with it for the moment. >So I reverted back to Python 1.5 with mailman 1.0b4, which so far seems to >work from the command line. However, I'm still having problems with the >web server, accessing the admin page gives the following error > >Traceback (innermost last): [compressed] >IOError: (13, 'Permission denied') So, the web server aren't allowed to access a certain file. Normally the webserver and Mailman is running as different user id's. This is always a source of trouble if the permission and owner settings gets messed up on certain files. But I have no good advise on this, other than you should try to determine which file(s) is causing the problem and correct the file permission settings somehow. >I'm going to revert back to Apache 1.3.0, and if that doesn't work, >backout of the multiple patches I installed for y2k and security. This >seems somewhat drastic so I'd really appreciate any tips from anyone >before doing this. Try not to panic. You need those sec and y2k patches sooner or later anyway. I hardly think reverting to older apache releases will do you a bit good. The most probable cause for some of your problems might be that by making upgrades certain files get replaced which have already been tailored by you or other software installations. Thus the break down. In order to avoid this in the future we need to understand why things got broken in the first place. Your situation might help in that regard. Your real problem is that you're the one taking the first blow ;-) A standing recommendation for now seem to be: do not upgrade anything on live mailman installations. You have our full sympathy. ;-) Tomas From farul at cuccfa.ccc.columbia.edu Wed Oct 28 18:56:51 1998 From: farul at cuccfa.ccc.columbia.edu (Farul Ghazali) Date: Wed, 28 Oct 1998 12:56:51 -0500 (EST) Subject: [Mailman-Users] Sun recommended patches breaks python/mailman, help! In-Reply-To: <000f01be028d$5a2b1610$f6d52dc1@bishop.twinspot.net> Message-ID: On Wed, 28 Oct 1998, Tomas Fasth wrote: > So, the web server aren't allowed to access a certain file. Normally the > webserver and Mailman is running as different user id's. This is always a > source of trouble if the permission and owner settings gets messed up on > certain files. But I have no good advise on this, other than you should try > to determine which file(s) is causing the problem and correct the file > permission settings somehow. Somehow I figured out that this was a permissions problem, apparently the cgi-bin directory needs to have the set-gid bit set. > Your real problem is that you're the one taking the first blow ;-) A > standing recommendation for now seem to be: do not upgrade anything on live > mailman installations. You have our full sympathy. ;-) Thanks for the sympathy :) However, the situation seems to be normal for now, I went and got the latest cvs revisions, compiled a fresh copy of the latest python and apache. I did back out of the y2k patches however, so that's something I'm going to have to redo later in life :-) So, the conclusion is, get the latest revision of mailman (pre 1.0b6?) along with the latest versions of python/apache and it technically should work. Now I have to figure out why my damn console is coming out in all caps :-( From klm at cnri.reston.va.us Thu Oct 29 01:12:55 1998 From: klm at cnri.reston.va.us (Ken Manheimer) Date: Wed, 28 Oct 1998 19:12:55 -0500 (EST) Subject: [Mailman-Users] Bug Message In-Reply-To: <3637355A.EC6821E7@phoenix.marymount.edu> Message-ID: On Wed, 28 Oct 1998, Alvin Gunkel wrote: > I have installed mailman and Python 1.5.1 per instructions. When > trying to access the subscribe program I get the following: > > We're sorry, we hit a bug! > [...] > Traceback (innermost last): > File "/u1/mailman/scripts/driver", line 97, in run_main > main() > File "../Mailman/Cgi/subscribe.py", line 30, in main > path = os.environ['PATH_INFO'] > File "/usr/local/lib/python1.5/UserDict.py", line 12, in __getitem__ > def __getitem__(self, key): return self.data[key] > KeyError: PATH_INFO > > Environment variables: > [...] The environment variables listed, in fact, lack a PATH_INFO variable, which mailman depends upon. (What HTTP server are you using?) There is what may be an alternative: > SCRIPT_NAME > /mailman/subscribe which we could use as an alternative in our scripts for PATH_INFO, if it really is a substitute. Funny thing is, the variable either does not serve as i expect, or the value indicates that you entered an incorrect path, somewhere. My question for you is, how you are trying to get at the subscribe script? It is not supposed to be visited directly - you should be coming to it from a listinfo page for the list to which you're trying to subscribe. E.g., when subscribing to mailman-users at python.org, one visits: http://www.python.org/mailman/listinfo/mailman-users and enters the subscription info, then they hit the 'Subscribe' button. A that point the 'subscribe' script is visited - and then PATH_INFO should be set. If not, we'll look for a fallback setting - but i expect i would have heard of this problem before if the PATH_INFO is at all commonly left out... (In any case we may want to fix mailman so the script handle the situation better, directing the user to the right place instead of faulting.) Ken Manheimer klm at python.org 703 620-8990 x268 (orporation for National Research |nitiatives # If you appreciate Python, consider joining the PSA! # # . # From klm at cnri.reston.va.us Thu Oct 29 01:27:32 1998 From: klm at cnri.reston.va.us (Ken Manheimer) Date: Wed, 28 Oct 1998 19:27:32 -0500 (EST) Subject: [Mailman-Users] Sun recommended patches breaks python/mailman, help! In-Reply-To: Message-ID: On Wed, 28 Oct 1998, Farul Ghazali wrote: > On Wed, 28 Oct 1998, Tomas Fasth wrote: > > > [Guidance to help eke out the cause of farul's problem.] > > Somehow I figured out that this was a permissions problem, apparently the > cgi-bin directory needs to have the set-gid bit set. (This is currently taken care of in the 'make finish' section of the install, which is supposed to be run as root. I'm not sure if that was the case with whatever version you were working with.) > Thanks for the sympathy :) However, the situation seems to be normal for > now, I went and got the latest cvs revisions, compiled a fresh copy of the > latest python and apache. I did back out of the y2k patches however, so > that's something I'm going to have to redo later in life :-) > > So, the conclusion is, get the latest revision of mailman (pre 1.0b6?) > along with the latest versions of python/apache and it technically should > work. Now I have to figure out why my damn console is coming out in all > caps :-( Except for the apparent difficulties with the y2k patches (and the damn console caps - i think i'm going to wait until the end of 1999 before trying out the y2k patches...-), it's great news that the pre-1.0b6 install is working for you. And many thanks to tomas fasth for chipping in to help people. This really is the spirit of open source... Ken Manheimer klm at python.org 703 620-8990 x268 (orporation for National Research |nitiatives # If you appreciate Python, consider joining the PSA! # # . #