Re: [Mailman-Users] How can our MM site admin see unadvertised lists via web interface?
As site admin, you should have command-line access to the server, or at least be able to remember what private lists you've created. Remember, it's not me being a list admin, but rather a site admin that's the issue. As a site admin, I wouldn't necessarily know all the many lists that our list admins would decide to make private. Actually, as a site-admin, I wouldn't necessarily know all the public lists too. I'd have to have a list available to me (we could potentially have dozens of lists made where the list admins would choose whether to advertise the list or not), and I was hoping I'd have that list available through a password-protected webpage, especially since there are other pages that require the site admin to log in within Mailman (specific list maintenance, etc.) But, yes, having a command-line-access to the server would be the only way for the site admin to have a complete set of lists (advertised and non-advertised.) But you are right that this would be a nice feature. Please feel free to go to the SourceForge Mailman Request for Enhancement page at http://sourceforge.net/tracker/?group_id=103atid=350103 and file an RFE. Brad, thanks for all the info. I appreciate it. Steve -- 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] How can our MM site admin see unadvertised lists via web interface?
Cool. Thanks Matt, I'll have to try that out.
Steve
Matt wrote:
I wrote a nasty script to generate an HTML file that lists all the
lists.
I run it daily from cron because I didn't want to monkey around with a
setuid mailman CGI program.
Use your web server to restrict access to the generated HTML file as
appropriate.
Here's an example. Customize as required. Works for me; it might
work for you.
#!/usr/bin/perl
# Create a web page from the output of the Mailman list_lists command.
$cmd=/usr/share/mailman/bin/list_lists;
open LISTINFO, $cmd | or die cannot run $cmd: $!\n;
print '
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN
http://www.w3.org/TR/html4/strict.dtd;
html
head
titleMailing lists/title
style type=text/css
.shaded {background: #EE;}
/style
/head
body
h1Mailing lists/h1
table
';
$rownumber = 0;
$headerline = LISTINFO;
while (LISTINFO) {
chop;
($listname, $description) = split / - /;
$listname =~ s/^\s+//;
if ($rownumber % 2) {
$class = ;
} else {
$class = 'class=shaded';
}
$rownumber++;
$lc_listname = lc $listname;
print tr $class\n;
print tda href=\/mailman/listinfo/$lc_listname\$listname/a\n;
print td$description\n;
print tda href=\mailto:[EMAIL PROTECTED]
mail list owner/a\n;
print /tr\n;
}
print /table;
# page footer
print '
/body
/html
';
--
Matt Emerson
[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
[Mailman-Users] How can our MM site admin see unadvertised lists via web interface?
If I am the site Mailman admin for my Mailman site, using the web interface, how can I see the lists of all my site's lists, including the unadvertised lists? I find that if I go to the MM admin page for my site, it says, There currently are no publicly-advertised Mailman mailing lists on mysite.jhu.edu. To visit the administrators configuration page for an unadvertised list, open a URL similar to this one, but with a '/' and the list name appended. However, there is at least one list on the site, but it is set not to 'advertise'. As the site admin, I can log into this specific unadvertised list from the web and make changes. But, I have to know ahead of time that this list is actually on our MM server. So, as site admin, how can I use the web interface to see the entire set of lists, advertised and unadvertised, on my MM server via the web, so that I know what lists I have to choose from? I thought I used to be able to do this on an old install of Mailman we used to have, but I can't seem to find any docs or FAQ entries that describe how to do it. (I know I can get the list of all MM mail lists at the command line, but if I'm working remotely via the web, I'd like not to have to log into the MM server machine at a command prompt and have to run the MM commands just to see all the lists on our server.) Thank in advance! Steve -- 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] How can our MM site admin see unadvertised lists via web interface?
Even to the site admins? Was it always like that? I was chatting with another admin here today, and for some reason, we seem to remember the site admin being able to see all lists via the web interface... mind you, that's when we were running MM about 2-3 years ago, and we just might be remembering something else. (We haven't run MM for a while now but are restarting the service and are trying to catch up.) Is there a reason why the design of Mailman doesn't allow for the web interface to display _all_ lists for a Mailman site admin only? I would think that would be a good feature to have, in that, if I wanted to configure lists remotely as the site admin (as opposed to a list admin), I'd want to see the names of all the lists, advertised or not. Thanks for your reply. Steve Brad Knowles wrote: Via the web interface? You don't. The web interface only shows the public lists. -- 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] Passwords of members UPDATE
But, the python commands you want me to try DO work (and mailman still yields the same errors from my previous e-mail): # python -V Python 2.2.2 # python Python 2.2.2 (#1, Jan 9 2003, 16:24:27) [GCC 2.95.2 19991024 (release)] on sunos5 Type help, copyright, credits or license for more information. import time time.__file__ '/usr/local/lib/python2.2/lib-dynload/time.so' So, what should I try next? (BTW, thanks for your help! :) Steve Rifkin [EMAIL PROTECTED] The second issue you had (no module name time) looks like your Python installation is broken. You should be able to do something like the following at the command line: % python Python 2.2.2 (#1, Oct 14 2002, 19:51:36) [GCC 2.96 2731 (Red Hat Linux 7.3 2.96-112)] on linux2 Type help, copyright, credits or license for more information. import time time.__file__ '/usr/local/lib/python2.2/lib-dynload/time.so' -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problems running mailctl and sending to lists...
I recently installed mailman 2.1 (upgrading over our mailman 2.13) to correct a
problem with list admin passwords.
At the time of the upgrade, I was running python 2.1
Today I finally ran genaliases to modify the old mm list aliases for the new
mailman.
With the aliases in place, I sent e-mail to one of my lists... newlist.
Instead of the message going through, I get back the following from the
mailer-daemon:
- The following addresses had permanent fatal errors -
|/users/rtfm/mailman/mail/mailman post newtest
(reason: 1)
(expanded from: newtest@cs)
- Transcript of session follows -
Traceback (most recent call last):
File /users/rtfm/mailman/scripts/post, line 69, in ?
main()
File /users/rtfm/mailman/scripts/post, line 64, in main
tolist=1, _plaintext=1)
File /users/rtfm/mailman/Mailman/Queue/Switchboard.py, line 119, in enqueue
msgfp = open(msgfile, 'w')
IOError: [Errno 13] Permission denied:
'/users/rtfm/mailman/qfiles/in/1042138477.3629709+2b891898799d3290ae81d057bdd6e8
2a56ffe112.msg'
554 5.3.0 unknown mailer error 1
=
What is causing the above?
OK, so I figure, since I was running python 2.1, maybe mailman 2.1 would rather
me run python 2.2.2.
I then installed python 2.2.2. Directly afterwards, I rebuilt (make clean,
configure, make, make install) mailman 2.1 again, and then, ran check_perms (and
corrected anything that needed correcting so that check_perms now comes back
clean.
Now, when I start to run the scripts/mailman script to startup mailmanctl, I
immediately get lots of messages that look like this:
# ./mailman start
cs:/users/rtfm/mailman/scripts:{153} Traceback (most recent call last):
File /users/rtfm/mailman/bin/qrunner, line 77, in ?
from Mailman.i18n import _
File /users/rtfm/mailman/Mailman/i18n.py, line 18, in ?
import time
ImportError: No module named time
Traceback (most recent call last):
File /users/rtfm/mailman/bin/qrunner, line 77, in ?
from Mailman.i18n import _
File /users/rtfm/mailman/Mailman/i18n.py, line 18, in ?
import time
ImportError: No module named time
Traceback (most recent call last):
I get the above messages continuously. What's happening here?
Mind you, when I had python 2.1 installed, I had no problem running mailmanctl
(except that mail sent to lists would yield the message near the top of this
e-mail. With python2.2.2 installed, I can't even get mailmanctl to run
properly... or rather, whatever it's running is giving me the errors directly
above.
And remember, *after* I installed python 2.2.2, I *rebuilt* mailman.
So, what should I do here?
If python's an issue, I'll go back to python 2.1 and hope someone here can help
me fix the problem with the mailer-daemon message. At least python 2.1, I could
run the mailman startup script.
(Note, the machine mailman is built on is Solaris 2.8.
Thanks in advance!
Steve Rifkin
[EMAIL PROTECTED]
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
Re: [Mailman-Users] Passwords of members UPDATE
I recently installed mailman 2.1 (upgrading over our mailman 2.13) to correct a
problem with list admin passwords.
At the time of the upgrade, I was running python 2.1
Today I finally ran genaliases to modify the old mm list aliases for the new
mailman.
With the aliases in place, I sent e-mail to one of my lists... newlist.
Instead of the message going through, I get back the following from the
mailer-daemon:
- The following addresses had permanent fatal errors -
|/users/rtfm/mailman/mail/mailman post newtest
(reason: 1)
(expanded from: newtest@cs)
- Transcript of session follows -
Traceback (most recent call last):
File /users/rtfm/mailman/scripts/post, line 69, in ?
main()
File /users/rtfm/mailman/scripts/post, line 64, in main
tolist=1, _plaintext=1)
File /users/rtfm/mailman/Mailman/Queue/Switchboard.py, line 119, in enqueue
msgfp = open(msgfile, 'w')
IOError: [Errno 13] Permission denied:
'/users/rtfm/mailman/qfiles/in/1042138477.3629709+2b891898799d3290ae81d057bdd6e8
2a56ffe112.msg'
554 5.3.0 unknown mailer error 1
=
What is causing the above?
OK, so I figure, since I was running python 2.1, maybe mailman 2.1 would rather
me run python 2.2.2.
I then installed python 2.2.2. Directly afterwards, I rebuilt (make clean,
configure, make, make install) mailman 2.1 again, and then, ran check_perms (and
corrected anything that needed correcting so that check_perms now comes back
clean.
Now, when I start to run the scripts/mailman script to startup mailmanctl, I
immediately get lots of messages that look like this:
# ./mailman start
cs:/users/rtfm/mailman/scripts:{153} Traceback (most recent call last):
File /users/rtfm/mailman/bin/qrunner, line 77, in ?
from Mailman.i18n import _
File /users/rtfm/mailman/Mailman/i18n.py, line 18, in ?
import time
ImportError: No module named time
Traceback (most recent call last):
File /users/rtfm/mailman/bin/qrunner, line 77, in ?
from Mailman.i18n import _
File /users/rtfm/mailman/Mailman/i18n.py, line 18, in ?
import time
ImportError: No module named time
Traceback (most recent call last):
I get the above messages continuously. What's happening here?
Mind you, when I had python 2.1 installed, I had no problem running mailmanctl
(except that mail sent to lists would yield the message near the top of this
e-mail. With python2.2.2 installed, I can't even get mailmanctl to run
properly... or rather, whatever it's running is giving me the errors directly
above.
And remember, *after* I installed python 2.2.2, I *rebuilt* mailman.
So, what should I do here?
If python's an issue, I'll go back to python 2.1 and hope someone here can help
me fix the problem with the mailer-daemon message. At least python 2.1, I could
run the mailman startup script.
(Note, the machine mailman is built on is Solaris 2.8.
Thanks in advance!
Steve Rifkin
[EMAIL PROTECTED]
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
Re: [Mailman-Users] Passwords of members UPDATE
A better solution would be to upgrade to MM2.1. It uses sha1 hashing, which will always be available. OK, I upgraded to MM2.1. After having to run check_perms with -f to fix permissions, I finally got the web pages up. When I go in as site admin and change the list admin's password for a list, I *still* cannot log in as the list admin. (I still receive the authentication error). And if I go back into the password change page for the list as the site admin, and if I put in a new list admin password and have a *different* verified password, I receive no errors when I click submit. However, if I run change_pw from the command line, changing the password for the list admin for the specific list, them, I CAN log in! :) So, it's the web interface that's screwing up. We're narrowing this one down now... I hope! Any suggestions? Steve Rifkin [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
What are you using for Password authentication on your system? Are you using PAMs? What does your /etc/nsswitch.conf file look like (are you using NIS)? NIS is used, but the mailman user account info is local to the web server. Mailman's home directory, though, is shared between the web server and the mail server. Some nsswitch.conf entries: passwd: compat group: files nis hosts: dns nis [NOTFOUND=return] files netgroup: nis automount: files nis aliases:files nis But again, I never had the list-admin authentication problem until I upgraded the Apache server. Whether the mailman list config databases before the apache upgrade had the nobody user set, I do not know. What could have changed from doing the apache upgrade? The user that CGI scripts get run by? Our cgi-scripts are working ok. Steve Rifkin [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
Just did another reinstall of 2.0.13. Again, installed with no problems. Check_perm ran fine... again And, the list ownerships for the config.db file for my test list is: -rw-rw 1 mailman mailman 3169 Jan 03 11:57 config.db (owned and group-owned by mailman) Then, I log into the list as the site admin, and change the lists's admin's password. When I do, the config.db file now has these attributes: -rw-rw 1 nobody mailman 3169 Jan 03 14:35 config.db Yes, nobody has replaced mailman as owner again And the list admin gets an authentication error trying to log in to its list. If, as site admin, I once again change the list admin's pwd (this time to a longer password, so that hopefully, config.db would change size) and log out, the config.db file remains the same size with the updated timestamp. -rw-rw 1 nobody mailman 3169 Jan 03 14:36 config.db Still owned by nobody! (yet, still group-owned by mailman) And still not allowing list admin's to log in... onl log in... only site admin and users can log in. (and this happens to all of our lists). Running check_perms again (now that nobody is the owner and mailman is the group owner of the config.db files), I still receive No problems found Since the only signs of error are 1) the Authentication failed error for the list admins, and 2) config.db doesn't looks as if it is updated [comparing the size of the of current and previous config.db files]... ...is there any way to do a trace of what is happening? Can python be used for this? It's almost as if the list admin password being changed by the site admin never really updates the config.db file. Oh, I even tried the setup using the mailman group consisting of mailman and nobody. Steve Rifkin [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members
My suggestion to you is that you re-install Python, then re-install
Mailman. Both are fairly easy to do. The order is important - you
definitely want to re-install Mailman after installing Python.
OK, reinstalled python. Python works. (v2.1)
Then, reinstalled mailman (v2.0.13). Mailman still does *not* allow for admin
logins... only site and user logins. No errors logged!
All built from scratch... i.e. with ./configure make make install
on Solaris 2.6.
Good Luck (and if you happen to hang that way: Merry Christmas!)
Have a great holiday. Thanks! :)
Oh, and if you have any other ideas on what to do (anybody reading), please let
me know. This is very frustrating.
I'd love to downgrade back to 2.08 without losing my 2.0.13 archive data.
Anyone know how? 2.08 had worked fine before the 2.13 upgrade. But, 2.08
won't let me install it, because a higher version is already on.
Steve
Jon Carnes
==
On Mon, 2002-12-23 at 15:29, Steve Rifkin wrote:
Hi Jon!
Well, I did what you said... I used dumpdb to look at the encrypted password
for
a list. Then I changed the list admin pw for th list (logged in as the site
admin), and did a dumpdb again. I get the same encrypted password for the
list
admin (and therefore, still cannot log in as the admin).
What else can I try?
Thanks!
Steve
[EMAIL PROTECTED]
Subject: Re: [Mailman-Users] Passwords of members
From: Jon Carnes [EMAIL PROTECTED]
To: Steve Rifkin [EMAIL PROTECTED]
Cc: Mailman users Mailing list [EMAIL PROTECTED]
Content-Transfer-Encoding: 7bit
Date: 14 Dec 2002 20:36:07 -0500
Mime-Version: 1.0
X-Keywords:
In this version of Mailman the admin password for the list is encrypted,
well sort of... If you want to be clever and look at the source you can
easily figure this part out.
In any case, I've seen this problem before after an upgrade and it seems
to be that the encryption has changed. Normally resetting the password
via the web-admin works. I don't know why it's not working in your case
- unless you upgraded python and didn't re-install Mailman.
You might want to use dumpdb to look at the encrypted password, then try
to change it via the web admin and use dumpdb to see if it actually
changed.
Good Luck - Jon Carnes
On Sat, 2002-12-14 at 14:24, Steve Rifkin wrote:
Now that we can see the plain-text passwords of members using dumpdb on
the
config.db file, how can we see the specific list admin password for a
given
list? I could see plaintext passwords for the users, but for what
looked
like
the admin, I saw something very different than what the password is set
to.
A (bogus) example of this: Here are what looks like the admin lines
from
the
config.db dump:
'owner': ['[EMAIL PROTECTED]'],
'password': '=\x2b\x4abH\xgg3\x3n\x5e\x4e\xh_\xb6\xb2\x8n\xqp',
'passwords': {[EMAIL PROTECTED]': 'sdjlkl',
'[EMAIL PROTECTED]': 'nasdat',
'[EMAIL PROTECTED]': 'kljlkd',
'[EMAIL PROTECTED]': 'jsdafk',
},
So, the user passwords are pretty clear, but the owner's password is not
listed
in plain text as to what the password is.
How do we get that password? If I had that info, I could check to see
why
we
are able to log into our mm site with the site-wide password or the user
(subscriber) passwords, but *not* the list admin's password. (for mm
2.0.13)
Thanks!
Steve
[EMAIL PROTECTED]
--
Date: 13 Dec 2002 16:58:52 -0500
From: Jon Carnes [EMAIL PROTECTED]
To: Gary Smith [EMAIL PROTECTED]
Cc: Mailman users Mailing list [EMAIL PROTECTED]
The archives have a script for this (for versions 2.0.x), and you can
easily modify the script found here to do it (you will have to be
system
admin):
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.007.htp
On Fri, 2002-12-13 at 12:25, Gary Smith wrote:
Hi.
How do I find out the passwords of subscribers with out clicking on
the
'send me my password button'?
Thanks,
Gary Smith
Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator
Technical Director
[EMAIL PROTECTED]
410-516-6281
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members
The other interesting thing I found is that once I log into a list as the SITE ADMIN, if I go to change the list admin's password, I can put anything into: Enter new password: Then, I can put something different into: Confirm new password: I can then proceed to click Submit Your Changes, and I receive NO error that the password I put in and the confirmation of that password are different. It acts like it's trying to submit, but then, just returns me back to the top of the list admin page for the list. I also notice that if I put some bogus password into the Enter Current Password fied at the bottom, and hit submit, I get: Error: Incorrect administrator password displayed at the top of the page. That tells me that the list thinks it has some list admin password set... but, there's no way to figure out what it is? Steve teve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
Going an extra step, I compiled python 2.2.2 and put it in place. I then rebuilt mailman (based on the new python). Again, mailman works EXCEPT FOR list admin passwords. I'm running out of options. I'm now at python 2.2.2 and mailman 2.0.13, and my list admins cannot log in, but the site admin and users can. When the site admin changes the list admin password for a list, should there be a confirmation of the change AFTER submit is clicked? WHOA! Here is something weird... all my mailman files are owned by user mailman and group mailman. At the list level, for a test list (mmtest), the dir looks like: -rw-rw 1 mailman mailman 3082 Dec 27 11:48 config.db -rw-rw 1 mailman mailman 3082 Dec 27 11:47 config.db.last -rw-rw-r-- 1 mailman mailman 869 Dec 26 16:57 request.db -rw-rw-r-- 1 mailman mailman 189 Jan 30 2002 handle_opts.html -rw-rw-r-- 1 mailman mailman 1026 Jan 30 2002 headfoot.html -rw-rw-r-- 1 mailman mailman 3136 Jan 30 2002 listinfo.html -rw-rw-r-- 1 mailman mailman 4106 Jan 30 2002 options.html -rw-rw-r-- 1 mailman mailman 1169 Jan 30 2002 roster.html -rw-rw-r-- 1 mailman mailman 198 Jan 30 2002 subscribe.html -rw-rw-r-- 1 mailman mailman 1706 Jan 30 2002 admindbpreamble.html That's ok. HOWEVER, whenever I log into a list or try to make changes to a list as the site admin, the ownership changes for config.db: -rw-rw 1 nobody mailman 3082 Dec 27 11:50 config.db -rw-rw 1 mailman mailman 3082 Dec 27 11:48 config.db.last -rw-rw-r-- 1 mailman mailman 869 Dec 26 16:57 request.db -rw-rw-r-- 1 mailman mailman 189 Jan 30 2002 handle_opts.html -rw-rw-r-- 1 mailman mailman 1026 Jan 30 2002 headfoot.html -rw-rw-r-- 1 mailman mailman 3136 Jan 30 2002 listinfo.html -rw-rw-r-- 1 mailman mailman 4106 Jan 30 2002 options.html -rw-rw-r-- 1 mailman mailman 1169 Jan 30 2002 roster.html -rw-rw-r-- 1 mailman mailman 198 Jan 30 2002 subscribe.html -rw-rw-r-- 1 mailman mailman 1706 Jan 30 2002 admindbpreamble.html And the filesize for config.db does not change. I suspect that the config.db file is not changing at all when I attempt changes logged in as the site admin. The only change to the file is config.db's ownership keeps changing to nobody! Why? Maybe the above is a clue to the problem! Any thoughts? Steve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members UPDATE
Oh, I should also add that, as user mailman, when I run: bin/check_perms I get: No problems found Steve -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members
Hi Jon!
Well, I did what you said... I used dumpdb to look at the encrypted password for
a list. Then I changed the list admin pw for th list (logged in as the site
admin), and did a dumpdb again. I get the same encrypted password for the list
admin (and therefore, still cannot log in as the admin).
What else can I try?
Thanks!
Steve
[EMAIL PROTECTED]
Subject: Re: [Mailman-Users] Passwords of members
From: Jon Carnes [EMAIL PROTECTED]
To: Steve Rifkin [EMAIL PROTECTED]
Cc: Mailman users Mailing list [EMAIL PROTECTED]
Content-Transfer-Encoding: 7bit
Date: 14 Dec 2002 20:36:07 -0500
Mime-Version: 1.0
X-Keywords:
In this version of Mailman the admin password for the list is encrypted,
well sort of... If you want to be clever and look at the source you can
easily figure this part out.
In any case, I've seen this problem before after an upgrade and it seems
to be that the encryption has changed. Normally resetting the password
via the web-admin works. I don't know why it's not working in your case
- unless you upgraded python and didn't re-install Mailman.
You might want to use dumpdb to look at the encrypted password, then try
to change it via the web admin and use dumpdb to see if it actually
changed.
Good Luck - Jon Carnes
On Sat, 2002-12-14 at 14:24, Steve Rifkin wrote:
Now that we can see the plain-text passwords of members using dumpdb on the
config.db file, how can we see the specific list admin password for a given
list? I could see plaintext passwords for the users, but for what looked
like
the admin, I saw something very different than what the password is set to.
A (bogus) example of this: Here are what looks like the admin lines from
the
config.db dump:
'owner': ['[EMAIL PROTECTED]'],
'password': '=\x2b\x4abH\xgg3\x3n\x5e\x4e\xh_\xb6\xb2\x8n\xqp',
'passwords': {[EMAIL PROTECTED]': 'sdjlkl',
'[EMAIL PROTECTED]': 'nasdat',
'[EMAIL PROTECTED]': 'kljlkd',
'[EMAIL PROTECTED]': 'jsdafk',
},
So, the user passwords are pretty clear, but the owner's password is not
listed
in plain text as to what the password is.
How do we get that password? If I had that info, I could check to see why
we
are able to log into our mm site with the site-wide password or the user
(subscriber) passwords, but *not* the list admin's password. (for mm
2.0.13)
Thanks!
Steve
[EMAIL PROTECTED]
--
Date: 13 Dec 2002 16:58:52 -0500
From: Jon Carnes [EMAIL PROTECTED]
To: Gary Smith [EMAIL PROTECTED]
Cc: Mailman users Mailing list [EMAIL PROTECTED]
The archives have a script for this (for versions 2.0.x), and you can
easily modify the script found here to do it (you will have to be system
admin):
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.007.htp
On Fri, 2002-12-13 at 12:25, Gary Smith wrote:
Hi.
How do I find out the passwords of subscribers with out clicking on the
'send me my password button'?
Thanks,
Gary Smith
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] list admin pw not working -- weird update,troubles, but some more clues...
I should add that the timestamp on the config.db file DID in fact change after I
changed the list admin password, just not the encrypted password itself.
And no error was given when I made the password change.
Are there mailman logs for login attempts? Any other ways to troubleshoot this?
And here's the really weird part... when I log in as the site admin to one of
the lists, and go to change the listadmin pw, if I put in the new password and
put in a DIFFERENT password in the confirm new password field and click Submit
Your Changes, I *do not* get an error... when I should, since the password I
enter and the one I confirm are different. So, why would I not be getting an
error? I should at least be getting an error flagged somewhere. But where?
It's certainly not on the list page, and it is not in the Mailman logs either.
Steve
[EMAIL PROTECTED]
Well, I did what you said... I used dumpdb to look at the encrypted password
for
a list. Then I changed the list admin pw for th list (logged in as the site
admin), and did a dumpdb again. I get the same encrypted password for the
list
admin (and therefore, still cannot log in as the admin).
What else can I try?
Thanks!
Steve
[EMAIL PROTECTED]
Subject: Re: [Mailman-Users] Passwords of members
From: Jon Carnes [EMAIL PROTECTED]
To: Steve Rifkin [EMAIL PROTECTED]
Cc: Mailman users Mailing list [EMAIL PROTECTED]
Content-Transfer-Encoding: 7bit
Date: 14 Dec 2002 20:36:07 -0500
Mime-Version: 1.0
X-Keywords:
In this version of Mailman the admin password for the list is encrypted,
well sort of... If you want to be clever and look at the source you can
easily figure this part out.
In any case, I've seen this problem before after an upgrade and it seems
to be that the encryption has changed. Normally resetting the password
via the web-admin works. I don't know why it's not working in your case
- unless you upgraded python and didn't re-install Mailman.
You might want to use dumpdb to look at the encrypted password, then try
to change it via the web admin and use dumpdb to see if it actually
changed.
Good Luck - Jon Carnes
On Sat, 2002-12-14 at 14:24, Steve Rifkin wrote:
Now that we can see the plain-text passwords of members using dumpdb on
the
config.db file, how can we see the specific list admin password for a
given
list? I could see plaintext passwords for the users, but for what looked
like
the admin, I saw something very different than what the password is set
to.
A (bogus) example of this: Here are what looks like the admin lines from
the
config.db dump:
'owner': ['[EMAIL PROTECTED]'],
'password': '=\x2b\x4abH\xgg3\x3n\x5e\x4e\xh_\xb6\xb2\x8n\xqp',
'passwords': {[EMAIL PROTECTED]': 'sdjlkl',
'[EMAIL PROTECTED]': 'nasdat',
'[EMAIL PROTECTED]': 'kljlkd',
'[EMAIL PROTECTED]': 'jsdafk',
},
So, the user passwords are pretty clear, but the owner's password is not
listed
in plain text as to what the password is.
How do we get that password? If I had that info, I could check to see why
we
are able to log into our mm site with the site-wide password or the user
(subscriber) passwords, but *not* the list admin's password. (for mm
2.0.13)
Thanks!
Steve
[EMAIL PROTECTED]
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Passwords of members
Now that we can see the plain-text passwords of members using dumpdb on the
config.db file, how can we see the specific list admin password for a given
list? I could see plaintext passwords for the users, but for what looked like
the admin, I saw something very different than what the password is set to.
A (bogus) example of this: Here are what looks like the admin lines from the
config.db dump:
'owner': ['[EMAIL PROTECTED]'],
'password': '=\x2b\x4abH\xgg3\x3n\x5e\x4e\xh_\xb6\xb2\x8n\xqp',
'passwords': {[EMAIL PROTECTED]': 'sdjlkl',
'[EMAIL PROTECTED]': 'nasdat',
'[EMAIL PROTECTED]': 'kljlkd',
'[EMAIL PROTECTED]': 'jsdafk',
},
So, the user passwords are pretty clear, but the owner's password is not listed
in plain text as to what the password is.
How do we get that password? If I had that info, I could check to see why we
are able to log into our mm site with the site-wide password or the user
(subscriber) passwords, but *not* the list admin's password. (for mm 2.0.13)
Thanks!
Steve
[EMAIL PROTECTED]
--
Date: 13 Dec 2002 16:58:52 -0500
From: Jon Carnes [EMAIL PROTECTED]
To: Gary Smith [EMAIL PROTECTED]
Cc: Mailman users Mailing list [EMAIL PROTECTED]
The archives have a script for this (for versions 2.0.x), and you can
easily modify the script found here to do it (you will have to be system
admin):
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.007.htp
On Fri, 2002-12-13 at 12:25, Gary Smith wrote:
Hi.
How do I find out the passwords of subscribers with out clicking on the
'send me my password button'?
Thanks,
Gary Smith
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] HELP! Getting different Import Error:python2.2/lib-dynload/_socket.so: bad ELF flags value: 256
For that specific problem, we re-installed the previous version (2.1) of python, and we do not get errors. Installing python 2.2 yields us the error. It's pretty consistant in terms of when we put on 2.2, we get the error, but when we put back 2.1, we're fine. So, we're at 2.1 and most things are working... except for the list admin passwd authentication problem that I have submitted in a different e-mail. Steve MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Date: Thu, 28 Nov 2002 23:34:00 -0500 To: Steve Rifkin [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] HELP! Getting different Import Error: python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 From: [EMAIL PROTECTED] (Barry A. Warsaw) X-Attribution: BAW X-Oblique-Strategy: Short circuit X-Url: http://barry.wooz.org SR == Steve Rifkin [EMAIL PROTECTED] writes: SR Anyone familiar with the error (we're running python 2.2.2 and SR mailman 2.08): SR admin(7162): ImportError: ld.so.1: /usr/local/bin/python: SR fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad SR ELF flags value: 256 This can only mean that your Python installation is messed up. -Barry Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator Technical Director [EMAIL PROTECTED] 410-516-6281 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] HELP! Getting different Import Error:python2.2/lib-dynload/_socket.so: bad ELF flags value: 256
root@sun(~) python -V Python 2.1 root@sun(~) As you can see, the version of python is 2.1, and yes, the version we tried, but got the error with, was 2.2.2. From the 2.1 README file: == This is Python version 2.1 == Copyright (c) 2001 Python Software Foundation. All rights reserved. Copyright (c) 2000 BeOpen.com. All rights reserved. Copyright (c) 1995-2001 Corporation for National Research Initiatives. All rights reserved. Copyright (c) 1991-1995 Stichting Mathematisch Centrum. All rights reserved. == MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Date: Fri, 13 Dec 2002 10:57:11 -0500 To: Steve Rifkin [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] HELP! Getting different Import Error: python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 From: [EMAIL PROTECTED] (Barry A. Warsaw) X-Attribution: BAW X-Oblique-Strategy: (Organic) machinery X-Url: http://barry.wooz.org SR == Steve Rifkin [EMAIL PROTECTED] writes: SR For that specific problem, we re-installed the previous SR version (2.1) of python, and we do not get errors. Installing SR python 2.2 yields us the error. It's pretty consistant in SR terms of when we put on 2.2, we get the error, but when we put SR back 2.1, we're fine. So, we're at 2.1 and most things are SR working... except for the list admin passwd authentication SR problem that I have submitted in a different e-mail. That's very strange, especially since when you say Python 2.2 I think you really mean Python 2.2.2. Not sure which micro release Python 2.1 is. While it /shouldn't/ matter, Python 2.2.2 and Python 2.1.3 are recommended. FTR, I run MM2.1cvs off of Python 2.1.3 on python.org (some mysterious Linux distro) and Python 2.2.2 (RH7.3) on my personal domains. I haven't seen any problems, but that doesn't mean there aren't Python issues on your particular platforms. -Barry -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] PLS HELP! Problems logging into mailman lists as list admin...
Hi! I hope someone can help me. I have recently upgraded from a working Mailman 2.0.8 to version 2.0.13. While Mailman 2.0.8 worked great, v2.0.13 is not totally working for me. Since the upgrade, I am having a problem with LIST ADMIN PASSWORD AUTHENTICATION via the web. As a user subscribed to a list, I am able to (via the web interface) successfully log in with the user list password to the user list options page. However, as the LIST ADMIN, any time I now log into the LIST ADMIN screen with the list admin password , I get authentication failed. However, I CAN log into any list admin screen with the *site-wide* master mailman admin password. I just cannot log into any list admin screens with the list-admin. Once I get into a *list admin* screen with the *site-wide password*, if I change that specific list's LIST ADMIN password, and they try to login as the LIST ADMIN, I still get an Authentication failed error. So, is this a bug of some sort in v 2.0.13? I had no problems with 2.0.8. Just a note too that I recently upgraded our Apache from 1.3.14 to 1.3.17. Python is at 2.1 We tried Pyton 2.2.2, but we get dynlink errors (ELF) with 2.2.2, so we dropped back to 2.1. Again, and this is important, everything worked with mailman 2.0.8. The upgrade to 2.0.13 has caused the problems with List Admin authentications via the web. Site-wide mailman and user mailman password authentication works fine. So, what could be happening? Is there anyway for the site admin to see the list admin passwords to see what mailman thinks it has? I considered downgrading back to Mailman 2.0.8, since that version had worked. However, mailman will not let you downgrade. When I try to re-install 2.0.8, it complains: Downgrade detected, from version 0x2000df0 to version 0x20008f0 This is probably not safe. Exiting.. So, I need to stay at 2.0.13. How can I fix this bug with list admin passwords for this version? Also, how does one change a list admin's password at the command line? Or is it only possible via the web? Thanks in advance! Steve Rifkin [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] HELP! List admin passwords not working in Mailman2.0.13
I have recently upgraded from a working Mailman 2.0.8 to version 2.0.13. While Mailman 2.0.8 worked great, v2.0.13 is not totally working for me. Since the upgrade, I am having a problem with LIST ADMIN PASSWORD AUTHENTICATION via the web. As a user subscribed to a list, I am able to (via the web interface) successfully log in with the user list password to the user list options page. However, as the LIST ADMIN, any time I now log into the LIST ADMIN screen with the list admin password , I get authentication failed. However, I CAN log into any list admin screen with the *site-wide* master mailman admin password. I just cannot log into any list admin screens with the list-admin. Once I get into a *list admin* screen with the *site-wide password*, if I change that specific list's LIST ADMIN password, and they try to login as the LIST ADMIN, I still get an Authentication failed error. So, is this a bug of some sort in v 2.0.13? I had no problems with 2.0.8. Just a note too that I recently upgraded our Apache from 1.3.14 to 1.3.17. Python is at 2.1 We tried Pyton 2.2.2, but we get dynlink errors (ELF) with 2.2.2, so we dropped back to 2.1. Again, and this is important, everything worked with mailman 2.0.8. The upgrade to 2.0.13 has caused the problems with List Admin authentications via the web. Site-wide mailman and user mailman password authentication works fine. So, what could be happening? Is there anyway for the site admin to see the list admin passwords to see what mailman thinks it has? I considered downgrading back to Mailman 2.0.8, since that version had worked. However, mailman will not let you downgrade. When I try to re-install 2.0.8, it complains: Downgrade detected, from version 0x2000df0 to version 0x20008f0 This is probably not safe. Exiting.. So, I need to stay at 2.0.13. How can I fix this bug with list admin passwords for this version? Also, how does one change a list admin's password at the command line? Or is it only possible via the web? Thanks in advance! Steve Rifkin [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
Still having troubles... I thought I'd start somewhat from scratch this time. Since mailman is failing with python errors that reference ssl, I've cleared out the ssl directory so that the ssl dir had nothing from a prior version in it. I rebuilt ssl (openssl-0.9.6g), and then, I rebuilt python 2.2.2, so that python, when being built, will only see the fresh openssl. Afterwords, I bring up mailman/listinfo via our web server, and once again received the error in the browser about a bug in Mailman 2.08 The logs from mailman this time indicate something different from last time. If you recall, last time, I was receiving: admin(3540): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 Clearly, ssl looked involved. But, this go around led to different errors, not related to ssl (as far as I can see.) admin(3771): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 Can anyone help out with this? The full error listing is below. Thanks! Steve admin(3771): [- Mailman Version: 2.0.8 -] admin(3771): [- Traceback --] admin(3771): Traceback (most recent call last): admin(3771): File /home/mailman/scripts/driver, line 80, in run_main admin(3771): import Mailman.pythonlib.cgi admin(3771): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(3771): import urllib admin(3771): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(3771): import socket admin(3771): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(3771): from _socket import * admin(3771): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 admin(3771): [- Python Information -] admin(3771): sys.version= 2.2.2 (#1, Nov 25 2002, 15:28:57) [GCC 2.95.2 19991024 (release)] admin(3771): sys.executable = /usr/local/bin/python admin(3771): sys.prefix = /usr/local admin(3771): sys.exec_prefix= /usr/local admin(3771): sys.path = /usr/local admin(3771): sys.platform = sunos5 admin(3771): [- Environment Variables -] admin(3771):PYTHONPATH: /home/mailman admin(3771):SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(3771):SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(3771):SERVER_ADMIN: [EMAIL PROTECTED] admin(3771):SCRIPT_NAME: /mailman/listinfo admin(3771):SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(3771):SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS admin(3771):REQUEST_METHOD: GET admin(3771):HTTP_HOST: www.cs.jhu.edu admin(3771):SCRIPT_URL: /mailman/listinfo admin(3771):SERVER_PROTOCOL: HTTP/1.1 admin(3771):QUERY_STRING: admin(3771):HTTP_CONNECTION: keep-alive admin(3771):HTTP_CACHE_CONTROL: max-age=0 admin(3771):REQUEST_URI: /mailman/listinfo admin(3771):HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8, video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(3771):HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(3771):HTTP_USER_AGENT: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020829 admin(3771):TZ: US/Eastern admin(3771):SERVER_NAME: www.cs.jhu.edu admin(3771):REMOTE_ADDR: 128.220.13.39 admin(3771):REMOTE_PORT: 42200 admin(3771):HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(3771):SERVER_PORT: 80 admin(3771):GATEWAY_INTERFACE: CGI/1.1 admin(3771):DOCUMENT_ROOT: /users/httpd/htdocs admin(3771):HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(3771):SERVER_ADDR: 128.220.13.101 admin(3771):HTTP_KEEP_ALIVE: 300 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] New apache is causing my mailman to fail...
Hi All! I'm currently running Mailman version 2.0.8. Until last week, our Apache webserver (1.3.14) interfaced with our Mailman just fine. Last week, we needed to upgrade our Apache Web server to 1.3.27. We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We're also running Python version 2.2.2. Since then, we've been getting the following error attempting to access mailman lists from our website: = Bug in Mailman version 2.0.8 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 even tried reinstalling Python to make sure it saw the updated OPENSSL stuff. Anyway, from the web, when we do a mailman/listinfo and get the above error, the mailman error log reports: Nov 21 11:03:35 2002 admin(18834): admin(18834): [- Mailman Version: 2.0.8 -] admin(18834): [- Traceback --] admin(18834): Traceback (most recent call last): admin(18834): File /home/mailman/scripts/driver, line 80, in run_main admin(18834): import Mailman.pythonlib.cgi admin(18834): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(18834): import urllib admin(18834): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(18834): import socket admin(18834): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(18834): from _socket import * admin(18834): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 admin(18834): [- Python Information -] admin(18834): sys.version= 2.2.2 (#1, Nov 20 2002, 18:28:42) [GCC 2.95.2 19991024 (release)] admin(18834): sys.executable = /usr/local/bin/python admin(18834): sys.prefix = /usr/local admin(18834): sys.exec_prefix= /usr/local admin(18834): sys.path = /usr/local admin(18834): sys.platform = sunos5 admin(18834): [- Environment Variables -] admin(18834): HTTP_PRAGMA: no-cache admin(18834): PYTHONPATH: /home/mailman admin(18834): SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(18834): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(18834): SERVER_ADMIN: [EMAIL PROTECTED] admin(18834): SCRIPT_NAME: /mailman/listinfo admin(18834): SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(18834): SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS Note the Import error above. So... again, it worked until we installed the new Apache and new openssl. Then, it stopped working giving the above errors. Rebuilding python did not help. Any ideas of what I can try? Is there really a bug in our version of Mailman? And should I be reinstalling Mailman? or is there an easier fix? Thanks a bunch in advance, and if you could seperately CC: me on your post to the mailman list, that would be much appreciated. Thanks! Steve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] New apache is causing my mailman to fail...
Hi Tom! Sorry, left out the server info... Installing on Solaris 2.6 using the: * 2170570 Aug 9 13:54:01 2002 openssl-0.9.6g.tar.gz [LATEST] * from openssl.org. For openssl source, I ncompressed and did (as INSTALL suggested): $ ./config $ make $ make test $ make install Nothing failed along the way. If I reinstalled openssl again (although, since there were no failures when I first installed it, I wouldn't expect there to be now), would I need to reinstall python, since python likes to configure itself with ssl, if ssl exists? Steve From: Thomas Oakes [EMAIL PROTECTED] To: Steve Rifkin [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: [Mailman-Users] New apache is causing my mailman to fail... Date: Thu, 21 Nov 2002 13:55:47 -0500 From this line in the traceback, /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 I looks like you have a problem with your new install of openssl. How did you install it? A package? and what OS are you using. You might reinstall openssl from source if possible. I'm not entirely sure what the 'bad ELF flags value' means but it sounds like you're using a precompiled openssl library on a system that doesn't support it. Use the source, Luke ==Tom== -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Rifkin Sent: Thursday, November 21, 2002 1:04 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Mailman-Users] New apache is causing my mailman to fail... Hi All! I'm currently running Mailman version 2.0.8. Until last week, our Apache webserver (1.3.14) interfaced with our Mailman just fine. Last week, we needed to upgrade our Apache Web server to 1.3.27. We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We're also running Python version 2.2.2. Since then, we've been getting the following error attempting to access mailman lists from our website: = Bug in Mailman version 2.0.8 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 even tried reinstalling Python to make sure it saw the updated OPENSSL stuff. Anyway, from the web, when we do a mailman/listinfo and get the above error, the mailman error log reports: Nov 21 11:03:35 2002 admin(18834): admin(18834): [- Mailman Version: 2.0.8 -] admin(18834): [- Traceback --] admin(18834): Traceback (most recent call last): admin(18834): File /home/mailman/scripts/driver, line 80, in run_main admin(18834): import Mailman.pythonlib.cgi admin(18834): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(18834): import urllib admin(18834): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(18834): import socket admin(18834): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(18834): from _socket import * admin(18834): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 admin(18834): [- Python Information -] admin(18834): sys.version= 2.2.2 (#1, Nov 20 2002, 18:28:42) [GCC 2.95.2 19991024 (release)] admin(18834): sys.executable = /usr/local/bin/python admin(18834): sys.prefix = /usr/local admin(18834): sys.exec_prefix= /usr/local admin(18834): sys.path = /usr/local admin(18834): sys.platform = sunos5 admin(18834): [- Environment Variables -] admin(18834): HTTP_PRAGMA: no-cache admin(18834): PYTHONPATH: /home/mailman admin(18834): SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(18834): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(18834): SERVER_ADMIN: [EMAIL PROTECTED] admin(18834): SCRIPT_NAME: /mailman/listinfo admin(18834): SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(18834): SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS Note the Import error above. So... again, it worked until we installed the new Apache and new openssl. Then, it stopped working giving the above errors. Rebuilding python did not help. Any ideas of what I can try? Is there really a bug in our version of Mailman? And should I be reinstalling Mailman? or is there an easier fix? Thanks a bunch in advance, and if you could seperately CC: me on your post to the mailman list, that would be much appreciated. Thanks! Steve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable
RE: [Mailman-Users] New apache is causing my mailman to fail...
Hmmm... Actually, I need to modify one of my earlier statements... Last week, we needed to upgrade our Apache Web server to 1.3.27. Mailman failed with errors I submitted earlier (that error log entry was from last night, but it was similar to what we got a week ago, which you'll find below). At that time (last week), though, we were running an older version of openssl (plain 'ol 0.9.6, if I recall). ** Before the Apache install last week, mailman worked fine with the Apache 1.3.14 and the older openssl. With the newer Apache and the older openssl, mailman's web interface broke with the errors I submitted. ** We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We actually did this (upgrading to the latest openssl) recently, in an attempt to hopefully have mailman work with the latest version of Apache. ( Oh, and we upgraded to the latest openssl, too, because of the many exploits of the older openssl. :) So, even before we upgraded openssl, merely upgrading apache broke our mailman web interface. Before we even upgraded openssl, but AFTER we upgraded Apache, here are the mailman error logs: dmin(8622): [- Mailman Version: 2.0.8 -] admin(8622): [- Traceback --] admin(8622): Traceback (most recent call last): admin(8622): File /home/mailman/scripts/driver, line 80, in run_main admin(8622): import Mailman.pythonlib.cgi admin(8622): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(8622): import urllib admin(8622): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(8622): import socket admin(8622): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(8622): from _socket import * admin(8622): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF f lags value: 768 admin(8622): [- Python Information -] admin(8622): sys.version= 2.2.2 (#1, Nov 8 2002, 16:56:01) [GCC 2.95.2 19991024 (release)] admin(8622): sys.executable = /usr/local/bin/python admin(8622): sys.prefix = /usr/local admin(8622): sys.exec_prefix= /usr/local admin(8622): sys.path = /usr/local admin(8622): sys.platform = sunos5 admin(8622): [- Environment Variables -] admin(8622):PYTHONPATH: /home/mailman admin(8622):SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(8622):SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(8622):SERVER_ADMIN: [EMAIL PROTECTED] admin(8622):SCRIPT_NAME: /mailman/listinfo admin(8622):SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(8622):SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS You;ll see these are similar to the logs we got AFTER we installed the newer openssl. Steve -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
Python worked fine before and after the openssl upgrade. Mailman worked before the openssl upgrade but only with the older Apache. With the new Apache and older ssl, mailman's web interface broke. Same errors. With the new openssl, we still get the same errors. As a precaution, I reinstalled python again. Openssl and python and apache all work, just not with mailman. Steve Date: Thu, 21 Nov 2002 12:50:38 -0700 From: Ashley M. Kirchner [EMAIL PROTECTED] X-Accept-Language: en MIME-Version: 1.0 To: Steve Rifkin [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [Mailman-Users] New apache is causing my mailman to fail... Content-Transfer-Encoding: 7bit Steve Rifkin wrote: admin(8622): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 My guess would be that you compiled python yourself, against the old version of openssl. now that you've upgraded openssl, python doesn't work because it can't find the old openssl. Or at least, the library isn't the same. If you tried running python by itself (just type in /usr/local/bin/python), you may find that it won't work either. You'll have to recompile python again. -- W | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator Technical Director [EMAIL PROTECTED] 410-516-6281 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
No, we hadn't touched mailman at all. Really, all we had done was upgrade Apache. Upgrading ssl and rebuilding python happened AFTER mailman's web interface stopped working. Steve Date: Thu, 21 Nov 2002 13:47:51 -0700 From: Ashley M. Kirchner [EMAIL PROTECTED] X-Accept-Language: en MIME-Version: 1.0 To: Steve Rifkin [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] New apache is causing my mailman to fail... Content-Transfer-Encoding: 7bit Steve Rifkin wrote: Python worked fine before and after the openssl upgrade. Mailman worked before the openssl upgrade but only with the older Apache. With the new Apache and older ssl, mailman's web interface broke. Same errors. With the new openssl, we still get the same errors. As a precaution, I reinstalled python again. Openssl and python and apache all work, just not with mailman. Did you guys by any chance recompile mailman as well? (not that it should make any difference, but it wouldn't hurt) -- W | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator Technical Director [EMAIL PROTECTED] 410-516-6281 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
