Mailman 3 October 2000 - Mailman-Users

2.0rc1 / no explicit Reply-To: header
by Michael Brennen Oct. 27, 2000

Oct. 27, 2000

I've got one list that I run explicit Reply-To: headers on. I just upgraded from a lightly patched b6 to 2.0rc1, and the Reply-To: header is still not being sent to the list. Since this version is a release candidate it seemed reporting. -- Michael

2 2

Something is fishy with RedHat 7 + Mailman 2.0rc1
by David B. O'Donnell Oct. 27, 2000

Oct. 27, 2000

I moved from RedHat 6.2 to RedHat 7.0 last night. Prior to the move, I copied all the data from ~mailman to a separate disk. The RedHat 7 install was a "fresh" one, so none of the old 6.2 stuff is lying around. I also applied the errata patch and updated to the latest package list from their update server. I copied the ~mailman files into the new /home/ directory, then did a straight install from the mailman 2.0rc1 archive. I made certain the smrsh symlink is in place, ~mailman/bin/check_perms returns no problems, and that all the list aliases are in place and working. I have triple-checked the relevant lines in httpd.conf to make sure they work. Going to http://www.destinyinternet.com/listinfo shows that there are no public lists on the server; however, two are supposed to be--one active list and one test list. Going to http://www.destinyinternet.com/listinfo/david-test brings me to the proper list info page. This works for the other three lists I host (one is public, two are private). Going to http://www.destinyinternet.com/admin/david-test *presently* sends me off into la-la land, where I time out before I get the page. Earlier tonight, however, it showed up fine -- for david-test ONLY, with the other three lists also sending me off into la-la land. (I am tailing the error log for mailman, plus the httpd access and error logs for www.destinyinternet.com, all the time. So far everything seems normal) When I *was* able to get into .../admin/david-test, I clicked on the "pending administrative requests" link and got an error. This is what my mailman error log shows: admin(19363): [----- Mailman Version: 2.0rc1 -----] admin(19363): [----- Traceback ------] admin(19363): Traceback (innermost last): admin(19363): File "/home/mailman/scripts/driver", line 96, in run_main admin(19363): main() admin(19363): File "/home/mailman/Mailman/Cgi/admindb.py", line 95, in main admin(19363): mlist.Save() admin(19363): File "/home/mailman/Mailman/MailList.py", line 845, in Save admin(19363): self.SaveRequestsDb() admin(19363): File "/home/mailman/Mailman/ListAdmin.py", line 93, in SaveRequestsDb admin(19363): self.__closedb() admin(19363): File "/home/mailman/Mailman/ListAdmin.py", line 80, in __closedb admin(19363): fp = open(self.__filename, 'w') admin(19363): IOError: [Errno 13] Permission denied: '/home/mailman/lists/david-test/request.db' admin(19363): [----- Python Information -----] admin(19363): sys.version = 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] admin(19363): sys.executable = /usr/bin/python admin(19363): sys.prefix = /usr admin(19363): sys.exec_prefix= /usr admin(19363): sys.path = /usr admin(19363): sys.platform = linux-i386 admin(19363): [----- Environment Variables -----] admin(19363): DOCUMENT_ROOT: /web/domains/destinynewmedia.net admin(19363): SERVER_ADDR: 209.8.223.164 admin(19363): QUERY_STRING: admin(19363): PATH_TRANSLATED: /web/domains/destinynewmedia.net/david-test admin(19363): REMOTE_ADDR: 209.8.223.165 admin(19363): HTTP_UA_OS: MacOS admin(19363): HTTP_ACCEPT_LANGUAGE: en admin(19363): GATEWAY_INTERFACE: CGI/1.1 admin(19363): SERVER_NAME: www.destinynewmedia.net admin(19363): HTTP_CONNECTION: Keep-Alive admin(19363): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.0; Mac_PowerPC) admin(19363): HTTP_ACCEPT: */* admin(19363): REQUEST_URI: /mailman/admindb/david-test admin(19363): HTTP_UA_CPU: PPC admin(19363): HTTP_EXTENSION: Security/Remote-Passphrase admin(19363): SCRIPT_FILENAME: /home/mailman/cgi-bin//admindb admin(19363): PATH_INFO: /david-test admin(19363): HTTP_HOST: www.destinynewmedia.net admin(19363): REQUEST_METHOD: GET admin(19363): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.14 Server at <A HREF="mailto:atropos@fates.org">www.destinynewmedia.net</A> Port 80</ADDRESS> admin(19363): SCRIPT_NAME: /mailman/admindb admin(19363): SERVER_ADMIN: atropos(a)fates.org admin(19363): SERVER_SOFTWARE: Apache/1.3.14 (Unix) admin(19363): PYTHONPATH: /home/mailman admin(19363): HTTP_COOKIE: david-test:admin=280200000069c6abf739732800000063396533663730313833613332633638333366346337353561326162626461313563313061306536 admin(19363): SERVER_PROTOCOL: HTTP/1.1 admin(19363): REMOTE_PORT: 49365 admin(19363): HTTP_REFERER: http://www.destinynewmedia.net/mailman/admin/david-test The listing for 'request.db' shows: -rw-r--r-- 1 mailman mailman 2 Oct 25 20:58 request.db This is the same for the other lists. FWIW, I noticed while trying to discover why I was not getting posts to one of my lists that I wasn't in the member list. When I tried to run the add_member script, it just sits and spins and as far as I can tell hangs. This is the traceback I get when I kill the process: Traceback (innermost last): File "./add_members", line 221, in ? main() File "./add_members", line 170, in main ml = MailList.MailList(listname) File "/home/mailman/Mailman/MailList.py", line 77, in __init__ self.Lock() File "/home/mailman/Mailman/MailList.py", line 1322, in Lock self.__lock.lock(timeout) File "/home/mailman/Mailman/LockFile.py", line 286, in lock self.__sleep() File "/home/mailman/Mailman/LockFile.py", line 424, in __sleep time.sleep(interval) KeyboardInterrupt Lastly, I'm noticing that it takes a LONG time for posts to actually make it to lists. Like up to an hour for them to go from arriving at the wrapper script to actually being posted. I'm at a loss for what's going on. Anyone with ideas, please let me know, I'm about ready to either go back to Mailman 1.2 or start looking for another list manager.

