Mailman 3 February 2000 - Mailman-Users

problems with install
by Jeremy Weathers 26 Feb '00

26 Feb '00

<alert name="neophyte" value="complete idiot"> Disclaimer: I am not a real unix admin, I don't even play one on TV - I'm simply the web developer who was conned into "maintaining" the company's MacOS X Server box. I have a _little_ Linux experience, and now some BSD "experiences" as well. I am having trouble with the installation and am hoping that either a) someone else on this list has installed Mailman under MacOS X, or b) some kind soul will guide me in the right direction. History I installed Python, untarred mailman source, created the mailman user and group, and ran configure with the desired options*. On the first run of make**, I got an error that PREFIX was not defined in src/common.c. I overwrote the PREFIX define in src/common.c with mailman's home directory and continued. Problem When I run make again, I get an error in src/cgi-wrapper.c. At this point, I'm guessing that configure did not pass in the variables to the source scripts as was planned. Here my ingenuity has failed me. The error reported by make cc -c -I. -DPREFIX="\"/Local/Users/mailman\"" -DPYTHON="\"/usr/local/bin/python\"" -DHELPFUL -g -O2 -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 ./common.c cc -c -I. -DPREFIX="\"/Local/Users/mailman\"" -DPYTHON="\"/usr/local/bin/python\"" -DHELPFUL -g -O2 -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 ./vsnprintf.c cc -DSCRIPT="\"admin\"" -I. -DCGI_GID=70 -g -O2 -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 common.o vsnprintf.o -o admin ./cgi-wrapper.c ./cgi-wrapper.c:31: `Mailman' undeclared here (not in a function) ./cgi-wrapper.c:31: parse error before `cgi' Lines 29-31 of src/cgi-wrapper.c /* passed in by configure */ #define SCRIPTNAME SCRIPT #define LOG_IDENT "Mailman cgi-wrapper (" ## SCRIPT ## ")" TIA, Jeremy Weathers * So far I think I only need to set $PREFIX - I think the rest is standard, if not I'm sure I'll find out after a successful installation (one without make errors). I used "./configure --prefix=/Local/Users/mailman". ** "make DIRSETGID=: install" as stated in README.BSD since this is a BSD variant. I did set the g+s bit on the $PREFIX directory because configure would complain otherwise.

1 0

news <-> list weirdness
by A Iqbal Santyaswardan 26 Feb '00

26 Feb '00

Hi all, remember my news <-> list phenomena? Well if you don't, here's the case again: It used to be that listA is connected to newsgrpA properly (that is, a person can post to the newsgroup and the list members will also receive, and vice versa). Then something happened, I don't know what, that made that connection vanish. Not even show in the error logs. It's as if the gate has been closed. Well then I tried to make listB connect to newsgrpB, and that seems to work fine. (same news and list server, by the way, actually they're the same box... just different newsgroup and list) Then I tried to have listA connect to newsgrpC, and it seems that posts to listA goes into newsgrpC, but posts to newsgrpC won't go into listA. Still no error in the logs. Then I moved listA back to newsgrpA, and now I get this message: ---------- Forwarded message ---------- Date: Sat, 26 Feb 2000 15:25:01 +0700 From: Cron Daemon <root(a)server.te.ugm.ac.id> To: mailman(a)server.te.ugm.ac.id Subject: Cron <mailman@server> /usr/bin/python /home/mailman/cron/gate_news Exception Mailman.LockFile.NotLockedError: <Mailman.LockFile.NotLockedError instance at 81867e0> in <method LockFile.__del__ of LockFile instance at 81abb10> ignored And posts to listA can be read in newsgrpA, but posts in newsgrpA won't show in listA. So, the fault lies in listA ? I am completely befuddled by this, especially since I know almost nothing of python. The easy answer is probably to start another list to connect to newsgrpA, and move all the members to there. But what's to guarantee that this wont happen again? Hmmm.... what other info should I send to further investigate this matter? Iqbal Santyaswardan

1 0

Re: [Mailman-Users] Adding bounce filters
by J C Lawrence 25 Feb '00

25 Feb '00

On Fri, 25 Feb 2000 10:55:30 -0500 Scott Russell <scottrus(a)raleigh.ibm.com> wrote: > I seem to be lost. I need to add a filter within Mailman so that > posts with the phrase 'out of the office' in the subject get > bounced. Simple. Have your list posts run thru a procmail filter before being sent to Mailman. Then just have the procmail filter pick up those messages and bounce them while passing everything else thru to Mailman. <<See Barry? No camelcasing! (tho I had to go back and manually correct every one)>> -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

answer_majordomo script
by Scott Russell 25 Feb '00

25 Feb '00

Has anyone set up the answer_majordomo script that's in the mailman/scripts dir? I've got a system with postfix + Mailman that I just migrated from majordomo and some users still haven't quite got this down yet. :) If anyone can share there answer_majordomo script config with me I would appreciate it. Thanks for the help! -- Regards, Scott Russell (scottrus(a)raleigh.ibm.com) Linux Technology Center, System Admin Red Hat Certified Engineer

1 0

accents in subjects
by Fil 25 Feb '00

25 Feb '00

Hi mailman-users what happens when accents are in subjects ? Usually it get morphed from Réf. : confirmation of subscription - request 170967 into something like =?iso-8859-1?Q?R=E9f._:_confirmation_of_subscription_--_request_170967?= This 1) prevents confirmation from working when the client mailer is stupid enough to use "Réf. :" instead of "Re:" ; 2) makes the digests ugly and unreadable because accntuated Subjects are printed in their =iso...= format. So I guess mailman should, before doing anything, convert these back to ascii. Any idea?

3 4

Re: [Mailman-Users] accents in subjects
by Nigel Metheringham 25 Feb '00

25 Feb '00

fil(a)bok.net said: > However it's not only a question of 'Réf.' but of any > accentuated Subject: when it comes to the digest issue. So mailman is > also a little faulty here. Not really. You cannot have 8 bit characters in header lines - the character set etc applies to the body, so that subject is broken to start with. [from previous message] > Usually it get morphed from > Réf. : confirmation of subscription - request 170967 > into something like > =?iso-8859-1?Q?R=E9f._:_confirmation_of_subscription_--_request_170967?= so some MTA is converting the broken subject into some form of MIMEish encapsulation - basically coping with a broken message by applying a semi-broken workaround. > So I guess mailman should, before doing anything, convert these back > to ascii. not sure you want mailman to start doing conversions around other people's breakage. One possibility might be to make the subject line have more of a key in it hopefully picked to not have char set implications - say that kast part be [[CONFIRM#170967]] and just look for that style tag ignoring everything else in the line - making sure that the tags chosen don't get hit by those 8 bit conversion problems. Nigel. -- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]

2 1

Adding bounce filters
by Scott Russell 25 Feb '00

25 Feb '00

I seem to be lost. I need to add a filter within Mailman so that posts with the phrase 'out of the office' in the subject get bounced. I did add "Subject: .*out of the office*." to the bounce_matching_headers on the privacy page however that means I get admin mail each time. I simply want these to be bounced and no further action to be taken. No email back to the sender should happen either. Thanks for the help. -- Regards, Scott Russell (scottrus(a)raleigh.ibm.com) Linux Technology Center, System Admin Red Hat Certified Engineer

1 0

'General posting filters' explanation required
by Mark Martinec 25 Feb '00

25 Feb '00

Under 'Privacy Options' in the section 'General posting filters' there are three settings: 1. Must posts be approved by an administrator? 2. Restrict posting privilege to list members? (member_posting_only) 3. Addresses of members accepted for posting to this list without implicit approval requirement. I must confess I find the interaction between the three settings unintuitive. I have to read '(details)' every time I set up a new list and when explaining it to a new list moderator. After all my re-readings I understand the interaction between 2 and 3, but please somebody explain the interaction between 1 and the other two. (and add '(details)' entry to the first item as well). Regards Mark -- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! Mark Martinec (system manager) tel +386 61 177-3575 !! !! J. Stefan Institute, Jamova 39 fax +386 61 219-385 !! !! SI-1000 Ljubljana, Slovenia mark.martinec(a)ijs.si !! !!!!!!!!!!!!!!!!!!!!!!!!!! http://www.ijs.si/people/mark/ !!!!

2 1

Postfix and Mailman
by Ralf Hildebrandt 25 Feb '00

25 Feb '00

While I got most parts of Mailman to work with Postfix, I'm having trouble with this: <quiz-request(a)www.stahl.bau.tu-bs.de>: service unavailable. Command output: /usr/sbin/smrsh: wrapper not available for sendmail programs local delivery is done by procmail, /usr/sbin/smrsh hasn't been used ever since I changed to Postfix. Any ideas? -- Ralf Hildebrandt <R.Hildebrandt(a)tu-bs.de> www.stahl.bau.tu-bs.de/~hildeb We can't prove that God exists. However, we can prove that if God does exist, he's pretty good at math. In fact, we can prove that even if God doesn't exist, he's still pretty good at math.

1 2

File Permissions
by Frank Martini 24 Feb '00

24 Feb '00

Hello all. Just moved my mailman files to my brand new 20Gb Hard Drive. Now I'm getting permission errors. Is there anywhere where all default permissions are documented? I can't seem to untangle the mess I've made. Everything was working fine for months until I moved the files... Thanks Error below: Traceback (innermost last): File "/home/mailman/scripts/driver", line 85, in run_main logger = StampedLogger('error', File "/home/mailman/Mailman/Logging/StampedLogger.py", line 48, in __init__ Logger.__init__(self, category, nofail, immediate) File "/home/mailman/Mailman/Logging/Logger.py", line 40, in __init__ self.__get_f() File "/home/mailman/Mailman/Logging/Logger.py", line 63, in __get_f reraise() File "/home/mailman/Mailman/Logging/Logger.py", line 55, in __get_f f = self.__fp = open(self.__filename, 'a+') IOError: (13, 'Permission denied') -- Frank Martini Voice: 713/621-1917 Cadence Development FAX: 713/621-1960 5075 Westheimer, Ste. 1266 eMail: fmartini(a)caddev.com Houston, Texas 77056 WWW: http://www.CadenceDevelopment.com/

2 1