Mailman 3 May 2000 - Mailman-Developers

.nfs* lock files
by Melissa G. Ng 17 May '00

17 May '00

I have innumerable files in the "locks" directory with the prefix ".nfs". There are several of these every minute of every day. I think it may be related to a problem I have regarding the cgi script "listinfo". When I try to invoke "<mailman-server>/mailman/listinfo" I get ----------------------------------------------begin here------------------------------------------------------------------- Bug in Mailman version 1.1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/user/mailman/scripts/driver", line 112, in run_main main() File "../Mailman/Cgi/listinfo.py", line 40, in main FormatListinfoOverview() File "../Mailman/Cgi/listinfo.py", line 88, in FormatListinfoOverview l = MailList.MailList(n, lock = 0) File "/user/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/user/mailman/Mailman/MailList.py", line 812, in Load dict = marshal.load(file) MemoryError: Environment variables: Variable Value DOCUMENT_ROOT /usr/apache/htdocs SERVER_ADDR 163.181.40.6 HTTP_ACCEPT_ENCODING gzip SERVER_PORT 80 REMOTE_ADDR 163.181.232.166 SERVER_SOFTWARE Apache/1.3.12 (Unix) GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_LANGUAGE en REMOTE_PORT 50107 SERVER_NAME super TZ US/Central HTTP_USER_AGENT Mozilla/4.7 [en] (X11; I; SunOS 5.7 sun4u) HTTP_ACCEPT_CHARSET iso-8859-1,*,utf-8 HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* REQUEST_URI /mailman/listinfo PATH /usr/bin:/usr/ucb:/bin:/etc:/usr/dt/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/etc:/usr/bin/X11://bin:.:/usr/openwin/bin:/apps/lsf/SOLARIS/bin QUERY_STRING SERVER_PROTOCOL HTTP/1.0 HTTP_HOST super REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.12 Server at super Port 80 SCRIPT_NAME /mailman/listinfo SERVER_ADMIN thanhn.tran(a)amd.com SCRIPT_FILENAME /user/mailman/cgi-bin/listinfo PYTHONPATH /user/mailman HTTP_CONNECTION Keep-Alive ----------------------------------------------end here------------------------------------------------------------------- But when I invoke the individual lists's "listinfo" page, it comes back fine. Could someone please help me out with this problem? -- Melissa G. Ng Systems Engineer 512.602.4111

2 1

Features Mailman
by Mr.Yotsak Kongwithayanont 16 May '00

16 May '00

Dear Sir Please help me too . I would like to know . What are all features of Mailman ? Regards; Yotsak

2 1

Problem accessing <server>/mailman/listinfo and <server>/mailman/admin
by Melissa G. Ng 15 May '00

15 May '00

Hello: When I try to access <server>/mailman/listinfo and <server>/mailman/admin. I get the following message on the web server: --------------------------------------------- --------------------------------------------- ---------------------------------- Bug in Mailman version 1.1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/user/mailman/scripts/driver", line 112, in run_main main() File "../Mailman/Cgi/listinfo.py", line 40, in main FormatListinfoOverview() File "../Mailman/Cgi/listinfo.py", line 88, in FormatListinfoOverview l = MailList.MailList(n, lock = 0) File "/user/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/user/mailman/Mailman/MailList.py", line 812, in Load dict = marshal.load(file) MemoryError: Environment variables: Variable Value DOCUMENT_ROOT /usr/apache/htdocs SERVER_ADDR 163.181.40.6 HTTP_ACCEPT_ENCODING gzip SERVER_PORT 80 REMOTE_ADDR 163.181.232.166 SERVER_SOFTWARE Apache/1.3.12 (Unix) GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_LANGUAGE en REMOTE_PORT 44489 SERVER_NAME super TZ US/Central HTTP_USER_AGENT Mozilla/4.7 [en] (X11; I; SunOS 5.7 sun4u) HTTP_ACCEPT_CHARSET iso-8859-1,*,utf-8 HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* REQUEST_URI /mailman/listinfo PATH /usr/bin:/usr/ucb:/bin:/etc:/usr/dt/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/etc:/usr/bin/X11://bin:.:/usr/openwin/bin:/apps/lsf/SOLARIS/bin QUERY_STRING SERVER_PROTOCOL HTTP/1.0 HTTP_HOST super REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.12 Server at super Port 80 SCRIPT_NAME /mailman/listinfo SERVER_ADMIN thanhn.tran(a)amd.com SCRIPT_FILENAME /user/mailman/cgi-bin/listinfo PYTHONPATH /user/mailman HTTP_CONNECTION Keep-Alive --------------------------------------------- --------------------------------------------- ---------------------------------- The message is similar for the <server>/mailman/admin output. -- Melissa G. Ng Systems Engineer 512.602.4111

