Mailman-Users August 1998

mailman-users@python.org

15 participants
13 discussions

by GoBig

Hi, I've just recently setup the mailman list server software and had a question I couldn't find the answer to. The question is: Is there any way to substitute this welcome announcement with one I modify?? I'd like to send a welcome msg to new users but the one listed below is far too detailed. I saw in the list configuration options, the ability to prepend a message to the "default" one but I'd like to do away with the "default" text below. Is this possible? Thanks, John Jones Numbskull Interactive www.numbskull.com > > > -----Original Message----- > > From: hognews-admin(a)eastsideharley.com > > [SMTP:hognews-admin@eastsideharley.com] > > Sent: Tuesday, August 25, 1998 1:35 PM > > To: John Jones > > Subject: Welcome To "Hognews"! > > > > Welcome to the Hognews(a)eastsideharley.com mailing list! > > > > To post to this list, send your email to: > > > > hognews(a)eastsideharley.com > > > > General information about the mailing list is at: > > > > http://mailman.eastsideharley.com/mailman/listinfo/hognews > > > > If you ever want to unsubscribe or change your options (eg, switch to > > or from digest mode, change your password, etc.), visit your > > subscription page at: > > > > > > > http://mailman.eastsideharley.com/mailman/options/hognews/johnjon@microsof > > t.com > > > > > > You can also make such adjustments via email by sending a message to: > > > > Hognews-request(a)eastsideharley.com > > > > with the word `help' in the subject or body, and you will get back a > > message with instructions. > > > > You must know your password to change your options (including changing > > the password, itself) or to unsubscribe. It is: > > > > eTqu > > > > If you forget your password, don't worry, you will receive a monthly > > reminder telling you what all your eastsideharley.com mailing list > > passwords are, and how to unsubscribe or change your options. There > > is also a button on your options page that will email your current > > password to you. > > > > You may also have your password mailed to you automatically off of the > > web page noted above. > > > > >

22 years, 11 months

misc problems and a bug report...

by Jerry Adlersfluegel

