Mailman 3 October 2004 - Mailman-Users

Compile problem: msgmerge: command not found
by Aaron Young Oct. 6, 2004

Oct. 6, 2004

Hey all, I'm running Solaris 2.8 and python 2.3.3 and my configure of mailman 2.1.5 goes swell, but when I attempt to compile, I get the following: gcc -I. -DMAIL_GROUP="\"mailman\"" -g -O2 -g -O2 -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 common.o vsnprintf.o -o mailman ./mail-wrapper.c make[1]: Leaving directory `/nn/local/src/mailman-2.1.5/src' make[1]: Entering directory `/nn/local/src/mailman-2.1.5/templates' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/nn/local/src/mailman-2.1.5/templates' make[1]: Entering directory `/nn/local/src/mailman-2.1.5/messages' Merging new template file with existing translations msgmerge -U ca/LC_MESSAGES/mailman.po mailman.pot make[1]: msgmerge: Command not found Seems like something is missing hasn't been made correctly along the way. Why msgmerge missing? Aaron ~

1 0

More help - please
by Layne Meier Oct. 6, 2004

Oct. 6, 2004

Okay - so I must be totally clueless here. I'm now able to create a list with my web interface. I followed the instructions to the letter. I created a list and subscribed to it, but I never got an e-mail to confirm my subscription to the list. I look at the pending.pck file and see my subscription, but I monitored Postfix (via /var/log/syslog) and the e-mail to my external account never even left the server. What am I doing wrong? System: Sun E250 Solaris 8 Postfix v2.1.5 Python v2.2.3 Mailman v2.1.5 Apache v2.0.47 ./configure options: --prefix=/usr/local/mailman --with-python=/usr/local/bin/python --with-username=mailman --with-groupname=mailman --with-mail-gid=mailman --with-cgi-cid=daemon --with-mailhost=mail.mydomain.tld --with-urlhost=www.mydomain.tld --with-gcc=yes Thank you, Layne Meier Atlanta Newspapers, Inc.

4 11

Cannot read wrapper configuration file error - please help!
by brandon dudley Oct. 6, 2004

Oct. 6, 2004

