Mailman 3 August 2002 - Mailman-Developers

[ mailman-Bugs-228680 ] Infinite loops with Auto-Reply
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #228680, was opened at 2001-01-13 13:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=228680&group_i… Category: mail delivery >Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Infinite loops with Auto-Reply Initial Comment: An infinite mail loop is created when a - member of a mailing list has an Out Of The Office or other Auto-Reply set up and - there is a misconfiguration of SMTP on the member's end (is what I'm told) and - the mailing list is moderated with a "pending moderator approval" message sent to the sender of a message Use case: person comes back from vacation and finds 3500 messages from Mailman saying "Your message is waiting for moderator approval", which were in response to her "I'm away on vacation" Auto-Reply ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:35 Message: Logged In: YES user_id=12800 I believe this problem is resolved in the latest MM2.1 betas through the use of various techniques, including not autoresponding to messages that have a Precedence: {junk,list,bulk} header, and a built-in governor for the number of autoreplies to any one address in a single day. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=228680&group_i…

1 0

[ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #229568, was opened at 2001-01-20 22:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_i… Category: Pipermail >Group: 2.1 beta Status: Open Resolution: Works For Me Priority: 5 Submitted By: Aharon Varady (aharon) Assigned to: Nobody/Anonymous (nobody) Summary: Pipermail won't resolve author names of aol.com addresses Initial Comment: Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve. For example: "John" <user(a)aol.com> is resolved by pipermail as: listname(a)foo.com and not as John. This bug only occurs for users of aol.com addresses. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-02 16:00 Message: Logged In: YES user_id=110886 Whoops. Diffed the wrong thing. That's what happens when I try to patch code but haven't slept in a few days. This actually works better: 180c180 < if e is not None: --- > if e is not None and self.email == "": ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-01 14:03 Message: Logged In: YES user_id=110886 The problem is that it defaults to using the reply-to address if it's set, and this isn't what we want when the reply-to is always being set by the list. Take a careful look at the rest of your archives and you'll probably note that *everyone's* email address is showing up as listname(a)foo.com. It's a nice anti-spam feature, perhaps, but probably not what you want. Here's a quick fix for pipermail.py: 180c180 < if e is not None: --- > if e is not None and self.email is None: This just changes it so that it defaults to the From: address (when it's set) rather than the Reply-to address. If there's some particular reason to take the Reply-To over the From, I can make something which actually checks to see if the reply-to is being set by the list, but this should solve your problem for the moment. Terri ---------------------------------------------------------------------- Comment By: Ava Jarvis (katanalynx) Date: 2002-06-10 22:14 Message: Logged In: YES user_id=561110 This bug -- for version 2.0.11 at least -- seems to occur when 'from' only contains the email address. There's some code in pipermail.py (version 2.0.11), line 177: <excerpt> # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') e = message.getheader('Reply-To') if e is not None: self.email = e self.email = strip_separators(self.email) self.author = strip_separators(self.author) if self.author == "": self.author = self.email </excerpt> If reply-to is set, then it is always taken as the author's email address. However, some lists set the reply-to field to be, for instance, the list address.... and you can guess what happens next when there is no name comment/author. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-06-06 12:09 Message: Logged In: NO This comment doesn't directly address the case you report, but it might be related so I thought it worthwhile to submit. I see you are using MM2.0.9. I saw a similar problem with MM2.1b1, which was fixed in MM2.1b2. The problem then was that an address with a name "comment" would be displayed in the archive as the list name, whereas an address with a name comment would be displayed (properly) with the name. Example: "John Doe" jdoe(a)whereever.com displayed as "John Doe" whereas jdoe(a)whereever.com displayed as the list name. In your comment, you use an example with a name comment of "John", but in the example you provided there is no name comment field, so perhaps my statements here do apply. ---------------------------------------------------------------------- Comment By: Aharon Varady (aharon) Date: 2002-06-05 21:37 Message: Logged In: YES user_id=139355 Well, this remains (and has always been) a problem for my lists. I have never had a user posting with an aol.com address that this hasn't been the case with. Currently my solution is to replace the wrong address shown (philly_ambient(a)phobos.serve.com) with a generic or balnk mark. Here is the html source of a typical email from our pipermail archive, and below it the source email with headers. ------------------------------------------------------------- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html> <head> <title> [Philly_ambient] tool! </title> <link REL="Index" HREF="index.html" > <link REL="made" HREF="mailto:philly_ambient%40phobos.serve.com"> <meta NAME="robots" CONTENT="index,nofollow"> <link REL="Previous" href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002904.html"> <link REL="Next" href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002911.html"> <style TYPE="text/css"></style></head> <body BGCOLOR="#cccccc"><font face="Arial,Helvetica" size=-1><ul> <h4>[Philly_ambient] tool!</h4>Posted by <b>. . . .. . . .</b> on <i>Mon Jun 3 23:17:02 2002</i> <p></font><table cellpadding=3><tr><td bgcolor=#FFFFFF width="475"><font face="geneva,courier"><tt>  <pre>hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina </pre>  </tt></font></td></tr></table><font face="Arial,Helvetica" size=-1> <p>  <li> Previous message: <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002904.html">[Philly_ambient] Noise Deafinitions and playlist </a></li> <li> Next message: <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002911.html">[Philly_ambient] Do you hear what I hear? (re: noise deaf) </a></li> <li> <b>Messages sorted by:</b> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/date.html#2907">[ date ]</a> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/thread.html#2907">[ thread ]</a> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/subject.html#2907">[ subject ]</a> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/author.html#2907">[ author ]</a> </li> </body></html> --------------------------------------------------------------------- Here is the original email with headers: --------------------------------------------------------------- >From - Tue Jun 04 01:16:56 2002 X-UIDL: m;n!!9'f!!a2E"!3;D"! X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <philly_ambient-admin(a)phobos.serve.com> Delivered-To: aharon(a)phobos.serve.com Received: from phobos.serve.com (localhost.localdomain [127.0.0.1]) by phobos.serve.com (Postfix) with ESMTP id 6BC4D52D2B; Mon, 3 Jun 2002 23:17:06 -0400 (EDT) Delivered-To: philly_ambient(a)phobos.serve.com Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D for <philly_ambient(a)phobos.serve.com>; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn(a)aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for <philly_ambient(a)phobos.serve.com>; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn(a)aol.com Message-ID: <d4.184e63f9.2a2d8a9b(a)aol.com> To: philly_ambient(a)phobos.serve.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Mac - Post-GM sub 66 Subject: [Philly_ambient] tool! Sender: philly_ambient-admin(a)phobos.serve.com Errors-To: philly_ambient-admin(a)phobos.serve.com X-BeenThere: philly_ambient(a)phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient(a)phobos.serve.com List-Help: <mailto:philly_ambient-request@phobos.serve.com?subject=help> List-Post: <mailto:philly_ambient@phobos.serve.com> List-Subscribe: <http://phobos.serve.com/mailman/listinfo/philly_ambient>, <mailto:philly_ambient-request@phobos.serve.com?subject=subscribe> List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts <philly_ambient.phobos.serve.com> List-Unsubscribe: <http://phobos.serve.com/mailman/listinfo/philly_ambient>, <mailto:philly_ambient-request@phobos.serve.com?subject=unsubscribe> List-Archive: <http://phobos.serve.com/pipermail/philly_ambient/> X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT Date: Mon, 3 Jun 2002 23:14:35 EDT X-UIDL: m;n!!9'f!!a2E"!3;D"! hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina _______________________________________________ Philly_ambient mailing list Philly_ambient(a)phobos.serve.com Subscribe, Unsubscribe, Edit Options at: http://phobos.serve.com/mailman/listinfo/philly_ambient a PAC(MaN) List http://simpletone.com -------------------------------------------------------------------- I don't know why pipermail would treat my aol subscribers different either. But it is. Aharon ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-28 21:11 Message: Logged In: YES user_id=12800 Bizarre. I've never seen this, and I can't see any reason why Pipermail would treat aol.com addresses any different. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_i…

1 0

[ mailman-Patches-422468 ] Avoid multiple prefixes in Subject
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Patches item #422468, was opened at 2001-05-08 17:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=422468&group_i… Category: None >Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Johan Holmberg (holmberg) Assigned to: Nobody/Anonymous (nobody) Summary: Avoid multiple prefixes in Subject Initial Comment: Mailman often erroneously add more than one "list-prefix" to the Subject line if the Subject contains non-ASCII characters. Before adding a prefix Mailman tries to see if there already is a prefix (for example in the case of a reply to an earlier post to the same list). But Mailman is not "aware" that the prefix can be buried in the MIME-encoded part of the line. Therefore Mailman can add a 2nd prefix. The receiving mail client sees two prefixes after decoding the MIME stuff. In the next reply to the list we can get three prefixes, and so on .... And example Subject line can look like: Subject: Re: [Test] Re: [Test] Re: [Test] räkmsörgås The solution is to: - MIME-decode the subject - add list-name-prefix (if it isn't already there) - MIME-reencode the subject I have reported this solution earlier to "mailman-developers", see: http://mail.python.org/pipermail/mailman-developers/2001-April/004007.html The problems I describe here has been reported as bug #230400: [ #230400 ] German Umlaute mess up subject-line and body I attach my patch below. I have used it successfully on 2.0.1, and the file patched hasn't changed from 2.0.1 to 2.0.5. /Johan Holmberg ---------------------------------------------------------------------- Comment By: Dmitry Kohmanyuk (dk379) Date: 2002-03-10 02:30 Message: Logged In: YES user_id=15044 the patch I have mentioned is available with bug 528031. there is another patch in bug 498766 which can fix the same problem, but it seems to be for 2.1 version. ---------------------------------------------------------------------- Comment By: Dmitry Kohmanyuk (dk379) Date: 2002-03-10 02:07 Message: Logged In: YES user_id=15044 this patch does not seem to work with koi8-r encoding; I am submitting another which was done by vaget at vaget.org and then beautified by me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=422468&group_i…

1 0

[ mailman-Bugs-230400 ] German Umlaute mess up subject-line and body
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #230400, was opened at 2001-01-29 11:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=230400&group_i… Category: mail delivery >Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Thomas Franosch (tfra) Assigned to: Nobody/Anonymous (nobody) Summary: German Umlaute mess up subject-line and body Initial Comment: These characters (ö, ä, ü and probably even others) in the subject-line lead to a multiplication of the [listname] and Re: when one replies to such a mail. This is not because of a crapy mailer. The more replies, the longer the subject-line gets (if the author doesn not delete it manually). The characters in the subject-line actually get displayed correctly. Unfortunately, the use of them in the body leads to an unreadable mess as has already been posted here earlier. Needless to say that both these phenomenons are very annoying for actually at least every German list that runs mailman! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:30 Message: Logged In: YES user_id=12800 I believe all this stuff works much better in the latest MM2.1 betas. Please resubmit a bug report if you find problems with MM2.1 ---------------------------------------------------------------------- Comment By: Johan Holmberg (holmberg) Date: 2001-05-08 17:43 Message: Logged In: YES user_id=215003 The problems with non-ASCII characters in the Subject line can be fixed by applying my patch: ....[ #422468 ] Avoid multiple prefixes in Subject /Johan Holmberg ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=230400&group_i…

1 0

[ mailman-Bugs-231776 ] Digest From address causing mail loop
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #231776, was opened at 2001-02-09 17:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=231776&group_i… Category: mail delivery >Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: D.J. Atkinson (deejster) Assigned to: Nobody/Anonymous (nobody) Summary: Digest From address causing mail loop Initial Comment: Synopsis: Request that "From" address for digest distributions be changed from <list>-request to <list>-owner I just had a situation where: 1) Digest went out 2) The user at remote.com was unknown (for whatever reason) 3) mdaemon(a)remote.com replied to the digest From address ("list-request(a)here.com") 4) the MM request processor said "your commands don't make sense" and sent it back to mdaemon(a)remote.com 5) mdaemon(a)remote.com [which apparently is also a command processor] said "your commands don't make sense" and sent it back to list-request(a)here.com 6) 4 & 5 get repeated ad-infinitum and the message grows like a snowball rolling down a mountain. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:28 Message: Logged In: YES user_id=12800 This should be fixed in MM2.1 through various techniques, including not autoresponding to Priority: {junk,list,bulk} messages, and a built-in governor maxing out the number of responses sent to any one address per day. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=231776&group_i…

1 0

[ mailman-Bugs-419992 ] bin/arch messed up existing web archive
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #419992, was opened at 2001-04-29 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_i… Category: Pipermail >Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch messed up existing web archive Initial Comment: When running arch and webpages still exists, the web archive is messed up. This is quite confusing. A warning should be printed if arch is started on a list where there is already stuff in the web archive. Optionally it could delete the files is is regenerating first. Details: arch seems to attach each mail again to the .txt monthly archive files here and then build the web archive out of this. No wonder that the mail I deleted is still in after the process.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_i…

1 0

[ mailman-Bugs-427421 ] Configure script problem on Mac OS X.
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #427421, was opened at 2001-05-25 17:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=427421&group_i… Category: configuring/installing >Group: 2.0.x Status: Open Resolution: Works For Me Priority: 3 Submitted By: Deniau Thomas (thdeniau) Assigned to: Thomas Wouters (twouters) Summary: Configure script problem on Mac OS X. Initial Comment: I can't run configure on Mac OS X 10.0.3 (Darwin 1.3.3). When I run it as root I get : checking for --with-var-prefix... no checking for --with-username... mailman checking for mailman UID... ./configure: permission denied: conftest.py [1152] /usr/local/bin/python: can't open file 'conftest.py' cat: conftest.out: No such file or directory configure: error: ***** No "mailman" user found! ***** Your system must have a "mailman" user defined ***** (usually in your /etc/passwd file). Please see the INSTALL ***** file for details. And when I run it as a normal user :: checking for --with-var-prefix... no checking for --with-username... sh: setgroups: Operation not permitted thomas checking for thomas UID... 501 checking for --with-groupname... mailman ---------------------------------------------------------------------- Comment By: Deniau Thomas (thdeniau) Date: 2002-04-29 03:43 Message: Logged In: YES user_id=43625 Yep, with mailman 2.0.10 / Mac OS X 10.1.4 I've still this error when configuring as normal user : checking for --with-var-prefix... no checking for --with-username... sh: setgroups: Operation not permitted I've to chown and su mailman the sources dir to make it work. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-28 17:50 Message: Logged In: YES user_id=12800 There hasn't been any new information on this bug in a long time. Is this a problem? ---------------------------------------------------------------------- Comment By: Deniau Thomas (thdeniau) Date: 2001-06-04 18:59 Message: Logged In: YES user_id=43625 The original problem (configure on mac OS X) isn't fixed. The configure script only works if you su mailman and chown mailman the sources dir before doing configure. There is still an odd bug with conftest.py if you su root before configuring ... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2001-06-04 14:36 Message: Logged In: YES user_id=12800 I suspect you might not be running qrunner properly from cron. Please read the README files about how to set this up. In any event, I'm closing this bug report, since the original problem (configure on MacOSX) seems to be solved. If you think you have another bug related to sending mail, please submit a new bug report. ---------------------------------------------------------------------- Comment By: Deniau Thomas (thdeniau) Date: 2001-05-30 07:57 Message: Logged In: YES user_id=43625 [thomac:~] thomas% cat > conftest.py print "hello world" [thomac:~] thomas% python conftest.py hello world this works ... OK, I've checked out the stable version ... make works perfectly, but I don't get the welcome mail when I create a new test list. i'm using Postfix as MTA and my aliases are correctly setup. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-05-30 06:58 Message: Logged In: YES user_id=34209 Oops, again. I should have been more explicit in checking out the CVS tree: if you want a stable Mailman, you should check out Mailman using cvs -d <CVSROOT> co -rRelease_2_0_1-branch mailman (after moving the old 'mailman' directory asside.) The head of the CVS tree is for Mailman 2.1, and is probably best described as "pleasantly unstable", not quite unlike Barry's poems :) The 2.0.1 release branch is currently 2.0.5 plus a few bugfixes, including the PREFIX one. I'm still stumped about the conftest.py failure, though. Can you create a file 'conftest.py' with a few lines of Python code ("print 'hello world'" will do) and try to execute it using "/usr/local/bin/python conftest.py" ? I wonder if it might be a problem with your python, in that it doesn't understand current working directories and such. (In fact.... Wasn't there a thread on python-dev not so long ago about how MacOS didn't have the concept of a current working directory ? :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2001-05-29 14:40 Message: Logged In: YES user_id=12800 Maybe you have an old version of mimelib? In version 0.3 the ReprMixin class was renamed to StringableMixin. ---------------------------------------------------------------------- Comment By: Deniau Thomas (thdeniau) Date: 2001-05-29 14:34 Message: Logged In: YES user_id=43625 hMmm ... i've tried with cvs. I installed mimelib and now, the compilation of common.c runs properly, but now I get the error : Traceback (most recent call last): File "bin/update", line 46, in ? from Mailman import MailList File "/usr/local/mailman/Mailman/MailList.py", line 42, in ? from Mailman.ListAdmin import ListAdmin File "/usr/local/mailman/Mailman/ListAdmin.py", line 33, in ? from Mailman import Message File "/usr/local/mailman/Mailman/Message.py", line 26, in ? from mimelib.StringableMixin import StringableMixin ImportError: No module named StringableMixin And there's still the configure problem. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-05-29 14:12 Message: Logged In: YES user_id=34209 D'oh! I just realized what the difference is... I'm using the current CVS tree, in which I fixed at least the PREFIX bug. I'm guessing you aren't. Can you try the CVS tree ? If you don't have access to cvs on your darwin box, let me know and I'll mail you a .tgz of a current snapshot. ---------------------------------------------------------------------- Comment By: Deniau Thomas (thdeniau) Date: 2001-05-29 12:37 Message: Logged In: YES user_id=43625 make -v GNU Make version 3.79, by Richard Stallman and Roland McGrath. Built for powerpc-apple-darwin1.0 Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. cc -v Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs Apple Computer, Inc. version gcc-926, based on gcc version 2.95.2 19991024 (release) and for the configure problem : i'm able to sudo ... and even as root, the install fails. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-05-29 12:28 Message: Logged In: YES user_id=34209 One thing that might matter is that I had root-privs, meaning that I was allowed to do sudo. Other than that, I do the exact same thing as you, and it really works fine. The other problem is even stranger! The 'cc' line you quote has the -DPREFIX= line, which defines 'PREFIX', but then cc complains that it isn't defined ?? What version of cc and make are you using ? it worked fine with: [localhost:~/mailman-2.0] thomas% cc -v Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs Apple Computer, Inc. version gcc-926, based on gcc version 2.95.2 19991024 (release) [localhost:~/mailman-2.0] thomas% make -v GNU Make version 3.79, by Richard Stallman and Roland McGrath. Built for powerpc-apple-darwin1.0 if your make doesn't report the version on -v, you're using BSD make (aka 'bsdmake' on darwin.) Try running 'gnumake' -- it wouldn't be the first weirdness being solved by using gmake instead of bsdmake :) ---------------------------------------------------------------------- Comment By: Deniau Thomas (thdeniau) Date: 2001-05-29 12:19 Message: Logged In: YES user_id=43625 HFS+ filesystem, too. I've the problem on a fresh download : the file conftest.py doesn't exist. Even I if chmod -R 777 the mailman folder, this doesn't work. The only way to configure properly is to chown the repertory to mailman and to run the configure as mailman, or to chown -R 777 continuously while configure runs. Very very odd. Maybe because HFS+ is case-insensitive ... And, even if I run configure as mailman, make install fails : cc -c -I. -DPREFIX="\/usr/local/mailman\" -DPYTHON="\/usr/local/bin/python\" -DHELPFUL -g -O2 -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 ./common.c:26: `PREFIX' undeclared here (not in a function) ./common.c:26: `scripts' undeclared here (not in a function) ./common.c:26: parse error before `;' make[1]: *** [common.o] Error 1 ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-05-29 12:02 Message: Logged In: YES user_id=34209 It works fine on my colleague's darwin 1.3.3, on a HFS+ filesystem. I suspect that you have a 'conftest.py' leftover from a previous run, and with odd permissions. Try deleting it, and see if that helps. You do need to make a 'mailman' user and group, though, just like the README says. I didn't want to totally screw my colleague's machine (he sits within striking distance of me) so I didn't actually install, but configure and make both went fine. (Contrary to compiling Python... Cost me a good two hours to compile python on the box :) ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-05-29 09:30 Message: Logged In: YES user_id=34209 Going to check on this on my colleague's MacOS X box. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=427421&group_i…

1 0

[ mailman-Patches-546362 ] Includes subject in mailto links
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Patches item #546362, was opened at 2002-04-19 20:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=546362&group_i… Category: Pipermail >Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Nicholas Russo (narusso) Assigned to: Nobody/Anonymous (nobody) Summary: Includes subject in mailto links Initial Comment: Each article in an archive lists the original sender in a mailto url at the top of the page and in the html headers. These urls could also contain the subject of the message, and the message id so the MUA may automatically set the In-Reply-To header and Subject line when resolving the url. The first diff should be used for the article.html template in each language. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:25 Message: Logged In: YES user_id=12800 This will be applied to MM2.1beta4 ---------------------------------------------------------------------- Comment By: Nicholas Russo (narusso) Date: 2002-04-20 12:09 Message: Logged In: YES user_id=118704 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=546362&group_i…

1 0

[ mailman-Bugs-443952 ] add subject to mailto link in archive
by noreply＠sourceforge.net 24 Aug '02

24 Aug '02

Bugs item #443952, was opened at 2001-07-23 19:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=443952&group_i… Category: Pipermail >Group: 2.1 beta >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Stig Hackvan (hackvan) Assigned to: Nobody/Anonymous (nobody) Summary: add subject to mailto link in archive Initial Comment: subjects should be specified in mailto links where appropriate. example: if i'm browsing, say, the email archive for linux/tulip drivers at http://www.scyld.com/pipermail/tulip/2001- April/003370.html and i wish to reply by clicking on becker(a)scyld.com, then it's 99% probable that i want the subject to be specified as "Re: [tulip] Any sucess with Conexant miniPCI (presario notebooks) on Linux?" ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:24 Message: Logged In: YES user_id=12800 I've applied Nicholas Russo's patch for MM2.1b4. ---------------------------------------------------------------------- Comment By: Nicholas Russo (narusso) Date: 2002-04-19 20:46 Message: Logged In: YES user_id=118704 see patch number 546362 While looking through instantiations of article.html, I noticed some mailto urls use the character encoding for '@' and others do not. I presume this is arbitrary? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-19 18:51 Message: Logged In: YES user_id=12800 I'll accept a patch for this, but I have little enthusiasm to work up the patch myself. Care to submit one? ---------------------------------------------------------------------- Comment By: Nicholas Russo (narusso) Date: 2002-04-18 00:09 Message: Logged In: YES user_id=118704 Unfortunately, the resolver of a mailto URL is not expected to respect an embedded In-Reply-To header, which would preserve the threading information. Failing that, a Subject header would at least be a start. ---------------------------------------------------------------------- Comment By: Stig Hackvan (hackvan) Date: 2001-07-25 05:27 Message: Logged In: YES user_id=17610 hypermail does this, by the way... an example link is mailto:becker@scyld.com?Subject=Re:%20[tulip]%20Conexant% 20LANfinity&In-Reply-To=<Pine.LNX.4.10.10104090257090.4813- 100000(a)vaio.greennet> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=443952&group_i…

1 0

[ mailman-Bugs-431511 ] charset="Windows-1252" in archive
by noreply＠sourceforge.net 23 Aug '02

23 Aug '02

Bugs item #431511, was opened at 2001-06-08 18:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=431511&group_i… Category: Pipermail >Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Ingimar Robertsson (iar) Assigned to: Nobody/Anonymous (nobody) >Summary: charset="Windows-1252" in archive Initial Comment: The archives seem to have trouble with Windows-1252 encoding. This is from the headers of such message: Content-Type: text/plain; charset="Windows-1252" Subject: [F1] =?Windows-1252?Q? RE=3A_=5BF1=5D_=5BF1=5D_Sp=E1_fyrir_Monako?= The Subject appears like this in the archives instead of being decoded. Don't know if this is a bug with the email client or Mailman but thought I'd mention it, there seems to be a lot of these things acording to a Google search for Mailman and Windows-1252. ---------------------------------------------------------------------- Comment By: Ben Gertzfield (che_fox) Date: 2001-08-09 21:31 Message: Logged In: YES user_id=89313 The bug is in HyperArch.py line 158. Check out the patch attached to bug report #449677 at http://sourceforge.net/tracker/index.php?func=detail&aid=449677&group_id=10… -- actually, I just realized I should upload it to the Patches section as well, and will do so now. The problem is that HyperArch.py assumes charsets are in the form \w+ (a-z A-Z 0-9 _ only). But they can and do have other characters like -, as you've seen. The patch is to replace "\w+" in HyperArch line 158 with: ".+?" This will make it match any character non-greedily up to the next ", without going past it. Hope this helps! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=431511&group_i…

1 0