Mailman 3 November 2002 - Mailman-Users

HELP! Getting different Import Error: python2.2/lib-dynload/_socket.so: bad ELF flags value: 256
by Steve Rifkin 29 Nov '02

29 Nov '02

Anyone familiar with the error (we're running python 2.2.2 and mailman 2.08): admin(7162): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 more details below. Thanks! Steve admin(7153): DOCUMENT_ROOT: /users/httpd/htdocs Nov 26 11:19:04 2002 admin(7162): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(7162): [----- Mailman Version: 2.0.8 -----] admin(7162): [----- Traceback ------] admin(7162): Traceback (most recent call last): admin(7162): File "/home/mailman/scripts/driver", line 80, in run_main admin(7162): import Mailman.pythonlib.cgi admin(7162): File "../Mailman/pythonlib/cgi.py", line 31, in ? admin(7162): import urllib admin(7162): File "/usr/local/lib/python2.2/urllib.py", line 26, in ? admin(7162): import socket admin(7162): File "/usr/local/lib/python2.2/socket.py", line 41, in ? admin(7162): from _socket import * admin(7162): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 admin(7162): [----- Python Information -----] admin(7162): sys.version = 2.2.2 (#1, Nov 25 2002, 15:28:57) [GCC 2.95.2 19991024 (release)] admin(7162): sys.executable = /usr/local/bin/python admin(7162): sys.prefix = /usr/local admin(7162): sys.exec_prefix= /usr/local admin(7162): sys.path = /usr/local admin(7162): sys.platform = sunos5 admin(7162): [----- Environment Variables -----] admin(7162): HTTP_PRAGMA: no-cache admin(7162): PYTHONPATH: /home/mailman admin(7162): SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(7162): SCRIPT_FILENAME: /home/mailman/cgi-bin/admin admin(7162): SERVER_ADMIN: webmaster(a)cs.jhu.edu admin(7162): SCRIPT_NAME: /mailman/admin admin(7162): SCRIPT_URI: http://www.cs.jhu.edu/mailman/admin admin(7162): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.27 Server at www.cs.jhu.edu Port 80</ADDRESS> admin(7162): REQUEST_METHOD: GET admin(7162): HTTP_HOST: www.cs.jhu.edu admin(7162): SCRIPT_URL: /mailman/admin admin(7162): SERVER_PROTOCOL: HTTP/1.0 admin(7162): QUERY_STRING: admin(7162): HTTP_CONNECTION: Keep-Alive admin(7162): REQUEST_URI: /mailman/admin admin(7162): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* admin(7162): HTTP_ACCEPT_CHARSET: iso-8859-1,*,utf-8 admin(7162): HTTP_USER_AGENT: Mozilla/4.7 [en] (X11; U; SunOS 5.6 sun4u) admin(7162): TZ: US/Eastern admin(7162): SERVER_NAME: www.cs.jhu.edu admin(7162): REMOTE_ADDR: 128.220.13.39 admin(7162): REMOTE_PORT: 35634 admin(7162): HTTP_ACCEPT_LANGUAGE: en admin(7162): SERVER_PORT: 80 admin(7162): GATEWAY_INTERFACE: CGI/1.1 admin(7162): HTTP_ACCEPT_ENCODING: gzip admin(7162): SERVER_ADDR: 128.220.13.101 admin(7162): DOCUMENT_ROOT: /users/httpd/htdocs

2 1

Announce-only lists?
by Chris 29 Nov '02

29 Nov '02

How does one set up an announce-only list? I didn't see that option listed, but I could have missed it. I was actually hoping that I could set up a list with about 200 people subscribed, but only about 5 of them have posting capabilities. Chris

7 7

Is this real? (Missing Password Message)
by Tim 29 Nov '02

29 Nov '02

One of my list managers forwarded the below to me and I've never seen anything like it before. My question is: Is this a legitimate Mailman v2.0.8 message or is it a worm generated message (notice the "To: undisclosed-recipients: ;")? Note I've replaced the valid user address with x's -------- Original Message -------- Date: Sat, 23 Nov 2002 19:57:41 -0500 (EST) From: elecraft-admin(a)mailman.qth.net To: undisclosed-recipients: ; Mailman noticed in .MailUserPassword() that: Subject: Elecraft(a)mailman.qth.net user xxxxxx(a)xxx.xxx missing password! From: elecraft-request(a)mailman.qth.net To: elecraft-admin(a)mailman.qth.net X-No-Archive: yes X-Ack: no Sender: elecraft-admin(a)mailman.qth.net Errors-To: elecraft-admin(a)mailman.qth.net X-BeenThere: elecraft(a)mailman.qth.net X-Mailman-Version: 2.0.8 Precedence: bulk User: 'xxxxxx(a)xxx.xxx' List: elecraft lacks a password. Please notify the Mailman system manager at this site!

2 1

Lists not advertised when they should...
by Gualter Barbas Baptista 29 Nov '02

29 Nov '02

Hi, I've upgraded from Mailman 2.0 to 2.1b5. Now, the lists that I already had from 2.0 are publicly advertised on the listinfo page. However, the new ones aren't. Both of them have the advertised option set to yes. Is this some kind of known bug or is it some problem of my configuration? Thanks, -- Gualter Barbas Baptista gualter(a)gaia.org.pt ICQ# 8106393 jabber.org: gandhiano GAIA - Grupo de Acção e Intervenção Ambiental http://gaia.org.pt gaia(a)gaia.org.pt Portugal Membro do Fórum Social Português

1 0

qrunner problems
by fish 29 Nov '02

29 Nov '02

I am still have the authentication problems with qrunner and, since nobody seems to know what the problem is or how to fix it, thought that I would ask what exactly does qrunner do? I can tell that the cron.d/mailman script is calling /usr/lib/mailman/cron/qrunner, but what does this script do? Since I only have a rudimentary programming knowledge, I would greatly appreciate your help on this. Robert Lydiate icon(a)accesscomm.ca

2 6

the public name of this list
by David Gordon 29 Nov '02

29 Nov '02

In the web admin page, "The public name of this list" is not "list" but my email address. Which is strange. Going to "Details", however, shows the correct title "list". Some thing wrong somewhere. My Mac OS X browser? [Chimera], my server or Mailman? -- DG

2 1

more permission problems
by David Gordon 28 Nov '02

28 Nov '02

[Sometimes I don't get a copy of my mail to this list so sorry if I appear to be repeating...] I've reinstalled Mailman 2.0.13 because I couldn't get it going yesterday. I beleive I'm installing it on a machine with "Apache/1.3.23 (Unix) (Red-Hat/Linux) mod_ssl/2.8.7 OpenSSL/0.9.6 PHP/4.1.2 FrontPage/ 4.0.4.3 configured". I have done the check_perms business. Mail doesn't get sent. One message got through. I then auto subscribed some members. Then it all went wrong. This is _exactly_ what happenned yesterday. Further point of information, since doing the check_perms I can't get to the web pages. Here's what I know, but don't understand >Traceback (innermost last): > File "/home/mailman/cron/gate_news", line 222, in ? > main() > File "/home/mailman/cron/gate_news", line 198, in main > lock.lock(timeout=0.5) > File "/home/mailman/Mailman/LockFile.py", line 219, in lock > self.__write() > File "/home/mailman/Mailman/LockFile.py", line 350, in __write > fp = open(self.__tmpfname, 'w') >IOError: [Errno 13] Permission denied: '/home/mailman/locks/ >gate_news.lock.epuk.thenexus.co.uk.18703' I have done the check_perms business ;-) I did have to manually chmod the $prefix/cgi-bin to get my web pages for this list working. (Stopped working since check_perms) I have sucessfully set up another list without problems, what's my problem really. This is the same/similar as I was having yesterday. I have reinstalled. Have I got a duff copy of Mailman. Should I download another copy from another location and have another attempt? -- DG

1 0

Subscribe, reply, nothing more
by Denny Schierz 28 Nov '02

28 Nov '02

hi, i installed the lastest Mailman on Gentoo Linux without problems. But i can subscribe on the webpage, then i reply the mail from mailman and that was it.: We have received a request from 192.168.100.150 for subscription of your email address, <cuall(a)gmx.de>, to the labe(a)cst-it.local mailing list. To confirm the request, please send a message to labe-request(a)cst-it.local, and either: ... I found no errors, in syslog, mailman logs & Co. . I have Postfix-Cyrus-Mysql System running. My other Mailman installations on Debian Potato/Woody are working without any problems. How can i find, what the problem is?. My perms are ok, for Mailman. cu denny

1 1

Premature end of script headers
by David Gordon 28 Nov '02

28 Nov '02

I've reinstalled Mailman 2.0.13 because I couldn't get it going yesterday. I beleive I'm installing it on a machine with "Apache/1.3.23 (Unix) (Red-Hat/Linux) mod_ssl/2.8.7 OpenSSL/0.9.6 PHP/4.1.2 FrontPage/ 4.0.4.3 configured". Followed all instructions, created new list, got initial message, went to configure list on web page but received an internal error message. The httpd error file says... [Thu Nov 28 15:37:24 2002] [error] [client 80.2.78.6] Premature end of script headers: /home/mailman/cgi-bin/admin ... do I start all over again? I don't know what's up here. I know I can do this, I've got a list running fime on another server. Thanks -- DG

1 0

Re: ImportError: No module named Charset
by Daniel Figucio 28 Nov '02

28 Nov '02

> * From: Carlos Barcenilla > * Subject: [Mailman-Users] ImportError: No module named Charset > * Date: Mon, 11 Nov 2002 04:37:26 -0800 > > Hi! > > When I call checkdbs (either manually or from cron) i get the > following error: > > [root@cox cron]# ./checkdbs > Traceback (most recent call last): > File "./checkdbs", line 26, in ? > from email.Charset import Charset > ImportError: No module named Charset > I solved this way, but I think it's a bug. > > [root@cox cron]# export PYTHONPATH=/usr/local/mailman/pythonlib > [root@cox cron]# ./checkdbs > Versions: > -OS: Red Hat 8.0 > -Python: 2.2.1 > -mailman: 2.1b4 > > Regards. > Carlos This is fixed in 2.1b5. If you don't want to download 2.1b5, open bin/checkdbs, and move the line: from email.Charset import Charset to just after the line: import paths This ensures that we are using the mailman email package... Sorry if this has been answered before, its just that I didn't find this solution in the archives, but it was in the archives for mailman developer. I checked the 2.1b5 version of checkdbs and it had been fixed there, too... daniel. -- Daniel Figucio Computer Graphics and Internet Specialist CRC for Catchment Hydrology GPO Box 1666 CANBERRA CITY ACT 2601 t: +61 2 6246 5822 f: + 61 2 6246 5845 http://www.catchment.crc.org.au http://www.clw.csiro.au/research/catchment/modelling/ AWAY NEXT: December 21 2002 - January 19 2003 (All Dates Inclusive)

1 0