For some reason, my mailman installation stopped working on Sunday, giving the typical "got GID xx" message. Because I had installed mailman from rpm, I decided to reinstall it from the same rpm. When I did this, and fixed the alias file, any post to any of my lists gives the above error message. I did a search of the archives and saw this question appear from time to time, but there was never an answer given. OS: SUSE 9.1 (i386) version: mailman-2.1.4-83.3 (SUSE's numbering) run manually: mailman@misanthrope:/usr/lib/mailman/scripts> /usr/lib/mailman/mail/mailman post Cannot read wrapper configuration file. logged error msg: /var/log/mail.warn:Oct 5 12:59:01 misanthrope Mailman mail-wrapper: Cannot read wrapper configuration file. /var/log/mail.info:Oct 5 13:02:34 misanthrope postfix/local[18980]: 2954715045B: to=<xxx(a)xxx.com>, relay=local, delay=0, status=bounced (Command died with status 8: "/usr/lib/mailman/mail/mailman post xxx". Command output: Cannot read wrapper configuration file. ) thanks in advance, and fingers crossed! Brandon

3 2

Borked 2.1.3 to 2.1.5 upgrade
by jsmith Oct. 6, 2004

Oct. 6, 2004

Hello all, I have a fbsd box and I have been running mailman-2.1.3 sinces its release. No major problems but I have moved my box nd it was time to get a few of the new features and benefits that 2.1.5 offers. Environment is FREEBSD 5.1-RELEASE Apache 1.3.29 Python 2.3.2 Sendmail is my MTA Again, all was working well. Of course I tared up the whole mailman director before I started the upgrade. After my upgrade attempt failed I put my 2.1.3 install back. But upon starting mailman I found I had the same problem as I did with 2.1.5 Obviously this upgrade has changed something and I was hoping for a little help to find it. Once I start Sendmail, Apache, and then Mailman. I can check and all my process' are starting. I see nothing in the maillog, error, or messages log file that would indicate my problem. Do I need to perform something to re-initialize my current lists? Once everything has started I point my browser to my list manager webpage and I receive the following. I did find one other post int eh archives with this exact error. He stated that he ran ./check_perms -f to fix his problem. Unfortunately my ./check_perms -f comes back with no errors. Maybe this is something that its just to late at night for me to see. Any and all help will be greatly appreciated. Joe _______________________________________________________________________ Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/local/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/local/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/local/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/local/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/usr/local/mailman/logs/error' ------------------------------------------------------------------------ -------- Python information: Variable Value sys.version 2.3.2 (#1, Dec 24 2003, 09:32:09) [GCC 3.2.2 [FreeBSD] 20030205 (release)] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd5 ------------------------------------------------------------------------ -------- Environment variables: Variable Value HTTP_COOKIE jobposting+admin=280200000069ae26604173280000006262656438653430333133623 4396339323934623331343635646337373463666662623832313733 SERVER_SOFTWARE Apache/1.3.29 (Unix) PHP/4.3.1 SCRIPT_NAME /mailman/listinfo SERVER_SIGNATURE Apache/1.3.29 Server at www.mysite.here <this had my correct domain Port 80 REQUEST_METHOD GET SERVER_PROTOCOL HTTP/1.0 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; MyIE2; SV1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME www.mysite.here <this had my correct domain REMOTE_ADDR Correct.ip.was.here SERVER_PORT 80 SERVER_ADDR Correct.ip.was.here DOCUMENT_ROOT /usr/home/meawest PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/listinfo SERVER_ADMIN very(a)innocent.com HTTP_HOST www.mysite.here <this had my correct domain REQUEST_URI /mailman/listinfo HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 64865 HTTP_ACCEPT_LANGUAGE en-us UNIQUE_ID QWOV@NF@m7wAAT-pDyE

1 0

Re: [Mailman-Users] Probe Message Problem
by Mark Sapiro Oct. 5, 2004

Oct. 5, 2004

Gary Kaplan wrote (accidently?) off list: >I have no idea what Marks response means. Can someone please help? > >-Gary > >Mark Sapiro wrote: > >> Gary Kaplan wrote: >> >>> One of my users informed me that she got this message in which a couple >>> hundred address from the list were disclosed. I want to know if there >>> is a >>> way to stop this. I don't want everyone who gets a probe message to see >>> everyone's email address. I have noted where the address are listed >>> but left >>> the actual addresses off. >>> >>> >>>> This is a probe message. You can ignore this message. >>>> >> <snip> >> >>>> >>>> Received: from mailnull by washington.hostforweb.net with local >>>> (Exim 4.41) >>>> id 1C9XAp-000348-CZ >>>> for Upcnews-bounces(a)upc-online.org; Mon, 20 Sep 2004 19:02:19 -0400 >>>> X-Failed-Recipients: >>> >>> >>> At this point it lists a couple hundred email addresses >>> >>> Then is says this: >>> >>>> Auto-Submitted: auto-generated >>>> From: Mail Delivery System <Mailer-Daemon(a)washington.hostforweb.net> >>>> To: Upcnews-bounces(a)upc-online.org >>>> Subject: Mail delivery failed: returning message to sender >>>> Message-Id: <E1C9XAp-000348-CZ(a)washington.hostforweb.net> >>>> Date: Mon, 20 Sep 2004 19:02:19 -0400 >>>> >>>> This message was created automatically by mail delivery software. >>>> >>>> A message that you sent could not be delivered to one or more of its >>>> recipients. This is a permanent error. The following address(es) >>>> failed: >>> >>> >>> and list the addresses again. >> >> >> It appears that Mailman is appending the bounce message to the probe >> and in this case there were "a couple hundred" subscribers in the >> washington.hostforweb.net domain that bounced. >> >> In any case, this seems to be sufficient reason to not append the >> original bounce mesage to the probe. >> >> I'm far from fluent in Python, but it looks like either >> >> self.sendProbe(member, msg) >> in the routine >> def registerBounce(self, member, msg, weight=1.0, day=None): >> in Bouncer.py >> >> or >> outer.attach(MIMEMessage(msg)) >> in >> def sendProbe(self, member, msg): >> in Deliverer.py >> >> are places where this can be addressed. >> OK, let me try again. >From the Mailman-2.1.5/NEWS file: - The bounce processor has been redesigned so that now when an address's bounce score reaches the threshold, that address will be sent a probe message. Only if the probe bounces will the address be disabled. The score is reset to zero when the probe is sent. Also, bounce events are now kept in an event file instead of in memory. This should help contain the bloat of the BounceRunner. What appears to have happened in your case is that you have "a couple hundred" subscribers in the washington.hostforweb.net domain that all bounced to the point of reaching the threshold causing a probe message to be sent to each of the bouncing addresses. In at least one case and maybe in all, the bouncing address was actually valid because the probe reached the subscriber. The problem here is that the bounce message that caused the score to reach the threshold was appended to the probe, and it contained a list of all the bouncing addresses in the domain. I don't think it is necessary for Mailman to append the bounce message to the probe message, and I think your experience is good reason not to. Unfortunately, there appears to be no way in 2.1.5 to fix this short of hacking the python code and I suggested a couple of places where one could start looking if one wanted to do this. As far as how often this might happen on your list is concerned, if all or almost all the addresses are actually valid and do not normally bounce, there was apparently some MTA transient situation that caused these addresses to all be bouncing at once. If this is a situation that might occur again, you might consider tuning your bounce processing parameters to minimize the likelihood of valid addresses reaching threshold. If, OTOH, almost all the addresses were in fact bad, they are now gone and won't be "revealed" again. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Content negotiation for language
by Evan Prodromou Oct. 5, 2004

Oct. 5, 2004

So, as far as I can tell, the Web interface for Mailman is completely ignorant of content negotiation (http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html). It doesn't seem to do any variation on the Accept-Language header sent by the browser. Am I incorrect? Is there some way to get Mailman to show the page in French if the user's browser preference is French, and German if the user's browser preference is German? Or does the user always have to see the default language version before changing over to their preferred language? ~ESP

2 1

Authorized Users
by Robert Haack Oct. 5, 2004

Oct. 5, 2004

I'm new to this list and to using Mailman. Please forgive me if this question has been asked before but I could not find it in my search through the archives. On our old list serv software we had the ability to create a group of authorized users who could post to any of 15 lists without being subscribed to that list. Is there any way to do the same sort of thing with Mailman? I tried to create a list called Auth_users and then put this list in the "List of non-member addresses whose postings should be automatically accepted" but that did not work. Any ideas would be greatly appreciated, I'd prefer not to have to go into each list and make changes every time. Thank You -- R Haack Programmer Analyst North Clackamas School District #12 haack(a)nclack.k12.or.us

2 1

Re: [Mailman-Users] Cannot read wrapper configuration file error - please help!
by brandon dudley Oct. 5, 2004

Oct. 5, 2004

That said, what typically does the error message "Cannot read wrapper configuration file" refer to? What is the wrapper configuration file? mm_cfg.py? I actually downloaded another rpm and used that, and got the same message. I removed the mailman rpm and reinstalled it - no dice. On Tue, 5 Oct 2004 22:56:16 +0200, Brad Knowles <brad(a)stop.mail-abuse.org> wrote: > At 1:21 PM -0700 2004-10-05, brandon dudley wrote: > > > For some reason, my mailman installation stopped working on Sunday, > > giving the typical "got GID xx" message. Because I had installed > > mailman from rpm, I decided to reinstall it from the same rpm. When I > > did this, and fixed the alias file, any post to any of my lists gives > > the above error message. I did a search of the archives and saw this > > question appear from time to time, but there was never an answer > > given. > > I think the important thing to figure out is what changed on > Sunday. Whatever that was, it may not be possible to fix this > problem by re-installing from the same RPM -- you may have to get a > new one. > > However, since you're talking about using the RPM version and > something mysteriously changed on Sunday, I think you're more likely > to be able to find answers to your questions on mailing lists and > newsgroups that are specific to your OS. > > I don't think there are any Mailman-specific problems here that > we can help you with. > > -- > Brad Knowles, <brad(a)stop.mail-abuse.org> > > "Those who would give up essential Liberty, to purchase a little > temporary Safety, deserve neither Liberty nor Safety." > > -- Benjamin Franklin (1706-1790), reply of the Pennsylvania > Assembly to the Governor, November 11, 1755 > > SAGE member since 1995. See <http://www.sage.org/> for more info. >

1 0

Content negotiation for language
by Evan Prodromou Oct. 5, 2004

Oct. 5, 2004

So, as far as I can tell, the Web interface for Mailman is completely ignorant of content negotiation (http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html). It doesn't seem to do any variation on the Accept-Language header sent by the browser. Am I incorrect? Is there some way to get Mailman to show the page in French if the user's browser preference is French, and German if the user's browser preference is German? Or does the user always have to see the default language version before changing over to their preferred language? ~ESP

1 0

Re: [Mailman-Users] More help - please
by K. Clair Oct. 5, 2004

Oct. 5, 2004

Are you certain that it started without any errors? I have been able to run the web interface without any problems on servers with python versions other than 2.3, but the qrunner doesn't work for me unless python 2.3.3 is installed. Kristina On Tue, Oct 05, 2004 at 03:46:32PM -0400, Layne Meier wrote: - Yes, I am running qrunner. - - Layne - - - On Oct 5, 2004, at 3:20 PM, K. Clair wrote: - - >This might seem like a silly question, but did you start up the - >qrunner? - > - >Kristina - > - >On Tue, Oct 05, 2004 at 03:26:02PM -0400, Layne Meier wrote: - >- Okay - so I must be totally clueless here. I'm now able to create a - >- list with my web interface. I followed the instructions to the - >letter. - >- I created a list and subscribed to it, but I never got an e-mail to - >- confirm my subscription to the list. I look at the pending.pck file - >- and see my subscription, but I monitored Postfix (via - >/var/log/syslog) - >- and the e-mail to my external account never even left the server. - >- - >- What am I doing wrong? - >- - >- System: - >- Sun E250 - >- Solaris 8 - >- Postfix v2.1.5 - >- Python v2.2.3 - >- Mailman v2.1.5 - >- Apache v2.0.47 - >- - >- ./configure options: - >- --prefix=/usr/local/mailman --with-python=/usr/local/bin/python - >- --with-username=mailman --with-groupname=mailman - >- --with-mail-gid=mailman --with-cgi-cid=daemon - >- --with-mailhost=mail.mydomain.tld --with-urlhost=www.mydomain.tld - >- --with-gcc=yes - >- - >- - >- Thank you, - >- Layne Meier - >- Atlanta Newspapers, Inc. - >- - >- ------------------------------------------------------ - >- Mailman-Users mailing list - >- Mailman-Users(a)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/

2 1