Re: [Mailman-Users] Approve all held?
Mark Sapiro пишет: > Алексей Алтухов wrote: >> Mark Sapiro wrote: >>> Alexei Altuhov wrote: >>> Unfortunately I don't have access to the web interface, because of the Group mismatch error. >>> >>> We can help you fix that. How did you install Mailman? From our source >>> or from a vendors package? >>> >>> Give us the details, and we'll try to help. >>> >>> >> Mailman has been installed by one of our admins from the repository, as >> usual. > > > This seems to say you installed someone's package from a package > repository as opposed to installing from our source. > > >> The thing is, that he has installed Asterix afterwards and as I >> understood from now on all cgi scripts are run from the asterix group >> rather than the mailman one. >> >> Is it possible to change that or divide, which cgi scripts will be >> executed from the mailman group and which ones from the mailman - I >> couldn't figure out by myself and that left me with the command line >> administration. > > > If you installed from source, the way to fix this is to re-run configure > with the addition of the option "--with-cgi-gid=asterix" and then run > "make install". The alternative is to configure the web server (is this > Asterix?) to run the Mailman CGI wrappers as the group they expect, but > I gather this is not possible in your case. > > Most packaged versions of Mailman have a way to tell the CGI wrappers > what group to expect, but how you do that is specific to the package. > You need to ask the packager. I.e., if this is a RedHat or CentOS rpm, > ask on a RedHat list or see other RedHat support resources; if Debian or > Ubuntu, check those support resources, etc. > Sorry for misspelling the name of the SW: it's Asterisk, open source PBX. And the web server is Apache 2.x. I learned from the beginning, that if Mailman is installed from source it would have been easier to cope with the group mismatch problem, but... Admin installed Mailman from the RHEL rpm, so, thanks for the pointer, I'll try to find answers from that community. (I knew it's good I subscribed to CentOS list earlier! =) ) Thanks again, all the best, Alexei. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Internal 500 Error (Ubuntu jaunty / Mailman 2.1.12/ Python 2.6.2)
On Tue, Jun 23, 2009 at 5:10 AM, Mark Sapiro wrote: > > The OP and I had a conversation on the #mailman channel at freenode. We > determined that he could successfully run > > sudo -u www-data /bin/sh -c "PATH_INFO=;export > PATH_INFO;HTTP_HOST=www.example.com;export > HTTP_HOST;REQUEST_METHOD=GET;export REQUEST_METHOD; > /usr/local/mailman/cgi-bin/listinfo" > > (with appropriate changes to host and path) from the command line and > the listinfo CGI would produce appropriate output, so the problem is > apparently some issue with the way apache is (or isn't) invoking the > CGI. The OP says suEXEC is not involved, and I had no other ideas. > I spent some time with Apache guys and they said the way the script is being executed doesn't tell us everything and that I should simply run it without setting up environments, etc. When I do, I get the same result (500 internal error). I tried setting up ScriptLog to see what is going on, but since it's a binary, it doesn't produce any logs out of it. I ran 'ldd' on 'listinfo' and 'admin', etc. to see if I'm missing any libraries, which I am not. I'm just stuck here. Derek -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] free Mailman hosting
<> Keep in mind Antonio, you get EXACTLY what you 'pay' for!! Ed Please visit MY site at: www.justbrits.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Internal 500 Error (Ubuntu jaunty / Mailman 2.1.12/ Python 2.6.2)
Dev Guy wrote: >Hi, >I've tried to look this up on the lists, forums, etc. but have failed to >find anything that resolves this issue, so forgive me if I have missed a >solution mentioned elsewhere. > >I have recently upgraded my Ubuntu distribution to Jaunty. This upgrade >included an upgrade on Mailman, Python and Apache2. > >I'm currently running the following versions: > >ii apache2 2.2.11-2ubuntu2.1 >Apache HTTP Server metapackage >ii apache2-mpm-prefork 2.2.11-2ubuntu2.1 >Apache HTTP Server - traditional non-threade >ii python2.6 2.6.2-0ubuntu1 > An interactive high-level object-oriented la >ii listadmin 2.40-2.2 > command line mailman moderator queue manipul >ii mailman 1:2.1.12-1 > Powerful, web-based mailing list manager > >I have looked through the logs, but nothing seems to indicate anything >special, aside from the expressive line: > > >Premature end of script headers: admin > > >In my Apache2 error log file (turned logging to 'debug' level). > >Running the 'admin' or 'listinfo' scripts from the shell gives me this: > > ># ./listinfo >Content-type: text/html > >Bug in Mailman version 2.1.12 >Bug in Mailman version 2.1.12 >We're sorry, we hit a bug! > >Please inform the webmaster for this site of this >problem. Printing of traceback and other system information has been >explicitly inhibited, but the webmaster can find this information in the >Mailman error logs. >- > >I ran 'check_perms' and while there were errors it found, they were all >fixed. This had no effect on the problem. Mailman appears to be operational >otherwise. Emails are sent and received without issues. I can admin the site >using the 'listadmin' tools. However, the web interface is completely >broken. > >What am I missing? The OP and I had a conversation on the #mailman channel at freenode. We determined that he could successfully run sudo -u www-data /bin/sh -c "PATH_INFO=;export PATH_INFO;HTTP_HOST=www.example.com;export HTTP_HOST;REQUEST_METHOD=GET;export REQUEST_METHOD; /usr/local/mailman/cgi-bin/listinfo" (with appropriate changes to host and path) from the command line and the listinfo CGI would produce appropriate output, so the problem is apparently some issue with the way apache is (or isn't) invoking the CGI. The OP says suEXEC is not involved, and I had no other ideas. -- Mark Sapiro 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] footers and members of the list
Hal Huntley wrote: > >Thank you for that information. I gave that URL idea a try and if I >happened to be logged in as a list administrator for a list, I got a list of >members. I also tried getting a roster by going to a >".../mailman/roster/" of a list I am a member of but was not >logged in. I got an "authentication failed." error message. Since one >needs to be a member of the list to see the members, that makes sense. Yeah, I always forget about that. I think if you go to a members only page without being logged in, you should get a login page and then be directed back to the original after login. It works that way for private archives (and the admin and admindb interfaces) and the user specific options page, but not for the roster. Gets me every time :( -- Mark Sapiro 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman repetitively trying to drop addresses
Ralph Prichard wrote: > >We imported about 1000 addresses from an old mailing list into a new >Mailman list, and we were hoping Mailman's bounce processing would start >removing any addresses that are clearly no longer valid. This is old >info; if we've got a bad address, we just want it dropped without any >further resuscitation efforts. Here are our bounce processing settings: > >bounce_processing = Yes >bounce_score_threshold = 3.0 >bounce_info_stale_after = 21 >bounce_you_are_disabled_warnings = 0 >bounce_you_are_disabled_warnings_interval = 7 >bounce_unrecognized_goes_to_list_owner = Yes >bounce_notify_owner_on_disable = Yes >bounce_notify_owner_on_removal = Yes > >These settings have been adjusted a few times, but not by any radical >amount. I'm sure I also inadvertantly dropped the >"bounce_score_threshold" from 3.5 to 3.0 while the latest message was >still being distributed. However, the previous message exhibited the >same problematic behavior I'm seeing today, and the values were all left >alone during that period. > > >After messages went out that resulted in bounce scores over the >threshold, there were a couple of issues... > > >1) Mailman tried to send a notification to the bad addresses indicating >that they've been dropped from the mailing list. It does so despite the >fact that "send_goodbye_msg" is set to "no". So my first question is >almost identical to this one: > >http://mail.python.org/pipermail/mailman-users/2006-August/052688.html > >Does anyone know how to get the bounce processing system to respect the >"send_goodbye_msg" value, while still sending the moderators/list owners >notification that an address has been dropped? You can modify the code. In the definition of the sendNextNotification() method, see self.ApprovedDeleteMember( member, 'disabled address', admin_notif=self.bounce_notify_owner_on_removal, userack=1) and change userack=1 to userack=0 if you want no notice or to userack=None (or just remove it) to use the list's send_goodbye_msg setting. However, what's the harm? If the address is truly undeliverable, it's just one more residual bounce. If not, the user may possibly notified of a problem. >2) Mailman tried to drop 2 addresses (out of an apparent list of 55 bad >addresses) over and over again, until after 10 attempts, when the >BounceRunner stopped. (Nothing at all seemed to happen to the other 53 >addresses.) The first notification that the list owners received >regarding the drop attempts referenced the actual message that a list >member sent. But the next 10 notifications referred to the fact that >the "You have been unsubscribed from the 'somelist' mailing list" >messages were _also_ bouncing. (Which is another reason I'd like to >suppress those messages from ever being sent in the first place.) > This is a bug in Mailman 2.1.11 that is fixed in 2.1.12 (it only occurs if bounce_you_are_disabled_warnings is 0). The attached patch.txt file contains a patch to Bouncer.py that will fix it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan === modified file 'Mailman/Bouncer.py' --- Mailman/Bouncer.py 2008-06-20 19:47:28 + +++ Mailman/Bouncer.py 2009-02-16 16:53:20 + @@ -1,4 +1,4 @@ -# Copyright (C) 1998-2008 by the Free Software Foundation, Inc. +# Copyright (C) 1998-2009 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -163,8 +163,10 @@ # We've set/changed bounce info above. We now need to tell the # MemberAdaptor to set/update it. We do it here in case the # MemberAdaptor stores bounce info externally to the list object to -# be sure updated information is stored. -self.setBounceInfo(member, info) +# be sure updated information is stored, but we have to be sure the +# member wasn't removed. +if self.isMember(member): +self.setBounceInfo(member, info) def disableBouncingMember(self, member, info, msg): # Initialize their confirmation cookie. If we do it when we get the === modified file 'NEWS' --- NEWS2009-02-14 22:25:29 + +++ NEWS2009-02-16 16:53:20 + @@ -92,6 +92,9 @@ - Recognize a couple more bounces. +- Fixed a bug introduced in 2.1.11 which would attempt to store bounce info + for a member just deleted if bounce_you_are_disabled_warnings is zero. + i18n - Updated Dutch, Catalan and Polish translations. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/option
Re: [Mailman-Users] How to deal with qfiles/bad/*.psv?
Benjamin Lotto wrote: >I've been using mailman for several years and have recently moved to a >new machine. Something funny happened, and I had a lot of files built >up in the qfiles/* directories. I restarted mailman with > >mailmanctl -s -q start > >and move everything was cleared out. There are six .psv files in >qfiles/bad and I have no idea what to do with them. I've been poking >around the web and various documentation and can't figure it out. >Help, please? > >Using Mailman version: 2.1.12 This is a recent Mailman feature. In older Mailman, when a runner encountered an exception in dequeueing a message, the fact was logged and the message discarded. Now, depending on settings, it may be saved as a .psv file in qfiles/bad/ See the comments in Defaults.py for the settings QRUNNER_SAVE_BAD_MESSAGES, BAD_SHUNT_STALE_AFTER and BAD_SHUNT_ARCHIVE_DIRECTORY. With default settings, assuming you've got a 2.1.12 Mailman crontab, these files are removed after 7 days. You can look at them with bin/dumpdb -p to see what's in them assuming they can be unpickled at all. There are also messages in Mailman's error log saying why they are there. -- Mark Sapiro 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] free Mailman hosting
No you but you can check us out at http://www.emwd.com/mailman.html. Our prices start out at $4 per month per list. Have a great week. :^) Regards, Brian Carpenter EMWD.com http://blog.emwd.com/ Curious comments from a web hosting techie > -Original Message- > From: mailman-users-bounces+brian=emwd@python.org [mailto:mailman- > users-bounces+brian=emwd@python.org] On Behalf Of Antonio Piu > Sent: Friday, June 19, 2009 8:11 PM > To: mailman-users@python.org > Subject: [Mailman-Users] free Mailman hosting > > Hi all! > Does anybody know some free Mailman hosting services? > I could not find anything. > > Thank you for your help. > > Antonio > -- > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman- > users%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman- > users/brian%40emwd.com > > Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Mailman repetitively trying to drop addresses
We imported about 1000 addresses from an old mailing list into a new Mailman list, and we were hoping Mailman's bounce processing would start removing any addresses that are clearly no longer valid. This is old info; if we've got a bad address, we just want it dropped without any further resuscitation efforts. Here are our bounce processing settings: bounce_processing = Yes bounce_score_threshold = 3.0 bounce_info_stale_after = 21 bounce_you_are_disabled_warnings = 0 bounce_you_are_disabled_warnings_interval = 7 bounce_unrecognized_goes_to_list_owner = Yes bounce_notify_owner_on_disable = Yes bounce_notify_owner_on_removal = Yes These settings have been adjusted a few times, but not by any radical amount. I'm sure I also inadvertantly dropped the "bounce_score_threshold" from 3.5 to 3.0 while the latest message was still being distributed. However, the previous message exhibited the same problematic behavior I'm seeing today, and the values were all left alone during that period. After messages went out that resulted in bounce scores over the threshold, there were a couple of issues... 1) Mailman tried to send a notification to the bad addresses indicating that they've been dropped from the mailing list. It does so despite the fact that "send_goodbye_msg" is set to "no". So my first question is almost identical to this one: http://mail.python.org/pipermail/mailman-users/2006-August/052688.html Does anyone know how to get the bounce processing system to respect the "send_goodbye_msg" value, while still sending the moderators/list owners notification that an address has been dropped? 2) Mailman tried to drop 2 addresses (out of an apparent list of 55 bad addresses) over and over again, until after 10 attempts, when the BounceRunner stopped. (Nothing at all seemed to happen to the other 53 addresses.) The first notification that the list owners received regarding the drop attempts referenced the actual message that a list member sent. But the next 10 notifications referred to the fact that the "You have been unsubscribed from the 'somelist' mailing list" messages were _also_ bouncing. (Which is another reason I'd like to suppress those messages from ever being sent in the first place.) But back to the failure to drop the address... There are the 11 restarts shown in the qrunner log file: Excerpt from /var/log/mailman/qrunner: == Jun 22 14:58:16 2009 (2047) Master qrunner detected subprocess exit (pid: 2073, sig: None, sts: 1, class: BounceRunner, slice: 1/1) [restarting] Jun 22 14:58:16 2009 (4880) BounceRunner qrunner started. Jun 22 15:13:16 2009 (2047) Master qrunner detected subprocess exit (pid: 4880, sig: None, sts: 1, class: BounceRunner, slice: 1/1) [restarting] Jun 22 15:13:16 2009 (5102) BounceRunner qrunner started. ...7 more occurrences removed (each BounceRunner startup has a different PID, if that's what the number in the bracket represents)... Jun 22 17:13:18 2009 (2047) Master qrunner detected subprocess exit (pid: 5522, sig: None, sts: 1, class: BounceRunner, slice: 1/1) [restarting] Jun 22 17:13:18 2009 (5574) BounceRunner qrunner started. Jun 22 17:28:18 2009 (2047) Master qrunner detected subprocess exit (pid: 5574, sig: None, sts: 1, class: BounceRunner, slice: 1/1) [restarting] Jun 22 17:28:18 2009 (2047) Qrunner BounceRunner reached maximum restart limit of 10, not restarting. There appears to be more interesting information in other files in /var/log/mailman. I'll include one excerpt from the "errors" file below. If anyone thinks the other information would be handy, please let me know and I'll try to trim it down a bit before sending a copy along. Excerpt from /var/log/mailman/error: Jun 22 17:28:18 2009 qrunner(5574): Traceback (most recent call last): Jun 22 17:28:18 2009 qrunner(5574): File "/var/lib/mailman/bin/qrunner", line 278, in Jun 22 17:28:18 2009 qrunner(5574): main() Jun 22 17:28:18 2009 qrunner(5574): File "/var/lib/mailman/bin/qrunner", line 238, in main Jun 22 17:28:18 2009 qrunner(5574): qrunner.run() Jun 22 17:28:18 2009 qrunner(5574): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 88, in run Jun 22 17:28:18 2009 qrunner(5574): self._cleanup() Jun 22 17:28:18 2009 qrunner(5574): File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 263, in _cleanup Jun 22 17:28:18 2009 qrunner(5574): BounceMixin._cleanup(self) Jun 22 17:28:18 2009 qrunner(5574): File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 137, in _cleanup Jun 22 17:28:18 2009 qrunner(5574): self._register_bounces() Jun 22 17:28:18 2009 qrunner(5574): File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 125, in _register_bounces Jun 22 17:28:18 2009 qrunner(5574): mlist.registerBounce(addr, msg, day=day) Jun 22 17:28:18 2009 qrunner(5574): File "/usr/lib/mailman/Mailman/Bouncer.py", line 167, in registerBounce Jun 22 17:28:18 2009 qrun
[Mailman-Users] How to deal with qfiles/bad/*.psv?
I've been using mailman for several years and have recently moved to a new machine. Something funny happened, and I had a lot of files built up in the qfiles/* directories. I restarted mailman with mailmanctl -s -q start and move everything was cleared out. There are six .psv files in qfiles/bad and I have no idea what to do with them. I've been poking around the web and various documentation and can't figure it out. Help, please? Using Mailman version: 2.1.12 Many thanks, -Ben -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] footers and members of the list
> Hal Huntley wrote: > > >We have a request from a list administrator asking if he can have the all > >the members of the list listed in the footer of the message. This list is > >under Mailman 2.1.9. > > > >This isn't a "personalization" listing with just the name of the member > >subscribing. He wants all the messages going out to have all the list > >members in the footer. > > > >Is there a variable that can handle that? Or must the list maintainer just > >add the names by hand? He may be content with just names or email > >addresses. > > > No, there is no variable that can handle that, but one could easily put > a link to the list's roster page in the footer which I think would be > much better than putting everyone's address in which raises serious > privacy concerns should such a message be forwarded off list. > > -- > Mark Sapiro 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://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/hal%40sofdev.sri.com > > Security Policy: http://wiki.list.org/x/QIA9 > === Mark, Thank you for that information. I gave that URL idea a try and if I happened to be logged in as a list administrator for a list, I got a list of members. I also tried getting a roster by going to a ".../mailman/roster/" of a list I am a member of but was not logged in. I got an "authentication failed." error message. Since one needs to be a member of the list to see the members, that makes sense. One could set the URL to point to the ".../listinfo/" page where the person could enter their email address and password to get the list members, but I think the list admininstrator wants something a bit easier to get the names. I will share your thoughts with the list administrator about not wanting to do that anyway due to privacy concerns. Excellent point. Hal -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Internal 500 Error (Ubuntu jaunty / Mailman 2.1.12 / Python 2.6.2)
Hi, I've tried to look this up on the lists, forums, etc. but have failed to find anything that resolves this issue, so forgive me if I have missed a solution mentioned elsewhere. I have recently upgraded my Ubuntu distribution to Jaunty. This upgrade included an upgrade on Mailman, Python and Apache2. I'm currently running the following versions: ii apache2 2.2.11-2ubuntu2.1 Apache HTTP Server metapackage ii apache2-mpm-prefork 2.2.11-2ubuntu2.1 Apache HTTP Server - traditional non-threade ii python2.6 2.6.2-0ubuntu1 An interactive high-level object-oriented la ii listadmin 2.40-2.2 command line mailman moderator queue manipul ii mailman 1:2.1.12-1 Powerful, web-based mailing list manager I have looked through the logs, but nothing seems to indicate anything special, aside from the expressive line: Premature end of script headers: admin In my Apache2 error log file (turned logging to 'debug' level). Running the 'admin' or 'listinfo' scripts from the shell gives me this: # ./listinfo Content-type: text/html Bug in Mailman version 2.1.12 Bug in Mailman version 2.1.12 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. - I ran 'check_perms' and while there were errors it found, they were all fixed. This had no effect on the problem. Mailman appears to be operational otherwise. Emails are sent and received without issues. I can admin the site using the 'listadmin' tools. However, the web interface is completely broken. What am I missing? Thanks! Derek Morrison -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] free Mailman hosting
Hi all! Does anybody know some free Mailman hosting services? I could not find anything. Thank you for your help. Antonio -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Approve all held?
Mark Sapiro wrote: Alexei Altuhov wrote: Unfortunately I don't have access to the web interface, because of the Group mismatch error. We can help you fix that. How did you install Mailman? From our source or from a vendors package? Give us the details, and we'll try to help. Mailman has been installed by one of our admins from the repository, as usual. The thing is, that he has installed Asterix afterwards and as I understood from now on all cgi scripts are run from the asterix group rather than the mailman one. Is it possible to change that or divide, which cgi scripts will be executed from the mailman group and which ones from the mailman - I couldn't figure out by myself and that left me with the command line administration. So, if you need more details in order to resolve this, I'd be happy to provide it! Thanks for trying to help, Alexei. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] footers and members of the list
Hal Huntley wrote: >We have a request from a list administrator asking if he can have the all >the members of the list listed in the footer of the message. This list is >under Mailman 2.1.9. > >This isn't a "personalization" listing with just the name of the member >subscribing. He wants all the messages going out to have all the list >members in the footer. > >Is there a variable that can handle that? Or must the list maintainer just >add the names by hand? He may be content with just names or email >addresses. No, there is no variable that can handle that, but one could easily put a link to the list's roster page in the footer which I think would be much better than putting everyone's address in which raises serious privacy concerns should such a message be forwarded off list. -- Mark Sapiro 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] footers and members of the list
We have a request from a list administrator asking if he can have the all the members of the list listed in the footer of the message. This list is under Mailman 2.1.9. This isn't a "personalization" listing with just the name of the member subscribing. He wants all the messages going out to have all the list members in the footer. Is there a variable that can handle that? Or must the list maintainer just add the names by hand? He may be content with just names or email addresses. Regards, Hal Huntley SRI International -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Approve all held?
Алексей Алтухов wrote: > Mark Sapiro wrote: >> Alexei Altuhov wrote: >> >>> Unfortunately I don't have access to the web interface, because of the >>> Group mismatch error. >>> >> >> >> We can help you fix that. How did you install Mailman? From our source >> or from a vendors package? >> >> Give us the details, and we'll try to help. >> >> > Mailman has been installed by one of our admins from the repository, as > usual. This seems to say you installed someone's package from a package repository as opposed to installing from our source. > The thing is, that he has installed Asterix afterwards and as I > understood from now on all cgi scripts are run from the asterix group > rather than the mailman one. > > Is it possible to change that or divide, which cgi scripts will be > executed from the mailman group and which ones from the mailman - I > couldn't figure out by myself and that left me with the command line > administration. If you installed from source, the way to fix this is to re-run configure with the addition of the option "--with-cgi-gid=asterix" and then run "make install". The alternative is to configure the web server (is this Asterix?) to run the Mailman CGI wrappers as the group they expect, but I gather this is not possible in your case. Most packaged versions of Mailman have a way to tell the CGI wrappers what group to expect, but how you do that is specific to the package. You need to ask the packager. I.e., if this is a RedHat or CentOS rpm, ask on a RedHat list or see other RedHat support resources; if Debian or Ubuntu, check those support resources, etc. -- Mark Sapiro 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