I have set up 1.0b5 on linux 2.0.32 with sendmail 8.8.7. The list is working ok, after I turned down the number of connections to just one. Before that, multiple messages were going out all the time. I'm not sure if that problem is resolved yet; but that isn't why I am writing. On the list info page, at the bottom where you enter your address and hit "Edit Options," I receive the following in the error log (in addition to the web page error that's returned): Aug 20 23:35:21 1998 admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/home/mailman/scripts/driver", line 97, in run_main admin: main() admin: File "../Mailman/Cgi/subscribe.py", line 95, in main admin: call_script('options', [list._internal_name, member]) admin: File "../Mailman/Cgi/subscribe.py", line 65, in call_script admin: list.Unlock() admin: AttributeError: Unlock admin: [----- Environment Variables -----] admin: DOCUMENT_ROOT: /home/httpd/html admin: REMOTE_HOST: 209.144.61.49 admin: CONTENT_TYPE: application/x-www-form-urlencoded admin: PATH_TRANSLATED: /home/httpd/html/rtctable/ admin: REMOTE_ADDR: 209.144.61.49 admin: HTTP_VIA: 1.0 jerrya:3128 (Squid/1.NOVM.16) admin: HTTP_ACCEPT_LANGUAGE: en-US admin: HTTP_X_FORWARDED_FOR: 127.0.0.1 admin: GATEWAY_INTERFACE: CGI/1.1 admin: SERVER_NAME: jerrya.fastrans.net admin: HTTP_USER_AGENT: Mozilla/4.05 [en] (X11; I; Linux 2.0.32 i486) admin: HTTP_ACCEPT_CHARSET: iso-8859-1,*,utf-8 admin: HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* admin: REQUEST_URI: /mailman/subscribe/rtctable/ admin: HTTP_CACHE_CONTROL: Max-age=259200 admin: PATH: /sbin:/usr/sbin:/bin:/usr/bin admin: QUERY_STRING: admin: SCRIPT_FILENAME: /home/mailman/cgi-bin/subscribe admin: SERVER_PORT: 80 admin: CONTENT_LENGTH: 26 admin: HTTP_HOST: jerrya.fastrans.net admin: REQUEST_METHOD: POST admin: SCRIPT_NAME: /mailman/subscribe admin: SERVER_ADMIN: root@localhost admin: SERVER_SOFTWARE: Apache/1.2.4 PHP/FI-2.0 admin: PYTHONPATH: /home/mailman admin: PATH_INFO: rtctable/jerrya(a)fastrans.net admin: HTTP_REFERER: http://jerrya.fastrans.net/mailman/listinfo/rtctable admin: SERVER_PROTOCOL: HTTP/1.0 admin: REMOTE_PORT: 9300 --------------------- That's the end of the report. I think that's the only thing that's failing at this time. Does this mean anything? Thanks! -- Jerry Adlersfluegel http://quake.fastrans.net/~jerrya/

22 years, 11 months

Localization

by Tomas Fasth

Hi, I'm new to this list. IMHO, Mailman is a jolly good piece of software. Have anyone tried to localize Mailman (translate to another language)? A quick look gave me a hint that it isn't that straight forward. It seem to exist quite a number of texts intended for user presentation inside scripts. Oh, maybe some are for the administrator presentation. Anyway, I wish to translate the whole thing. Like to share experiences on this topic, anyone? I intend to join the developer's list as well to discuss what can be done to make it easier in coming releases. Thanks, Tomas

22 years, 11 months

mailman problem (?)

by bob＠staff.cs.usyd.edu.au

I've installed mailman and followed the instructions to set up a list called test. I go to the management page for the list and I'm asked for"test Administrative Authentication". I enter the correct password (as verified in the initial mail) but the page that comes up is the general admin page (/mailman/admin). Is this correct? I was expecting a page to allow me to manage the list. Bob.

22 years, 11 months

mailman, pipermail

by David.Sparrman＠kristnet.org

I need to get a listserver up and running in one week, and am currently checking out mailman. My current problem is that I am not familiar at all with mailing list software. (etc etc, standard newbie warning) The installation procedure for mailman is fairly well documented including shell commands except for one stage: "point an external archiver at the public and private archives" [pipermail]. I can't find anything in the pipermail package that give me any hints about how this should be done, and dejanews have no further hints. mailman 1.0b5 is installed in /home/mailman pipermail 0.05 is installed in /usr/local/pipermail if I run; python pipermail.py - nothing happens python hypermail.py - it complains with a message saying it can't open MBOX. mkdir mbox ; python hypermail.py -m /usr/local/pipermail/mbox I seem to accomplish something. Not sure off what, though. What else should be done? (looking sheepishly) Thanks

22 years, 11 months

Hi and, well, er, Help!

by Mark

Hi there. First, I must say that I am a Social Sciences major who has a work study job in the computer dept at my college, so please excuse that I am not that bright with computers and thus this silly question. We are transferring the administration of our all-campus mailing list to the Director of Propaganda..er Public Information and mailman looked like real sexy way for him to be able to administer and, well, I didn't want to setup majordomo again cause I was in hospital for weeks after an attempt on my own life due to sheer frustration. Anyway, here is the lowdown: the system is a Pent 200 running Debian 2.0 smail 3.2.0.101-4.5 apache 1.3.0-2 python 1.5.1-4 The compile seemed to go well, the web pages it made worked ok and looked real nifty. I did manage to generate the error: Mailman mail-wrapper: Failure to exec script. WANTED gid 8, GOT gid 1002. (Reconfigure to take 1002?) But I fixed that with a recompile. When the test list was created, it sent me a message just as it should have. An attempt to subscribe via the web page sent a message just as it should have. But.... both an attempt to send for the "help" message and to reply to the subscribe message produced this message to mail-daemon: "/home/mailman/mail/wrapper mailcmd test" ... failed: transport file: failed to open output file: Permission denied and the smail logs produce this... 08/06/1998 21:42:36: [m0z4bYC-000XZdC] Delivered TO: ORIG-TO:<test-request(a)robin.warren-wilson.edu> DIRECTOR:aliases TRANSPORT:pipe 08/06/1998 21:42:36: [m0z4bYC-000XZhC] Received FROM:<+> HOST:robin.warren-wilson.edu PROTOCOL:bsmtp PROGRAM:smail SIZE:1384 08/06/1998 21:42:36: [m0z4bYC-000XZhC] Delivered VIA:owl.warren-wilson.edu TO:mark@warren-wilson.edu ORIG-TO:<postmaster> ROUTER:inet_hosts TRANSPORT:smtp 08/06/1998 21:42:36: [m0z4bYC-000XZhC] Completed. 08/06/1998 21:42:38: [m0z4bYC-000XZdC] Error sent FOR:"/home/mailman/mail/wrapper mailcmd test" TO:postmaster 08/06/1998 21:42:38: [m0z4bYC-000XZdC] Completed. Stuff seems to have the right permissions, I tried every combo, changing the group to mail, putting both mail and mailman in each others groups and then finally putting hte whole /home/mailman into super slut mode 777. Still no go... Any suggestions out there? (and remember, I am a social sciences major, so use small words). mark

22 years, 11 months

low level failure

by Ken MacCuish

FWIW I am having the same problem that Luke mentioned in an earlier posting. That is when trying to submit anyting via the web interface I receive the following: 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback. Please report this to the Mailman administrator at this site. I have grabbed the driver script that was posted and am trying it out now. -ken

22 years, 11 months

Odd b5 behavior

by Corbett J. Klempay

I've been having this problem for a few days, and I am just trying to find out if anyone else here is experiencing a similar phenomenon (so that maybe I'll get lucky and talk to you and figure out what the story is): - 1.0b5 + sendmail 8.9.1 - RH Linux 5.1 (if you need more info, it's also http://www2.acm.jhu.edu -- there's lots of stuff there) There was some weirdness with permissions being set wrong with Linux + b5, but Barry issued a patch in about 2 seconds flat that cleared that one up. The current problem is that I have several lists set up, but if you send mail to them (like test(a)acm.jhu.edu), your mail is swallowed into a bottomless pit...it never sees the light of day again. If you look at /var/log/maillog, it claims the mail has been sent. Users have that they did get their monthly password reminder from Mailman itself, however. I don't think this is really something misconfigured with sendmail on my end; this same setup was chugging right along with 1.0b4 until I tried to switch. ------------------------------------------------------------------------------- Corbett J. Klempay Quote of the Week: http://www2.acm.jhu.edu/~cklempay "Money is the root of all good." PGP Fingerprint: 7DA2 DB6E 7F5E 8973 A8E7 347B 2429 7728 76C2 BEA1 -------------------------------------------------------------------------------