1 0

Don't send your mail again thanks!
by 刘红铄 12 May '00

12 May '00

1 0

Please dont send your mail again,thanks!
by 刘红铄 12 May '00

12 May '00

1 0

Please don't send your mail again,thanks!
by 刘红铄 12 May '00

12 May '00

1 0

Re: [Mailman-Developers] cookies
by Harald Meland 12 May '00

12 May '00

[Ricardo Kustner] > you used 2 test cookies in your example, but i'm not sure if that's > necessary... It is once others beside me get a user database :), because then they will have cross-list authentication using a single cookie. In that scenario it would be a shame if the test cookie overwrote a valid authentication cookie for some other list. > also, AFIAK, deleting a cookie can be done by re-setting it with an > empty value (though i believe there are some old versions of either > IE or Netscape which have a bug with this feature) I'd prefer to go with the method described in RFC 2109: 4.2.2 Set-Cookie Syntax [...] Max-Age=delta-seconds Optional. The Max-Age attribute defines the lifetime of the cookie, in seconds. The delta-seconds value is a decimal non- negative integer. After delta-seconds seconds elapse, the client should discard the cookie. A value of zero means the cookie should be discarded immediately. > > Of course, if there are any (major) browsers in use out there that > > doesn't understand Max-Age, it would be a bad idea to change Mailman. > this is the first time I've heard about Max-Age RFC 2109 is dated February 1997, and one of it's authors was a Netscape employee. I'll try issuing Cookies with Max-Age instead of Expires for our own users, and let you know how it goes >-) -- Harald

1 0

Current round of checkins are finished
by bwarsaw＠python.org 10 May '00

10 May '00

I've checked in all my current modifications to make losing messages much less likely. I'm sure there are bugs lurking about, so be careful if you're running the CVS snapshot. I'm going to spend a few hours over the next couple of days testing things so watch for more patches. If you do play with the snapshot and find problems, please let me know. Figure if I get some time, there will be a beta this weekend. -Barry

2 1

Re: Extraordinary locking mechanisms...
by Jeremy Hylton 10 May '00

10 May '00

[Dan A. Dickey wrote:] >Well, I figure its finally time for me to aska stupid question. > >Why do people use filesystems for locking? >Why not use IPC semaphores instead? > >It seems that people are going through extraordinary >trouble and grief to get the filesystem locking correct. >Like I said - it may be a stupid question, and I'm >just not getting something. What is that something? Chris pointed at that mailman runs as a distributed system, so IPC won't work. The idea, though, of using something other than the filesystem for locking makes good sense. The locking could be based on a server that communication with other mailman components over a socket. It would look basically like the Javaspaces leasing service. (Leases are basically locks that timeout.) The only worry I would have is about crashes of the lease service. For a single machine, it could run under init; for multiple machines, a leader election protocol would be necessary to guard against machine crashes. Jeremy

2 1

Re: [Mailman-Developers] cookies
by Harald Meland 10 May '00

10 May '00

[Ricardo Kustner] > Hi, > > this was just suggested to me by somebody from mailman-users: > > > Please write a patch which puts the string "Cookie could not be set" on the > > web page so that I can see that pressing submit will not work :-) > > i think thats a good point... it would safe some user questions if > MM tells exactly why the authorisation failed. While I agree that such a warning would be nice, I don't think it's possible to do such things with cookies. > I'm not sure if this subject has been touched already, but what > allowing admins to choose between cookies and > Basic-Authorization... it should be possible to use Basic-auth, > right? What is Basic-Authorization? If it doesn't involve a HTTP POST of the admin login page, I believe it will not work (out of the box, anyway). -- Harald

4 5