[Mailman-Users] Where's my mail?
I sent mail to [EMAIL PROTECTED] a few minutes ago, but it hasn't appeared on the list, it's not in the archives, and I haven't gotten any error messages, either. And I've tried mailq | grep suntalk, but it returns null. How should I troubleshoot this problem? Ben -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] help file
I've read in the Mailman FAQ that there is a help file that you can retrieve by requesting through email. Does this have to be set up separately? I've sent mail to the request address, with help in the subject line, but I do not receive any mail with the help instructions in them. Did I misunderstand something? Thanks in advance, Sandy -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] current moderator in a perl command
Is there a way to retrieve the current moderator through a perl command? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Error when accessing Mailman CGI web interface
Hi everyone, I'm trying to install a fresh copy of mailman 2.1.6 on a FC3 machine with SELinux disabled, and running into a problem trying to access the web interface. My configure statement looks like this: ./configure \ --prefix=/home/mailman/domains/chuckie.co.uk \ --with-username=mailman \ --with-groupname=mailman \ --with-cgi-gid=apache I then do a make install followed by bin/check_perms -f as noted in the manual. However when I try and access the administration URL at http://server/mailman/admin then I get the following error in the Apache error log: [Tue Dec 20 14:23:00 2005] [error] [client 213.152.63.90] /usr/bin/python: can't open file '/home/mailman/domains/chuckie.co.uk/scripts/driver' [Tue Dec 20 14:23:00 2005] [error] [client 213.152.63.90] Premature end of script headers: admin What is strange is that I also get the same error if do this: su - apache cd ~/domains/chuckie.co.uk/cgi-bin admin But the following appears to work as expected, outputting a CGI error: su - apache /usr/bin/python /home/mailman/domains/chuckie.co.uk/scripts/driver Any help would be greatly appreciated. Many thanks, Mark. WebBased Ltd 17 Research Way Plymouth PL6 8BT T: +44 (0)1752 797131 F: +44 (0)1752 791023 http://www.webbased.co.uk http://www.infomapper.com http://www.swtc.co.uk This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] help file
[EMAIL PROTECTED] wrote: I've read in the Mailman FAQ that there is a help file that you can retrieve by requesting through email. Does this have to be set up separately? I've sent mail to the request address, with help in the subject line, but I do not receive any mail with the help instructions in them. Did I misunderstand something? I don't know if you misunderstood or not. Did you get any reply? You don't have to set anything up for this to work. Do other mails to the list-request address work? Any mail to the list request address should produce a 'results of your email commands' return email. The RFC 2369 List-Help: header contains a mailto URI that should work. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's my mail?
Ben Ostrowsky wrote: I sent mail to [EMAIL PROTECTED] a few minutes ago, but it hasn't appeared on the list, it's not in the archives, and I haven't gotten any error messages, either. And I've tried mailq | grep suntalk, but it returns null. How should I troubleshoot this problem? Check the MTA log to see where the mail was delivered. Are the qrunners running? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's my mail?
See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp. Thanks -- it seems that the problem here is not actually with Mailman, as I can post to lists as long as I'm not in the building. I think I have to configure my main mail server, since in-house PCs deliver all their mail to mail.tblc.org (but machines outside the network have their own MTAs which sensibly deliver directly to lists.tblc.org as per the MX record). I've got mail.tblc.org set up to forward list mail, I think; /etc/aliases on the main mail server looks like this (for each list): youth: [EMAIL PROTECTED] youth-admin: [EMAIL PROTECTED] youth-bounces: [EMAIL PROTECTED] youth-confirm: [EMAIL PROTECTED] youth-join: [EMAIL PROTECTED] youth-leave: [EMAIL PROTECTED] youth-owner: [EMAIL PROTECTED] youth-request: [EMAIL PROTECTED] youth-subscribe: [EMAIL PROTECTED] youth-unsubscribe: [EMAIL PROTECTED] And I've run 'newaliases' already. So now I'm off to troubleshoot Postfix on the main mail server... Thanks again! Ben -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
Mark Cave-Ayland wrote: However when I try and access the administration URL at http://server/mailman/admin then I get the following error in the Apache error log: [Tue Dec 20 14:23:00 2005] [error] [client 213.152.63.90] /usr/bin/python: can't open file '/home/mailman/domains/chuckie.co.uk/scripts/driver' [Tue Dec 20 14:23:00 2005] [error] [client 213.152.63.90] Premature end of script headers: admin What is strange is that I also get the same error if do this: su - apache cd ~/domains/chuckie.co.uk/cgi-bin admin But the following appears to work as expected, outputting a CGI error: su - apache /usr/bin/python /home/mailman/domains/chuckie.co.uk/scripts/driver What happens if you do the above with su - mailman instead of apache. At this point, the wrapper is invoking the driver as group mailman because it is SETGID. Are you sure SELinux is disabled? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] removing a post before digest
Hi. is there a simple method that I can remove a post before a digest is triggered and not having it appear on the archives? Can this be done from the admin interface? also, is there a way to stop a digest from being released until I do this? Thanks! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: 20 December 2005 16:08 To: Mark Cave-Ayland; mailman-users@python.org Subject: Re: [Mailman-Users] Error when accessing Mailman CGI web interface (cut) What happens if you do the above with su - mailman instead of apache. At this point, the wrapper is invoking the driver as group mailman because it is SETGID. Are you sure SELinux is disabled? Hi Mark, The su - mailman version works without any problems, e.g. su - mailman cd ~/domains/chuckie.co.uk/cgi-bin ./admin Content-type: text/html head titleMailman CGI error!!!/title /headbody h1Mailman CGI error!!!/h1 The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: pre Group mismatch error. Mailman expected the CGI wrapper script to be executed as group apache, but the system's web server executed the CGI script as group mailman. Try tweaking the web server to run the script as group apache, or re-run configure, providing the command line option `--with-cgi-gid=mailman'./pre According to /etc/selinux/config: SELINUX=disabled SELINUXTYPE=targeted Looking at the mailman source, I guess that somehow the execve() call is failing but I'm not sure exactly where to start digging... Many thanks, Mark. WebBased Ltd 17 Research Way Plymouth PL6 8BT T: +44 (0)1752 797131 F: +44 (0)1752 791023 http://www.webbased.co.uk http://www.infomapper.com http://www.swtc.co.uk This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] confusing permission errors, help please
Hugh Esco wrote: I might need to do several instances of mailman before the new year, sailed right through my first install, but got stuck on the second one. I'm seeking advice on how to build this. Apparently I will need a distinct instance for each virtual host of the $prefix heirarchy. I'm wondering though if I can have only a single copy of the installation directory which is created from unpacking the tar ball. I'm not sure what you're saying. Yes, you can unpack the tarball only once into one source directory, but then for each mailman instance you'll have to run configure in that directory with completely separate --prefix (and --exec-prefix and --with-var-prefix if used) values followed by make install: for that instance. Also, I'm creating a unique vhost specific user for each instance of mailman. Is this overkill? Can a single mailman user support multiple vhosts? Yes. One mailman instance can support multiple vhosts. The restriction is that since a single mailman instance has only one 'namespace' for listnames, you can't have the same list name on two different vhosts supported by the same mailman instance. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.047.htp At any rate, to the error at hand: At: http://mumble.example.ca/mailman/listinfo Browser reports error as: Forbidden You don't have permission to access /mailman/listinfo on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. /var/log/apache/mumble-error.log says: [Mon Dec 19 22:43:27 2005] [error] [client nn.nnn.nn.nnn] (13)Permission denied: access to /mailman/listinfo denied permissions on directory and file are: drwxrwsr-x 2 mumble mumble 320 Dec 19 18:38 cgi-bin -rwxr-sr-x 1 mumble mumble 36637 Dec 19 18:38 cgi-bin/listinfo apache configuration (which works based on function of other aliases) includes: ScriptAlias /mailman/ /u/m/mumble/mailman/cgi-bin/ OK. I'm stumped. Have you run /u/m/mumble/mailman/bin/check_perms? I would think that perhaps adding the apache user to the mumble group might do it, but /etc/group shows that the instance of mailman I put up two days ago (another virtual host on the same gentoo server), which works, did not require that intervention. And I see that the permissions are 02755 on the script, so apache ought to be able to execute the script regardless. I agree. Do you perhaps have something in your Apache config that directly or indirectly removed the ExecCGI option from the /u/m/mumble/mailman/cgi-bin/ directory? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problems with archiving
I have just recently installed mailman and I am trying to get the archiving feature to work. I have gone into the archiving settings on two different test lists that I set up and told them both to do archiving. I set one to public and one to private, just to see how each one reacted. So far, not one message that I've sent to the list has been archived. I followed the setup instructions for getting the archiving to work but I think I must have missed something. I also found something in the FAQ that I added to the httpd.conf file but it still doesn't work. At first I think it was a permissions problem but I think I fixed that. Originally, the public directory was owned by root:other and the private was owned by nobody:nobody (the user/group that runs apache). I left the private alone and chown'd the public dir to mailman:mailman. In the httpd.conf file, I have the following lines: ScriptAlias /mailman/ /path/to/mailman/cgi-bin/ Alias /pipermail/ /path/to/mailman/archives/public/ Directory /path/to/mailman/archives/public/ AddDefaultCharset Off Options FollowSymLinks /Directory Does this seem correct? Am I missing something? Thanks. Josh -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
what does ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver say? what does /usr/sbin/getenforce say? -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
Mark Cave-Ayland wrote: The su - mailman version works without any problems, e.g. su - mailman cd ~/domains/chuckie.co.uk/cgi-bin ./admin I meant try su - mailman /usr/bin/python /home/mailman/domains/chuckie.co.uk/scripts/driver (or perhaps) /usr/bin/python /home/mailman/domains/chuckie.co.uk/scripts/driver admin -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
-Original Message- From: John Dennis [mailto:[EMAIL PROTECTED] Sent: 20 December 2005 16:32 To: Mark Cave-Ayland Cc: 'Mark Sapiro'; mailman-users@python.org Subject: Re: [Mailman-Users] Error when accessing Mailman CGI web interface what does ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver say? what does /usr/sbin/getenforce say? Hi John, Thanks for your help. This is what I get from the two commands above: $ ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver -rw-r--r-- 1 mailman mailman 9736 Dec 20 14:20 /home/mailman/domains/chuckie.co.uk/scripts/driver $ /usr/sbin/getenforce Disabled Many thanks, Mark. WebBased Ltd 17 Research Way Plymouth PL6 8BT T: +44 (0)1752 797131 F: +44 (0)1752 791023 http://www.webbased.co.uk http://www.infomapper.com http://www.swtc.co.uk This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] removing a post before digest
Mister Time wrote: is there a simple method that I can remove a post before a digest is triggered and not having it appear on the archives? It's already in the archives by the time you see it. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.003.htp for info about removal. You can edit the lists/list_name/digest.mbox file before the digest is produced and remove the post. This will keep it out of the digest. To do this safely, first stop mailman (bin/mailmanctl stop), then edit digest.mbox, then start mailman. This will prevent additional posts from being processed while you're editing and perhaps being lost from the digest. It will also prevent a digest being triggered by size. To prevent a periodic digest, remove the senddigests entry from mailman's crontab. Can this be done from the admin interface? No. also, is there a way to stop a digest from being released until I do this? See above. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: 20 December 2005 16:38 To: Mark Cave-Ayland; mailman-users@python.org Subject: RE: [Mailman-Users] Error when accessing Mailman CGI web interface (cut) I meant try su - mailman /usr/bin/python /home/mailman/domains/chuckie.co.uk/scripts/driver (or perhaps) /usr/bin/python /home/mailman/domains/chuckie.co.uk/scripts/driver admin Hi Mark, Sorry for the misunderstanding. Both of the /usr/bin/python ... lines above work without any problems, using either the mailman user or the apache user. Many thanks, Mark. WebBased Ltd 17 Research Way Plymouth PL6 8BT T: +44 (0)1752 797131 F: +44 (0)1752 791023 http://www.webbased.co.uk http://www.infomapper.com http://www.swtc.co.uk This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
On Tue, 2005-12-20 at 16:42 +, Mark Cave-Ayland wrote: Thanks for your help. This is what I get from the two commands above: $ ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver -rw-r--r-- 1 mailman mailman 9736 Dec 20 14:20 /home/mailman/domains/chuckie.co.uk/scripts/driver $ /usr/sbin/getenforce Disabled Then I don't think I can help :-( Your original post said the you built mailman with uid=gid=mailman and the wrapper seems to be executing correctly based on a subsequent post. All looks good from here. Here is the sequence that should be happening, see if you can find any reason why its not: apache invokes the cgi wrapper as the user 'apache', the cgi wrapper verifies it was called by apache, then the wrapper does a setgid to mailman and invokes the driver script, the driver script should be group mailman, so it should have no problems reading the driver script, but that is what is failing, go figure, seems like it should work. -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problems with archiving
Josh Greenberg wrote: At first I think it was a permissions problem but I think I fixed that. Originally, the public directory was owned by root:other and the private was owned by nobody:nobody (the user/group that runs apache). I left the private alone and chown'd the public dir to mailman:mailman. This is probably at least part of the problem. The private directory must be group writable and group 'mailman'. In the httpd.conf file, I have the following lines: ScriptAlias /mailman/ /path/to/mailman/cgi-bin/ Alias /pipermail/ /path/to/mailman/archives/public/ Directory /path/to/mailman/archives/public/ AddDefaultCharset Off Options FollowSymLinks /Directory Does this seem correct? Yes. Am I missing something? Thanks. Can you go to either archive from the web and see the 'No messages have been posted to this list yet' page? Try running bin/check_perms to be sure the ownership/permissions are OK. The 'mailman' group has to be able to write everywhere in the archives/private structure. Are messages being collected in archives/private/listname.mbox/listname.mbox? Are the permissions = 02775 and group = 'mailman' on the archives/private/listname.mbox/ directories? Have you overridden any of the Archive defaults in mm_cfg.py? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
Mark Cave-Ayland wrote: Sorry for the misunderstanding. Both of the /usr/bin/python ... lines above work without any problems, using either the mailman user or the apache user. I know you said you rean check_perms, but verify that all the scripts in cgi-bin/ are SETGID and group mailman. BTW, does the listinfo page work? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] can moderators add moderators?
Is there a way that a moderator can change the current moderator? For example, if I have 3 moderators and current moderator is going out of town, can the current moderator assign the moderator job to one of the other moderators? Thanks, S -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] can moderators add moderators?
[EMAIL PROTECTED] wrote: Is there a way that a moderator can change the current moderator? For example, if I have 3 moderators and current moderator is going out of town, can the current moderator assign the moderator job to one of the other moderators? If the moderator knows the list admin password, she can change moderators. If she only knows the list moderator password, she can only use the admindb interface for moderation, she can't use the admin interface. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.060.htp -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] removing a post before digest
does anyone know where mailman resides on a server after it has been created by cpanel? I have root access, but can not find it. Thanks. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Topics wildcards
Can any type of wildcards (*) be used in the topics Regexp: area? I would like to add a topic to include all message that do not belong to a topic, how can I do this? S -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Topics wildcards
[EMAIL PROTECTED] wrote: Can any type of wildcards (*) be used in the topics Regexp: area? I would like to add a topic to include all message that do not belong to a topic, how can I do this? These are Python regexps. See http://docs.python.org/lib/re-syntax.html. But why do you want to do this? Users can already choose whether or not to receive messages that don't match any topic. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] confusing permission errors, help please
Mr. Sapiro: Thank you sir, for your help. Yes, I ran check_perms with and without -f as root until I got good results. I've now added the following stanza to my vhost.conf file: Directory /u/m/mumble/mailman/cgi-bin/ Options ExecCGI SetHandler cgi-script /Directory I don't know what would have undone that. That stanza is not needed apparently in the other vhost I have. Perhaps, since this is a third level domain, I ought to check the conf file for its second level configuration. I had started setting up mailman (and a couple of other applications) in my apache config file, before the third level was delegates to me. I commented all of those out and still get the same errors in the browser: Forbidden You don't have permission to access /mailman/listinfo on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. The apache error log for mumble still says: [Tue Dec 20 13:29:44 2005] [error] [client nnn.nnn.nnn.nnn] (13)Permission denied: access to /mailman/listinfo denied Your answer about using a single user for every instance of mailman didn't indicate if I was actually going overboard by creating instance specific users for each installation. I have paired up user1 with mumble1, user2 with mumble2, etc., as an added security barrier and to protect users and their archives from one another. Will it run this way? Is that necessary? If I use a single source directory, yet install in multiple installation directories, each serving its own vhost, can two instances share a listname so I can have [EMAIL PROTECTED] and another at [EMAIL PROTECTED] -- Hugh On Tue, 20 Dec 2005 08:31:47 -0800 Mark Sapiro [EMAIL PROTECTED] wrote: Hugh Esco wrote: I might need to do several instances of mailman before the new year, sailed right through my first install, but got stuck on the second one. I'm seeking advice on how to build this. Apparently I will need a distinct instance for each virtual host of the $prefix heirarchy. I'm wondering though if I can have only a single copy of the installation directory which is created from unpacking the tar ball. I'm not sure what you're saying. Yes, you can unpack the tarball only once into one source directory, but then for each mailman instance you'll have to run configure in that directory with completely separate --prefix (and --exec-prefix and --with-var-prefix if used) values followed by make install: for that instance. Also, I'm creating a unique vhost specific user for each instance of mailman. Is this overkill? Can a single mailman user support multiple vhosts? Yes. One mailman instance can support multiple vhosts. The restriction is that since a single mailman instance has only one 'namespace' for listnames, you can't have the same list name on two different vhosts supported by the same mailman instance. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.047.htp At any rate, to the error at hand: At: http://mumble.example.ca/mailman/listinfo Browser reports error as: Forbidden You don't have permission to access /mailman/listinfo on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. /var/log/apache/mumble-error.log says: [Mon Dec 19 22:43:27 2005] [error] [client nn.nnn.nn.nnn] (13)Permission denied: access to /mailman/listinfo denied permissions on directory and file are: drwxrwsr-x 2 mumble mumble 320 Dec 19 18:38 cgi-bin -rwxr-sr-x 1 mumble mumble 36637 Dec 19 18:38 cgi-bin/listinfo apache configuration (which works based on function of other aliases) includes: ScriptAlias /mailman/ /u/m/mumble/mailman/cgi-bin/ OK. I'm stumped. Have you run /u/m/mumble/mailman/bin/check_perms? I would think that perhaps adding the apache user to the mumble group might do it, but /etc/group shows that the instance of mailman I put up two days ago (another virtual host on the same gentoo server), which works, did not require that intervention. And I see that the permissions are 02755 on the script, so apache ought to be able to execute the script regardless. I agree. Do you perhaps have something in your Apache config that directly or indirectly removed the ExecCGI option from the /u/m/mumble/mailman/cgi-bin/ directory? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- RCK Computer Services http://reclaimedcomputers.ca/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives:
[Mailman-Users] scrubbing/posting attachments?
(Don't know whether this post belongs in the development list or not ...) (I know very little about Mailman at this point, am just trying to gather some information.) We would very much like to be able to configure Mailman to strip certain attachments, but rather than deleting them entirely have them posted to a temporary or archived location and have the attachment replaced by a link to that location. (The point would be to allow users to send useful attachments to the list (e.g. Excel files etc.) without hammering the mail server.) It seems that Mailman already does something very much like this for archiving purposes. Is it imaginable that the existing code could be hacked/adapted to allow this behavior? sincerely Ben Bolker -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange Email
Jess Mooers wrote: I recently started receiving the following email: == Forwarded Message == Date: 12/20/05 1:45 PM Received: 12/20/05 2:12 PM -0600 From: Cron Daemon [EMAIL PROTECTED] To: [EMAIL PROTECTED] /usr/bin/python: can't open file '/Applications/mailman/cron/gate_news' == End Forwarded Message == I understand why I am getting the message, as the path is invalid, but I have a few questions. 1. Where is the email generated? By the cron daemon when it attempts to run the command. 2. Can I change the address it is sent to (my domain has changed)? Yes. See 'man cron' 'man crontab' and 'man 5 crontab' 3. Where is the path defined as 'Applications/mailman/cron/gate_news' so I can change it? In some crontab. Normally, it's the mailman user's crontab which is possibly /var/spool/cron/mailman, but is installed/maintained by 'crontab' - see 'man crontab'. However, the fact that results/errors are apparently being mailed to 'root' and not 'mailman' says this may be a crontab installed in /etc/cron.d. These are a slightly different format as they have an additional field between the times/days and the command which contains the user under which to run the command. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] scrubbing/posting attachments?
Ben Bolker wrote: We would very much like to be able to configure Mailman to strip certain attachments, but rather than deleting them entirely have them posted to a temporary or archived location and have the attachment replaced by a link to that location. (The point would be to allow users to send useful attachments to the list (e.g. Excel files etc.) without hammering the mail server.) It seems that Mailman already does something very much like this for archiving purposes. Is it imaginable that the existing code could be hacked/adapted to allow this behavior? Mailman 2.1.6 and above also does this for regular posts if you set the list's scrub_nondigest attribute to Yes. You can also make the default for new lists = Yes by putting DEFAULT_SCRUB_NONDIGEST = Yes in mm_cfg.py. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] can't see icons
I can't see any icons, just the placeholders and labels for them, when I open Mailman. How do I direct Apache2 and Mailman to see where the icons reside so that Mailman can properly display them? Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Way to reset list Admin password?
I replaced an older server today with a new Mac OS X XServe. I moved my mailman lists and I see then in the Server Admin. but when I try and access them via the Mailman web page UI, I get a Authorization failed error when I try to enter my list moderator password. I found this in the archive and willing to give it a try, but wanted to see 1) Is this the right way to go? 2) Other suggestions? http://www.mail-archive.com/mailman-users@python.org/msg34242.html Old Server: Mac OS X Server 10.4.4/ G4 tower; Mailman 2.1.5 New Server: Mac OS X Server 10.4.4/ G5 XServe; Mailman 2.1.5 NOTE: new email address -- Thomas Waters Director of Information and Communication Services University of Pittsburgh School of Pharmacy 412-383-7471 [EMAIL PROTECTED] http://www.pharmacy.pitt.edu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Way to reset list Admin password?
Thomas Waters wrote: I replaced an older server today with a new Mac OS X XServe. I moved my mailman lists and I see then in the Server Admin. but when I try and access them via the Mailman web page UI, I get a Authorization failed error when I try to enter my list moderator password. If you literally mean what you said, you're not supposed to be able to access the list's 'admin' interface with the 'moderator' password. You can only access the 'admindb' interface with the 'moderator' password. The 'admin' interface requires the list's 'administrator' password or the Mailman installation's 'site' password. I expect though that when you say 'moderator' you probably mean 'administrator' I found this in the archive and willing to give it a try, but wanted to see 1) Is this the right way to go? 2) Other suggestions? http://www.mail-archive.com/mailman-users@python.org/msg34242.html This is one way to proceed. The other is to log on to the list's admin interface with the site password and change the list administrator password via the admin-Passwords page. You can use bin/mmsitepass to set a new site password. It just occurs to me that maybe you've been using the site password all along, and you didn't move data/adm.pw to the new server. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] can't see icons
Dr. Scott S. Jones wrote: I can't see any icons, just the placeholders and labels for them, when I open Mailman. How do I direct Apache2 and Mailman to see where the icons reside so that Mailman can properly display them? What I do is copy them to apache's icons directory as described in http://www.list.org/mailman-install/node10.html. I believe Apache aliases this directory to /icons/ by default, so no mm_cfg.py change to the default IMAGE_LOGOS = '/icons/' is required. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] apache config issue?
Mr. Sapiro: Thank you sir, for your help. Yes, I ran check_perms with and without -f as root until I got good results. I've now added the following stanza to my vhost.conf file: Directory /u/m/mumble/mailman/cgi-bin/ Options ExecCGI SetHandler cgi-script /Directory I don't know what would have undone that. That stanza is not needed apparently in the other vhost I have. Perhaps, since this is a third level domain, I ought to check the conf file for its second level configuration. I had started setting up mailman (and a couple of other applications) in my apache config file, before the third level was delegates to me. I commented all of those out and still get the same errors in the browser: Forbidden You don't have permission to access /mailman/listinfo on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. The apache error log for mumble still says: [Tue Dec 20 13:29:44 2005] [error] [client nnn.nnn.nnn.nnn] (13)Permission denied: access to /mailman/listinfo denied Your answer about using a single user for every instance of mailman didn't indicate if I was actually going overboard by creating instance specific users for each installation. I have paired up user1 with mumble1, user2 with mumble2, etc., as an added security barrier and to protect users and their archives from one another. Will it run this way? Is that necessary? If I use a single source directory, yet install in multiple installation directories, each serving its own vhost, can two instances share a listname so I can have [EMAIL PROTECTED] and another at [EMAIL PROTECTED] -- Hugh On Tue, 20 Dec 2005 08:31:47 -0800 Mark Sapiro [EMAIL PROTECTED] wrote: Hugh Esco wrote: I might need to do several instances of mailman before the new year, sailed right through my first install, but got stuck on the second one. I'm seeking advice on how to build this. Apparently I will need a distinct instance for each virtual host of the $prefix heirarchy. I'm wondering though if I can have only a single copy of the installation directory which is created from unpacking the tar ball. I'm not sure what you're saying. Yes, you can unpack the tarball only once into one source directory, but then for each mailman instance you'll have to run configure in that directory with completely separate --prefix (and --exec-prefix and --with-var-prefix if used) values followed by make install: for that instance. Also, I'm creating a unique vhost specific user for each instance of mailman. Is this overkill? Can a single mailman user support multiple vhosts? Yes. One mailman instance can support multiple vhosts. The restriction is that since a single mailman instance has only one 'namespace' for listnames, you can't have the same list name on two different vhosts supported by the same mailman instance. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.047.htp At any rate, to the error at hand: At: http://mumble.example.ca/mailman/listinfo Browser reports error as: Forbidden You don't have permission to access /mailman/listinfo on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. /var/log/apache/mumble-error.log says: [Mon Dec 19 22:43:27 2005] [error] [client nn.nnn.nn.nnn] (13)Permission denied: access to /mailman/listinfo denied permissions on directory and file are: drwxrwsr-x 2 mumble mumble 320 Dec 19 18:38 cgi-bin -rwxr-sr-x 1 mumble mumble 36637 Dec 19 18:38 cgi-bin/listinfo apache configuration (which works based on function of other aliases) includes: ScriptAlias /mailman/ /u/m/mumble/mailman/cgi-bin/ OK. I'm stumped. Have you run /u/m/mumble/mailman/bin/check_perms? I would think that perhaps adding the apache user to the mumble group might do it, but /etc/group shows that the instance of mailman I put up two days ago (another virtual host on the same gentoo server), which works, did not require that intervention. And I see that the permissions are 02755 on the script, so apache ought to be able to execute the script regardless. I agree. Do you perhaps have something in your Apache config that directly or indirectly removed the ExecCGI option from the /u/m/mumble/mailman/cgi-bin/ directory? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- RCK Computer Services http://reclaimedcomputers.ca/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives:
Re: [Mailman-Users] confusing permission errors, help please
Hugh Esco wrote: The apache error log for mumble still says: [Tue Dec 20 13:29:44 2005] [error] [client nnn.nnn.nnn.nnn] (13)Permission denied: access to /mailman/listinfo denied So apparently, adding Directory /u/m/mumble/mailman/cgi-bin/ Options ExecCGI SetHandler cgi-script /Directory didn't fix it. I would have added Options +ExecCGI, but that probably won't help either. The 403 Forbidden error was encountered while trying to use an ErrorDocument seems to say there is something wrong with this virtual host. Are you by any chance using suEXEC with this virtual host? Are you running SELinux? If suEXEC, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.017.htp Your answer about using a single user for every instance of mailman didn't indicate if I was actually going overboard by creating instance specific users for each installation. I have paired up user1 with mumble1, user2 with mumble2, etc., as an added security barrier and to protect users and their archives from one another. Will it run this way? Is that necessary? Yes, it will run that way. If you don't need the ability to have the same list name on separate hosts, then this is probably overkill. if you're asking is having a separate user per Mailman instance overkill vs. having multiple, distinct instances all with the same user, having separate users would allow giving the actual virtual host clients more control over/visibility into their own Mailman without allowing them to impact others. This may be useful. The alternative protection is to have restrictive enough permissions so the individual virtual host users don't have shell access to their Mailman at all. If I use a single source directory, yet install in multiple installation directories, each serving its own vhost, can two instances share a listname so I can have [EMAIL PROTECTED] and another at [EMAIL PROTECTED] Yes, and that is the major reason for doing it this way. If you don't need this ability, you can probably do just fine with a single mailman instance with Mailman's virtual host support. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] confusing permission errors, help please
I added the + sign, restarted the apache server and still got the same errors in the borwser and apache log: Permission denied: access to /mailman/listinfo denied. I'm running gentoo (not SELinux) on this server, while my experience is with debian. A choice made by others, I'm afraid. So in the mean time, I'm groping. I just took a quick scan at the suEXEC docs on the apache2 site. But I have no previous familiarity with it. Nor am I sure how I might determine if apache was compiled with it. Looking at my configuration files with grep suEXEC -R /etc/apache2/* yielded an empty result set. As an experiment, I'll try the advise for suEXEC. If it doesn't get me anywhere, I'll back it out. -- Hugh On Tue, 20 Dec 2005 15:52:37 -0800 Mark Sapiro [EMAIL PROTECTED] wrote: Hugh Esco wrote: The apache error log for mumble still says: [Tue Dec 20 13:29:44 2005] [error] [client nnn.nnn.nnn.nnn] (13)Permission denied: access to /mailman/listinfo denied So apparently, adding Directory /u/m/mumble/mailman/cgi-bin/ Options ExecCGI SetHandler cgi-script /Directory didn't fix it. I would have added Options +ExecCGI, but that probably won't help either. The 403 Forbidden error was encountered while trying to use an ErrorDocument seems to say there is something wrong with this virtual host. Are you by any chance using suEXEC with this virtual host? Are you running SELinux? If suEXEC, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.017.htp Your answer about using a single user for every instance of mailman didn't indicate if I was actually going overboard by creating instance specific users for each installation. I have paired up user1 with mumble1, user2 with mumble2, etc., as an added security barrier and to protect users and their archives from one another. Will it run this way? Is that necessary? Yes, it will run that way. If you don't need the ability to have the same list name on separate hosts, then this is probably overkill. if you're asking is having a separate user per Mailman instance overkill vs. having multiple, distinct instances all with the same user, having separate users would allow giving the actual virtual host clients more control over/visibility into their own Mailman without allowing them to impact others. This may be useful. The alternative protection is to have restrictive enough permissions so the individual virtual host users don't have shell access to their Mailman at all. If I use a single source directory, yet install in multiple installation directories, each serving its own vhost, can two instances share a listname so I can have [EMAIL PROTECTED] and another at [EMAIL PROTECTED] Yes, and that is the major reason for doing it this way. If you don't need this ability, you can probably do just fine with a single mailman instance with Mailman's virtual host support. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- RCK Computer Services http://reclaimedcomputers.ca/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] confusing permission errors, help please
Hugh Esco wrote: As an experiment, I'll try the advise for suEXEC. If it doesn't get me anywhere, I'll back it out. It doesn't matter whether Apache was compiled with it. If you do NOT have an SuexecUserGroup directive in your virtual host or globally in your Apache configuration, then this is not the issue in your case. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] removing a post before digest
Mister Time wrote: does anyone know where mailman resides on a server after it has been created by cpanel? You might have better luck following the advice in http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman vs. Apache - please help
Hi folks, I have the latest versions of Apache and Cygwin installed on my WinXP machine. Under Cygwin, I have Exim installed (and working), and Mailman (build and installed). I cannot get Mailman to co-operate with Apache. Following this advice: http://www.python.org/cgi-bin/faqw-mm.py?req=all#5.2 I made a user called mailman which is a member of a group mm, then configured and installed mailman with these. I ran check_perms and all permissions are OK. This is in my Apache config: ScriptAlias /mailman C:/cygwin/usr/local/mailman/cgi-bin Directory C:/cygwin/usr/local/mailman/cgi-bin/ Order allow,deny Allow from all /Directory When I attempt to access Mailman from my brower, eg. http://ahualoa.net/mailman/admin.exe I get: Mailman CGI error!!! Group mismatch error. Mailman expected the CGI wrapper script to be executed as group mm, but the system's web server executed the CGI script as group Administrators. Try tweaking the web server to run the script as group mm, or re-run configure, providing the command line option `--with-cgi-gid=Administrators'. Does this really mean I have to force Apache to run as a user in the mm group? From what I know of Apache, that means forcing it with suEXEC which is really horribly messy. There is this advice in the GNU Mailman - Installation Manual, section 10: Warning: You want to be very sure that the user id under which your CGI scripts run is NOT in the mailman group you created above, otherwise private archives will be accessible to anyone. This seems to directly contradict the Mailman CGI error message - do I need to run the mailman CGI scripts as mailman.mm, or not? Thanks for any help, advice or pointers! -Ben -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman vs. Apache - please help
Ben wrote: I get: Mailman CGI error!!! Group mismatch error. Mailman expected the CGI wrapper script to be executed as group mm, but the system's web server executed the CGI script as group Administrators. Try tweaking the web server to run the script as group mm, or re-run configure, providing the command line option `--with-cgi-gid=Administrators'. Does this really mean I have to force Apache to run as a user in the mm group? From what I know of Apache, that means forcing it with suEXEC which is really horribly messy. No. You don't need (or want) suEXEC. The above message indicates that you configured mailman with --with-cgi-gid=mm. This is not what you wanted to do as it requires you to have Apache run the cgi-bin wrappers as group 'mm' (which I think you could do with User and Group directives rather than suEXEC, but you don't want to anyway). What you need is just what it says. Rerun configure with --with-cgi-gid=Administrators instead of --with-cgi-gid=mm (and the rest of the options the same as before) and then run 'make install'. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] confusing permission errors, help please
It didn't matter. I backed it out. I then replicated my apache.conf vhost definition as gibberish.validdomain.org, where the vhost file for validdomain includes the first working mailman installation. This time, I got a working listinfo page reporting no lists for gibberish.validdomain.org. This is so even though I had not and still have not built and configured an instance of mailman as suggested by the apache config file. This suggests to me some relationship between my control of a second level domain, in the case of the working examples, and my efforts to configure for a third level name in the example which is giving me fits. -- Hugh On Tue, 20 Dec 2005 16:48:33 -0800 Mark Sapiro [EMAIL PROTECTED] wrote: Hugh Esco wrote: As an experiment, I'll try the advise for suEXEC. If it doesn't get me anywhere, I'll back it out. It doesn't matter whether Apache was compiled with it. If you do NOT have an SuexecUserGroup directive in your virtual host or globally in your Apache configuration, then this is not the issue in your case. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- RCK Computer Services http://reclaimedcomputers.ca/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman under Cygwin - won't add list
Hi folks, Aside from the Apache problem, I can't seem to get Mailman to create a list. This is on Cygwin. I give the command: $ newlist friends Enter the email of the person running the list: [EMAIL PROTECTED] Initial friends password: Create a new, unpopulated mailing list. Usage: /usr/local/mailman/bin/newlist [options] [listname [listadmin-addr [admin- password]]] Options: (...a whole bunch of explanation...) Illegal list name: [EMAIL PROTECTED] Now, LittleGuy is just the name of my local host; it's not the fully-qualified domain. I don't know why Mailman is trying to use it, but I figured that I could force it otherwise: $ newlist --urlhost=ahualoa.net --emailhost=ahualoa.net [EMAIL PROTECTED] Enter the email of the person running the list: [EMAIL PROTECTED] Initial friends password: () Illegal list name: [EMAIL PROTECTED] This doesn't make any sense at all. I'm telling Mailman very explicitly which domain to create the list on. Why is Mailman still trying to use my local hostname? Thanks, Ben -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] confusing permission errors, help please
That's a never mind. Turns out I missed the forest while looking at the trees. the mailman/cgi-bin/'s permissions were fine, but the mode on a directory a level or so up were too restrictive to let apache look that deep to read what was inside. a chmod 02775 fixed that and I now can browse to the mailman instance. Thanks for your ideas and help. Thanks for a great product. -- Hugh On Tue, 20 Dec 2005 17:37:50 -0800 Hugh Esco [EMAIL PROTECTED] wrote: It didn't matter. I backed it out. I then replicated my apache.conf vhost definition as gibberish.validdomain.org, where the vhost file for validdomain includes the first working mailman installation. This time, I got a working listinfo page reporting no lists for gibberish.validdomain.org. This is so even though I had not and still have not built and configured an instance of mailman as suggested by the apache config file. This suggests to me some relationship between my control of a second level domain, in the case of the working examples, and my efforts to configure for a third level name in the example which is giving me fits. -- Hugh On Tue, 20 Dec 2005 16:48:33 -0800 Mark Sapiro [EMAIL PROTECTED] wrote: Hugh Esco wrote: As an experiment, I'll try the advise for suEXEC. If it doesn't get me anywhere, I'll back it out. It doesn't matter whether Apache was compiled with it. If you do NOT have an SuexecUserGroup directive in your virtual host or globally in your Apache configuration, then this is not the issue in your case. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- RCK Computer Services http://reclaimedcomputers.ca/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/he%40reclaimedcomputers.ca Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- RCK Computer Services http://reclaimedcomputers.ca/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