2 2

Re: [Mailman-Users] Re: RC1 Seems to work but incoming mails are ignored
by Dan Mick Oct. 27, 2000

Oct. 27, 2000

> Andreas, play it cool, man. You're right, but I've seen discussions like > this a lot. Sometimes a poor soul is really just confused and missed > one particular sentence in an INSTALL or FAQ. Let's assume this is the > case. That's why there's a new paragraph at the very beginning of INSTALL. Really. Second paragraph. Go look.

1 0

2.0rc1 notes
by Steve Fox Oct. 27, 2000

Oct. 27, 2000

Just installed 2.0rc1 and had a couple small problems with it. 1. When a new list is created the mail which gets sent out to the list administration appears to be missing a slash in the URL after hostname/mailman as it says hostname/mailmanadmin/listname and hostname/mailmanlistinfo/listname 2. On the general options of the admin page the parameters which have "yes" and "no" for options do not have them consistently ordered. Most have "No" then "Yes" but I found one that doesn't (the "Send mail to poster when their posting is held for approval?" option). No biggie, just thought it might clean up the interface a little. Thanks much everyone! P.S. Please cc me as I'm not subscribed to the list. Thanks. -- Steve Fox IBM Linux Technology Center http://oss.software.ibm.com/developerworks/opensource/linux/ http://stevefx.rchland.ibm.com (IBM intranet) http://k-lug.com (Rochester Linux Users Group)

2 1

problems installing
by Rodrigo Moya Oct. 27, 2000

Oct. 27, 2000

Hi all! I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members. I've been checking my /etc/aliases file, among other things, and everything seems to be in its place, so I don't know where to look anymore. Any help, please!! thanks very much

4 6

Weird Setting.
by Stephen J Chula Oct. 27, 2000

Oct. 27, 2000

Ok, I have moved into a job where a mailman list-serv is in place. On of the lists got a setting slightly messed up. when a new user subscribes to the list, mailman send the confirmation notice, however the reply to address is incorrect. I has a reply address of abc-list instead of abc-list-request. Where is that set? i cannot find documentation on it, or a place to set it. Thanx -Steve chulas(a)msoe.edu

1 0

Bug in Archives ?
by Tobias Capangil Oct. 27, 2000

Oct. 27, 2000

Hi, I am using rc1 and whenever I someone posts something to a list, Mailman logs following error to "logs/error": #Traceback (most recent call last): File "./arch", line 129, in ? main() File "./arch", line 119, in main archiver.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 301, in close self.write_TOC() File "/home/mailman/Mailman/Archiver/HyperArch.py", line 910, in write_TOC toc.write(self.html_TOC()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 660, in html_TOC d["archive_listing"] = string.join(accum, '') UnboundLocalError: Local variable 'accum' referenced before assignment Same if I try to run bin/arch. The archive *.html file is empty. But the list is NOT broken, because I added few new lists and the error still occurs. Any idea ? Thanks in advance, Tobias

1 0

Reply-to in administrative messages.
by Cthulhu Oct. 27, 2000

Oct. 27, 2000

I've set the "reply-to" parameter to the address of the list. Yes, it is unsuggested, but I need to do that. Now, when people try to subscribe by email, even the automatic messages generated by MailMan have the Reply-To: set to the list name. It this expected behaviour or a littel bug or what? Another question: absolutely no way to enable subscriptions without any confirm from someone? listing, Cthulhu P.S.: *SPOT* we are using an OOOOLD version of MailMan to manage about 20 lists with up to 12.000 users. It works. -- Ph'nglui mglw'nafh Cthulhu http://www.rlyeh.it/ wgah'nagl fhtgan! <f.sileno(a)agora.it>

2 1