22 years, 11 months

Re: [Mailman-Users] Re: [Mailman-Developers] Odd b5 behavior

by Janne Sinkkonen

"Corbett J. Klempay" <cklempay(a)acm.jhu.edu> writes: > How do I check? Is this what I see when I do mailq? If that's it, it's > empty. Ok. > > When I had a broken sendmail, most of the messages still went through. > > I don't know that my sendmail is really broken..it works with b4, and all > of our non-mailman mail is running smoothly. At least the MIME bug is not your problem, since it doesn't exist in 8.9.1. (BTW, practically all of our non-mailman mail ran smoothly as well, so that's not an indicator of anything.) To see whether the mail really goes to the MTA, change the logging level of sendmail high enough (if it isn't). That's just the 'O' thing in sendmail.cf - it is easy to edit manually. -- Janne

22 years, 11 months

Re: [Mailman-Developers] Odd b5 behavior

by Janne Sinkkonen

Ken Manheimer <klm(a)cnri.reston.va.us> writes: > There is a known bug in some recent versions of sendmail (8.8.x for some > x, and 8.9.0) such that the sendmail will core dump when attempting to > deliver mailman's (or any 8-bit encoded) Mime-format digests in certain > (somewhat uncommon) circumstances. The question then is, were the > messages that never appeared in the users mailbox Mime digests? And if > not, could you construct a repeatable test that at least reduces the > likelihood that the problem is on the receiving ends? For that matter, > might you happen to be running sendmail 8.8.x or 8.9.0? Your sendmail > may be getting so far as negotiating the delivery and then failing > partway through... He should check his mail spool. If sendmail dies, it leaves the undelivered message to the spool, which then starts to gradually grow. When I had a broken sendmail, most of the messages still went through. -- Janne

22 years, 11 months