Re: [Mailman-Users] Perm Hosery in 2.0rc1?
by Dan Mick Oct. 27, 2000

Oct. 27, 2000

That looks like the Openwall Security Patch issue; hard links are restricted in some way I don't remember. Check the list archives; Marc Merlin has an installation procedure that works around the problem, and has posted about it several times. > I'm trying to set up 2.0rc1, and I can't seem to get it working. There > seems to be a problem with permissions. I've run check_perms and it > only bitches about the docs/ directory, which I created (for HTML docs). > I've found, however, that I get an error when I try to use the admin CGI, > and it leaves a lockfile in locks/ that causes any subsequent attempts > to hang. I've found I can make modifications through the admin CGI > if I change the owner of lists/<listname>/config.db* to nobody (the > user&group of Apache). > > However, if I do that, qrunner and the other cronned jobs fails with a > permission error. Changing the ownership to 'mailman' lets these run. > > I created the list as root; the install doc didn't say it needed to be > run as 'mailman'. Also, I just tested running 'newlist' as 'mailman', > and it still failed with a permission error. > > It /appears/ that the CGI needs to use mail/wrapper, but maybe Apache > does not let CGIs run Set[UG]ID programs? > > What it looks to me like > > Here's how I installed: > > $ ./configure --with-mail-gid=nobody --with-cgi-gid=nobody \ > --with-cgi-ext= && make > (As non-root, non-mailman user) > > # make install > > This is an Immunix 6.2 system, which is basically a Red Hat 6.2 system > rebuilt with the StackGuard compiler. I've replaced Sendmail with > Postfix. The above GIDs are correct for Postfix and Apache. > > Just so you don't think I'm crazy, here are some perms that seem to > be relevant: > > /home/mailman/lists/test] > # ls -l > total 22 > -rw-rw-r-- 1 mailman mailman 1706 Oct 26 17:14 admindbpreamble.html > -rw-rw---- 1 mailman mailman 2815 Oct 26 17:14 config.db > -rw-rw---- 1 nobody mailman 2815 Oct 26 17:16 config.db.tmp.mithra.wirex.com.19740 > -rw-rw-r-- 1 mailman mailman 189 Oct 26 17:14 handle_opts.html > -rw-rw-r-- 1 mailman mailman 900 Oct 26 17:14 headfoot.html > -rw-rw-r-- 1 mailman mailman 3136 Oct 26 17:14 listinfo.html > -rw-rw-r-- 1 mailman mailman 0 Oct 26 17:14 next-digest > -rw-rw-r-- 1 mailman mailman 0 Oct 26 17:14 next-digest-topics > -rw-rw-r-- 1 mailman mailman 4106 Oct 26 17:14 options.html > -rw-rw-r-- 1 mailman mailman 1169 Oct 26 17:14 roster.html > -rw-rw-r-- 1 mailman mailman 198 Oct 26 17:14 subscribe.html > > # ls -l mail > total 33 > -rwxr-sr-x 1 root mailman 32464 Oct 26 11:35 wrapper > > # ls -l locks > total 2 > -rw-rw-r-- 2 nobody mailman 52 Oct 26 2000 test.lock > -rw-rw-r-- 2 nobody mailman 52 Oct 26 2000 test.lock.mithra.wirex.com.20052 > > And here's the backtrace from the CGI error: > > Oct 26 17:53:43 2000 admin(20362): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > admin(20362): [----- Mailman Version: 2.0rc1 -----] > admin(20362): [----- Traceback ------] > admin(20362): Traceback (innermost last): > admin(20362): File "/home/mailman/scripts/driver", line 96, in run_main > admin(20362): main() > admin(20362): File "/home/mailman/Mailman/Cgi/admin.py", line 138, in main > admin(20362): mlist.Save() > admin(20362): File "/home/mailman/Mailman/MailList.py", line 842, in Save > admin(20362): self.__save(dict) > admin(20362): File "/home/mailman/Mailman/MailList.py", line 818, in __save > admin(20362): os.link(fname, fname_last) > admin(20362): OSError: [Errno 1] Operation not permitted > > (I'll assume you don't need the rest of it. I can send it if you do.) > > Wil > -- > W. Reilly Cooley, Esq. wcooley(a)wirex.com > > > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users(a)python.org > http://www.python.org/mailman/listinfo/mailman-users

3 2

RC1 Seems to work but incoming mails are ignored
by Andreas Gruener Oct. 27, 2000

Oct. 27, 2000

Hi, I installed today mailman for the first time. I started right away with version 2.0RC1. The web frontend works, I can subscribe, administer and so on. Mailman sends mails out as a result of all interaction with the web frontend. But as soon as I send a mail to my list, I do not get any reaction besides that two files are created in the directory qfiles. None of the subscribed users get any mail. Subscription via mail doesn't work either. My System: Linux 2.2.14 (SuSE) python-1.5.2 apache-1.3.6 sendmail-8.9.3 best regards, Andreas Please reply with cc to gruener(a)mercatis.de

5 6