From dan.mick@sun.com Fri Nov 1 03:03:50 2002 From: dan.mick@sun.com (Dan Mick) Date: Thu, 31 Oct 2002 19:03:50 -0800 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> Message-ID: <3DC1EF16.6070400@sun.com> Barry A. Warsaw wrote: > A quick fix for the Archiver problems, until I can debug them more is > to add the following in ArchRunner.py, just under the "class > ArchRunner" line: > > class ArchRunner(Runner): > QDIR = mm_cfg.ARCHQUEUE_DIR > SLEEPTIME = mm_cfg.minutes(10) > > def _dispose(self, mlist, msg, msgdata): > > This at least makes ArchRunner only run once per 10 minutes. > > -Barry The problem's affecting me badly right now too. So far it seems that the holdup is in the 'date.html' index file processing; everything else is finished, but the "bin/qrunner -r Arch -o" process has lost its little mind trying to write the date index. It's in a loop, chewing up 409600 bytes of memory (brk), and then opening, reading, and closing archidxentry.html, hundreds of times in a row. It's been doing this for about 15 minutes now. (yes, one message.) The process size is 203MB and 196M is resident. Clearly, there's some horrible misuse of objects in the date-processing stuff, but I lost track of the pdb before it got into the date stuff so I don't have a lot of visibility yet. I have a number of files queued up, though, so I can try again as soon as it ends. From chuqui@plaidworks.com Fri Nov 1 03:11:39 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Thu, 31 Oct 2002 19:11:39 -0800 Subject: [Mailman-Developers] CVS glitch. In-Reply-To: <3DC18F12.8040704@sun.com> Message-ID: Sure. It finds stuff that's otherwise missing... and my problem went away. Sigh. i'll fix my CVS commands. Thanks, all. cvs -q up -P -d -A ? misc/email-2.3 ? misc/email-2.4.3 ? misc/JapaneseCodecs-1.4.8 ? misc/KoreanCodecs-2.0.5 P ACKNOWLEDGMENTS P NEWS P README.EXIM U README.MACOSX P TODO P UPGRADING P admin/www/MMGenerator.py P admin/www/download.ht P admin/www/download.html U admin/www/faq.ht P admin/www/faq.html P admin/www/i18n.ht P admin/www/i18n.html P admin/www/index.ht P admin/www/index.html P admin/www/mailman.html P admin/www/todo.ht P admin/www/todo.html P bin/add_members P bin/arch P bin/change_pw P bin/check_db P bin/check_perms P bin/cleanarch P bin/clone_member P bin/config_list P bin/dumpdb P bin/find_member P bin/genaliases P bin/inject P bin/list_admins P bin/list_lists P bin/list_members P bin/mailmanctl P bin/mmsitepass P bin/newlist P bin/pygettext.py P bin/qrunner P bin/remove_members P bin/rmlist P bin/sync_members P bin/transcheck P bin/unshunt P bin/update P bin/withlist P cron/bumpdigests P cron/checkdbs P cron/disabled P cron/gate_news P cron/mailpasswds P cron/nightly_gzip P cron/senddigests U doc/mailman-admin.tex P messages/mailman.pot U messages/cs/LC_MESSAGES/mailman.mo P messages/cs/LC_MESSAGES/mailman.po U messages/de/LC_MESSAGES/mailman.mo P messages/de/LC_MESSAGES/mailman.po U messages/es/LC_MESSAGES/mailman.mo P messages/es/LC_MESSAGES/mailman.po U messages/fi/LC_MESSAGES/mailman.mo P messages/fi/LC_MESSAGES/mailman.po U messages/fr/LC_MESSAGES/mailman.mo P messages/fr/LC_MESSAGES/mailman.po U messages/hu/LC_MESSAGES/mailman.mo P messages/hu/LC_MESSAGES/mailman.po U messages/it/LC_MESSAGES/mailman.mo P messages/it/LC_MESSAGES/mailman.po U messages/ja/LC_MESSAGES/mailman.mo P messages/ja/LC_MESSAGES/mailman.po U messages/ko/LC_MESSAGES/mailman.mo P messages/ko/LC_MESSAGES/mailman.po U messages/nl/LC_MESSAGES/mailman.mo P messages/nl/LC_MESSAGES/mailman.po U messages/no/LC_MESSAGES/mailman.mo P messages/no/LC_MESSAGES/mailman.po U messages/pt_BR/LC_MESSAGES/mailman.mo P messages/pt_BR/LC_MESSAGES/mailman.po U messages/ru/LC_MESSAGES/mailman.mo P messages/ru/LC_MESSAGES/mailman.po U messages/sv/LC_MESSAGES/mailman.mo P messages/sv/LC_MESSAGES/mailman.po U misc/email-2.4.3.tar.gz P misc/paths.py.in P src/common.h P templates/it/article.html P templates/it/postauth.txt P templates/ja/listinfo.html P templates/ja/options.html P templates/ja/roster.html U templates/no/archidxfoot.html U templates/no/archidxhead.html U templates/no/archliststart.html U templates/no/archtoc.html U templates/no/archtocentry.html P templates/no/article.html P templates/no/postack.txt P templates/ru/options.html P tests/test_bounces.py U tests/bounces/dsn_10.txt U tests/bounces/microsoft_01.txt U tests/bounces/microsoft_02.txt # cvs -q up -d -P -A ? misc/email-2.3 ? misc/email-2.4.3 ? misc/JapaneseCodecs-1.4.8 ? misc/KoreanCodecs-2.0.5 On Thursday, October 31, 2002, at 12:14 PM, Dan Mick wrote: > Dale Newfield wrote: >>>> What happens when you do "cvs -q up -P -d -A" ? >>> > What he said; Chuq, can you soothe my mind about the panacea for CVS's > brokenness, and try those flags? > -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From bob@nleaudio.com Fri Nov 1 06:31:48 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Fri, 1 Nov 2002 02:31:48 -0400 Subject: [Mailman-Developers] CVS glitch. In-Reply-To: References: <3DC18F12.8040704@sun.com> Message-ID: <20021101063148.M62358@nleaudio.com> Perhaps the docs on the website should be updated to reflect these commands, so others don't have the same problems. Bob > Sure. It finds stuff that's otherwise missing... > > and my problem went away. Sigh. i'll fix my CVS commands. Thanks, all. > > cvs -q up -P -d -A > ? misc/email-2.3 > ? misc/email-2.4.3 > ? misc/JapaneseCodecs-1.4.8 > ? misc/KoreanCodecs-2.0.5 > P ACKNOWLEDGMENTS > P NEWS > P README.EXIM > U README.MACOSX > P TODO > P UPGRADING > P admin/www/MMGenerator.py > P admin/www/download.ht > P admin/www/download.html > U admin/www/faq.ht > P admin/www/faq.html > P admin/www/i18n.ht > P admin/www/i18n.html > P admin/www/index.ht > P admin/www/index.html > P admin/www/mailman.html > P admin/www/todo.ht > P admin/www/todo.html > P bin/add_members > P bin/arch > P bin/change_pw > P bin/check_db > P bin/check_perms > P bin/cleanarch > P bin/clone_member > P bin/config_list > P bin/dumpdb > P bin/find_member > P bin/genaliases > P bin/inject > P bin/list_admins > P bin/list_lists > P bin/list_members > P bin/mailmanctl > P bin/mmsitepass > P bin/newlist > P bin/pygettext.py > P bin/qrunner > P bin/remove_members > P bin/rmlist > P bin/sync_members > P bin/transcheck > P bin/unshunt > P bin/update > P bin/withlist > P cron/bumpdigests > P cron/checkdbs > P cron/disabled > P cron/gate_news > P cron/mailpasswds > P cron/nightly_gzip > P cron/senddigests > U doc/mailman-admin.tex > P messages/mailman.pot > U messages/cs/LC_MESSAGES/mailman.mo > P messages/cs/LC_MESSAGES/mailman.po > U messages/de/LC_MESSAGES/mailman.mo > P messages/de/LC_MESSAGES/mailman.po > U messages/es/LC_MESSAGES/mailman.mo > P messages/es/LC_MESSAGES/mailman.po > U messages/fi/LC_MESSAGES/mailman.mo > P messages/fi/LC_MESSAGES/mailman.po > U messages/fr/LC_MESSAGES/mailman.mo > P messages/fr/LC_MESSAGES/mailman.po > U messages/hu/LC_MESSAGES/mailman.mo > P messages/hu/LC_MESSAGES/mailman.po > U messages/it/LC_MESSAGES/mailman.mo > P messages/it/LC_MESSAGES/mailman.po > U messages/ja/LC_MESSAGES/mailman.mo > P messages/ja/LC_MESSAGES/mailman.po > U messages/ko/LC_MESSAGES/mailman.mo > P messages/ko/LC_MESSAGES/mailman.po > U messages/nl/LC_MESSAGES/mailman.mo > P messages/nl/LC_MESSAGES/mailman.po > U messages/no/LC_MESSAGES/mailman.mo > P messages/no/LC_MESSAGES/mailman.po > U messages/pt_BR/LC_MESSAGES/mailman.mo > P messages/pt_BR/LC_MESSAGES/mailman.po > U messages/ru/LC_MESSAGES/mailman.mo > P messages/ru/LC_MESSAGES/mailman.po > U messages/sv/LC_MESSAGES/mailman.mo > P messages/sv/LC_MESSAGES/mailman.po > U misc/email-2.4.3.tar.gz > P misc/paths.py.in > P src/common.h > P templates/it/article.html > P templates/it/postauth.txt > P templates/ja/listinfo.html > P templates/ja/options.html > P templates/ja/roster.html > U templates/no/archidxfoot.html > U templates/no/archidxhead.html > U templates/no/archliststart.html > U templates/no/archtoc.html > U templates/no/archtocentry.html > P templates/no/article.html > P templates/no/postack.txt > P templates/ru/options.html > P tests/test_bounces.py > U tests/bounces/dsn_10.txt > U tests/bounces/microsoft_01.txt > U tests/bounces/microsoft_02.txt > > # cvs -q up -d -P -A > ? misc/email-2.3 > ? misc/email-2.4.3 > ? misc/JapaneseCodecs-1.4.8 > ? misc/KoreanCodecs-2.0.5 > > On Thursday, October 31, 2002, at 12:14 PM, Dan Mick wrote: > > > Dale Newfield wrote: > >>>> What happens when you do "cvs -q up -P -d -A" ? > >>> > > > What he said; Chuq, can you soothe my mind about the panacea for CVS's > > brokenness, and try those flags? > > > > -- > Chuq Von Rospach, Architech > chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ > > Stress is when you wake up screaming and you realize you haven't > fallen asleep yet. > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From pioppo@ferrara.linux.it Fri Nov 1 10:15:14 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Fri, 1 Nov 2002 11:15:14 +0100 Subject: [Mailman-Developers] re: Much cpu/memory load In-Reply-To: <3DC1EF16.6070400@sun.com> References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> Message-ID: <20021101101514.GB2899@ferrara.linux.it> On Thu, Oct 31, 2002 at 07:03:50PM -0800, Dan Mick wrote: > The problem's affecting me badly right now too. So far it seems that the > holdup is in the 'date.html' index file processing; everything else is > finished, but the "bin/qrunner -r Arch -o" process has lost its little mind > trying to write the date index. It's in a loop, chewing up 409600 bytes of > memory (brk), and then opening, reading, and closing archidxentry.html, > hundreds of times in a row. Ok, I believe this is because of my patch for i18n in archives. Do you feel like trying this patch? It should speed up things a lot.... Index: HyperArch.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v retrieving revision 2.22 diff -u -r2.22 HyperArch.py --- HyperArch.py 19 Oct 2002 20:59:27 -0000 2.22 +++ HyperArch.py 1 Nov 2002 10:13:21 -0000 @@ -923,10 +923,14 @@ 'sequence': article.sequence, 'author': author } - print Utils.maketext( - 'archidxentry.html', d, raw=1, - lang=self.maillist.preferred_language, - mlist=self.maillist) + print """
  • %(subject)s +   + %(author)s + """ % d + #print Utils.maketext( + # 'archidxentry.html', d, raw=1, + # lang=self.maillist.preferred_language, + # mlist=self.maillist -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From danny@terweij.nl Fri Nov 1 11:15:01 2002 From: danny@terweij.nl (Danny Terweij) Date: Fri, 1 Nov 2002 12:15:01 +0100 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> Message-ID: <019001c28197$ec0301a0$1e00a8c0@onsnet.org> From: "Dan Mick" > Barry A. Warsaw wrote: > > A quick fix for the Archiver problems, until I can debug them more is > > to add the following in ArchRunner.py, just under the "class > > ArchRunner" line: > The problem's affecting me badly right now too. So far it seems that the > holdup is in the 'date.html' index file processing; everything else is > finished, but the "bin/qrunner -r Arch -o" process has lost its little mind > trying to write the date index. It's in a loop, chewing up 409600 bytes of > memory (brk), and then opening, reading, and closing archidxentry.html, > hundreds of times in a row. As i said before i did also thought it was a loop orso. So i do not add this quick fix :) i have set the optoin to achrive to mbox only and at night i recreate the achrives now. I hope there will be a working fix soon... Danny Terweij From danny@terweij.nl Fri Nov 1 11:17:50 2002 From: danny@terweij.nl (Danny Terweij) Date: Fri, 1 Nov 2002 12:17:50 +0100 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu><000f01c2811d$f1e55b10$1e00a8c0@onsnet.org><15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> Message-ID: <019a01c28198$50ad6c30$1e00a8c0@onsnet.org> From: "Simone Piunno" > > The problem's affecting me badly right now too. So far it seems that the > Ok, I believe this is because of my patch for i18n in archives. > Do you feel like trying this patch? > It should speed up things a lot.... > Index: HyperArch.py > =================================================================== Gonna try this. Danny. From Dale@Newfield.org Fri Nov 1 13:46:48 2002 From: Dale@Newfield.org (Dale Newfield) Date: Fri, 1 Nov 2002 08:46:48 -0500 (EST) Subject: [Mailman-Developers] python.org mailing list memberships reminder (fwd) Message-ID: I'm guessing from this (and the settings I've got on these lists) that setting the "Get password reminder email for this list?" flag to "No" doesn't work. -Dale ---------- Forwarded message ---------- Date: Fri, 01 Nov 2002 05:00:22 -0500 From: mailman-21-owner@python.org To: Dale@newfield.org Subject: python.org mailing list memberships reminder This is a reminder, sent out once a month, about your python.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. From barry@python.org Fri Nov 1 14:46:12 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 1 Nov 2002 09:46:12 -0500 Subject: [Mailman-Developers] CVS glitch. References: <3DC18F12.8040704@sun.com> <20021101063148.M62358@nleaudio.com> Message-ID: <15810.37812.33652.892873@gargle.gargle.HOWL> >>>>> "bob" == writes: bob> Perhaps the docs on the website should be updated to reflect bob> these commands, so others don't have the same problems. Thing is, -A usually /shouldn't/ be necessary unless folks are trying to checkout a specific branch, tag, or date. And unless you're doing maintenance on the 2.0 branch, or you want to see what 2.1b3 was like, you probably aren't doing that. So I still want to know why Chuq finds it necessary to include the -A flag. Chuq, does your CVS directory have a Tag file in it? -Barry From Dan.Mick@sun.com Fri Nov 1 20:18:48 2002 From: Dan.Mick@sun.com (Dan Mick) Date: Fri, 01 Nov 2002 12:18:48 -0800 Subject: [Mailman-Developers] CVS glitch. References: <3DC18F12.8040704@sun.com> <20021101063148.M62358@nleaudio.com> <15810.37812.33652.892873@gargle.gargle.HOWL> Message-ID: <3DC2E1A8.2020405@sun.com> Barry A. Warsaw wrote: >>>>>>"bob" == writes: > > > bob> Perhaps the docs on the website should be updated to reflect > bob> these commands, so others don't have the same problems. > > Thing is, -A usually /shouldn't/ be necessary unless folks are trying > to checkout a specific branch, tag, or date. And unless you're doing > maintenance on the 2.0 branch, or you want to see what 2.1b3 was like, > you probably aren't doing that. > > So I still want to know why Chuq finds it necessary to include the -A > flag. Chuq, does your CVS directory have a Tag file in it? None of mine do, and I've definitely missed things in the past that -A has gotten me. From Dan.Mick@sun.com Fri Nov 1 20:20:11 2002 From: Dan.Mick@sun.com (Dan Mick) Date: Fri, 01 Nov 2002 12:20:11 -0800 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> Message-ID: <3DC2E1FB.5050201@sun.com> Simone Piunno wrote: > On Thu, Oct 31, 2002 at 07:03:50PM -0800, Dan Mick wrote: > > >>The problem's affecting me badly right now too. So far it seems that the >>holdup is in the 'date.html' index file processing; everything else is >>finished, but the "bin/qrunner -r Arch -o" process has lost its little mind >>trying to write the date index. It's in a loop, chewing up 409600 bytes of >>memory (brk), and then opening, reading, and closing archidxentry.html, >>hundreds of times in a row. > > > Ok, I believe this is because of my patch for i18n in archives. > Do you feel like trying this patch? > It should speed up things a lot.... > > Index: HyperArch.py > =================================================================== > RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v > retrieving revision 2.22 > diff -u -r2.22 HyperArch.py > --- HyperArch.py 19 Oct 2002 20:59:27 -0000 2.22 > +++ HyperArch.py 1 Nov 2002 10:13:21 -0000 > @@ -923,10 +923,14 @@ > 'sequence': article.sequence, > 'author': author > } > - print Utils.maketext( > - 'archidxentry.html', d, raw=1, > - lang=self.maillist.preferred_language, > - mlist=self.maillist) > + print """
  • %(subject)s > +   > + %(author)s > + """ % d > + #print Utils.maketext( > + # 'archidxentry.html', d, raw=1, > + # lang=self.maillist.preferred_language, > + # mlist=self.maillist > That's definitely the cause of the many opens of archidxentry.html, but it doesn't explain the 400K-per-iteration growth. Barry, wasn't there some Python instrumentation trick for using the GC to find unreferenced objects and complain, or invoking GC manually in a loop to try to alleviate such problems?....was it in the gc module?... From Dan.Mick@sun.com Fri Nov 1 20:37:37 2002 From: Dan.Mick@sun.com (Dan Mick) Date: Fri, 01 Nov 2002 12:37:37 -0800 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> <3DC2E1FB.5050201@sun.com> Message-ID: <3DC2E611.3070406@sun.com> Dan Mick wrote: > Simone Piunno wrote: > >> On Thu, Oct 31, 2002 at 07:03:50PM -0800, Dan Mick wrote: >> >> >>> The problem's affecting me badly right now too. So far it seems that >>> the holdup is in the 'date.html' index file processing; everything >>> else is finished, but the "bin/qrunner -r Arch -o" process has lost >>> its little mind trying to write the date index. It's in a loop, >>> chewing up 409600 bytes of memory (brk), and then opening, reading, >>> and closing archidxentry.html, >>> hundreds of times in a row. >> >> >> >> Ok, I believe this is because of my patch for i18n in archives. >> Do you feel like trying this patch? It should speed up things a lot.... >> >> Index: HyperArch.py >> =================================================================== >> RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v >> retrieving revision 2.22 >> diff -u -r2.22 HyperArch.py >> --- HyperArch.py 19 Oct 2002 20:59:27 -0000 2.22 >> +++ HyperArch.py 1 Nov 2002 10:13:21 -0000 >> @@ -923,10 +923,14 @@ >> 'sequence': article.sequence, >> 'author': author >> } >> - print Utils.maketext( >> - 'archidxentry.html', d, raw=1, >> - lang=self.maillist.preferred_language, >> - mlist=self.maillist) >> + print """
  • %(subject)s >> +   >> + %(author)s >> + """ % d >> + #print Utils.maketext( >> + # 'archidxentry.html', d, raw=1, >> + # lang=self.maillist.preferred_language, >> + # mlist=self.maillist >> > > That's definitely the cause of the many opens of archidxentry.html, but it > doesn't explain the 400K-per-iteration growth. > > Barry, wasn't there some Python instrumentation trick for using the GC > to find unreferenced objects and complain, or invoking GC manually in a > loop to try to alleviate such problems?....was it in the gc module?... yes, with that patch the opens of archidxentry.html go away, and now its only system call activity is brk() after brk() after brk() (with an occasional flush of buffers to date.html). Something is wrong in the date-processing loop that's leaking memory hand-over-fist. From Dan.Mick@sun.com Fri Nov 1 21:05:04 2002 From: Dan.Mick@sun.com (Dan Mick) Date: Fri, 01 Nov 2002 13:05:04 -0800 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> <3DC2E1FB.5050201@sun.com> <3DC2E611.3070406@sun.com> Message-ID: <3DC2EC80.5010702@sun.com> Dan Mick wrote: >> Barry, wasn't there some Python instrumentation trick for using the GC >> to find unreferenced objects and complain, or invoking GC manually in >> a loop to try to alleviate such problems?....was it in the gc module?... Adding this: --- /usr/local/src/mailman/Mailman/Archiver/pipermail.py Tue Oct 15 20:22 :49 2002 +++ /export/home/mailman/Mailman/Archiver/pipermail.py Fri Nov 1 12:48:47 2002 @@ -9,6 +9,7 @@ import cPickle as pickle from cStringIO import StringIO from string import lowercase +import gc __version__ = '0.09 (Mailman edition)' VERSION = __version__ @@ -425,6 +426,7 @@ self._update_thread_index(archive, arcdir) def _update_simple_index(self, hdr, archive, arcdir): + gc.set_debug(gc.DEBUG_LEAK) self.message(" " + hdr) self.type = hdr hdr = hdr.lower() @@ -442,6 +444,7 @@ else: count = count + 1 self.write_index_entry(article) + sys.stderr.write("gc, number of uncollectables: %d\n" % gc.collect( )) msgid = self.database.next(archive, hdr) # Finish up this index self.write_index_footer() prints a bunch of "gc, number of uncollectables: 0", and doesn't stop the memory growth. Note that the time between each round of brks() is high, too, as though there's a *lot* of userland work going on. That process can take 70% of a CPU by itself while running. From e008993@cobalt.sbirmc.ac.uk Fri Nov 1 14:45:03 2002 From: e008993@cobalt.sbirmc.ac.uk (Martin Whinnery ) Date: Fri, 1 Nov 2002 14:45:03 +0000 (GMT) Subject: [Mailman-Developers] Help programming MemberAdaptor... Message-ID: On Wed, 30 Oct 2002, Greg Ward wrote: > > What I'd really like to do is have lists EITHER populate in the normal > > file way OR populated from LDAP. I was thinking I might use an address > > like > > Err, define "populate". Is this a one-time thing? Or do you want the > list membership to always come from an LDAP lookup? > The latter. I help run a large educational campus, and we hold all accounts and groups in LDAP. These groups change membership over time, and I want to associate mailing lists with some of them. What I don't need is the headache of remembering to keep the memberships in sync. > If the former, I would just write a script that does the LDAP query and > sets the list population from it. Use bin/add_members as an example. > If we absolutely must. It's what we do with DNS and DHCP. But I'd rather not. Just more code to maintain. > If the latter, why use Mailman at all? Why not just use an MTA that can > lookup aliases using LDAP, and then send mail to that alias? I'm pretty > sure both Exim and postfix can do that. > 'Cos mailman does the [approve|reject|defer|discard] thing. And archives. And it deals with 'real' mailing lists (which we would die rather than lose). Martin Whinnery *Assistant* Network Manager South Birmingham College 'Just the assistant' From e008993@cobalt.sbirmc.ac.uk Fri Nov 1 15:01:14 2002 From: e008993@cobalt.sbirmc.ac.uk (Martin Whinnery ) Date: Fri, 1 Nov 2002 15:01:14 +0000 (GMT) Subject: [Mailman-Developers] More extend.py questions Message-ID: On Wed, 30 Oct 2002, Greg Ward wrote: > On 30 October 2002, Martin Whinnery said: > > Please indulge a python virgin. Barry has advised someone to 'overload > > the Load & Save function' in extend.py . Would someone help me with a > > little sample? It doesn't need to do anything useful, just replace the > > original function. > > Huh? There's no file called extend.py in the Mailman source tree. Just > what are you trying to accomplish? > And I quote (From NEWS 2.36) " - Membership Adaptors o Internally, mailing list memberships are accessed through a MemberAdaptor interface. This would allow for integrating membership databases with external sources (e.g. Zope or LDAP), although the only MemberAdaptor currently implemented is a "classic" adaptor which stores the membership information on the MailList object. ... - List Extensibility o A framework has been added which can be used to specialize and extend specific mailing lists. If there is a file called lists//extend.py, it is execfile()'d after the MailList object is instantiated. The file should contain a function extend() which will be called with the MailList instance... " Now after a little more digging (And I take your point about not hacking the actual source, I don't know what I was thinking. Probably why I'm 'just the assistant') it appears that what I need to do is implement new Load() and Save() functions ( orginally defined in MailList.py ), which cause membership information to be read into the mlist structure from LDAP rather than from config.pck, and which fail to write that information back to config.pck. Or rather, (after more digging), Save() should remove all the membership information from the MailList instance before calling the original Save(), and Load should call the original Load() then replace any membership information with info taken from LDAP. I appreciate that this will leave membership options unable to be changed, but that's what we want. A later version might be able to write that info back to LDAP, but there's authentication issues and the matter of schema definitions, and I don't need to go there just yet. Now, what I want is for the Load() and Save() functions defined in MailList.py to be overridden for this list with my own versions. I just don't understand Python/Mailman well enough. --------- My efforts so far ------------- # /usr/local/mailman/lists/ldaplist/extend.py def extend(mlist): mlist.OldSave = mlist.Save def MySave(self): print "WOOKIE" # So I can see it in withlist mlist.__class__.Save(self) mlist.Save = MySave -------- snip snip ---------------------- But when I try m.Save(m) from within "withlist ldaplist", I get a 'NotLocked' error: NotLockedError: : None And at this point I'm pretty well stuck. Any examples, flames, advice or witticisms will be revered in a darkened room. Thanks in advance (I like the desperate sound that makes when I say it) Martin Whinnery "Just the" Assistant Network Manager South Birmingham College From dan.mick@sun.com Sat Nov 2 03:56:55 2002 From: dan.mick@sun.com (Dan Mick) Date: Fri, 01 Nov 2002 19:56:55 -0800 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> <3DC2E1FB.5050201@sun.com> <3DC2E611.3070406@sun.com> <3DC2EC80.5010702@sun.com> Message-ID: <3DC34D07.9020805@sun.com> Sigh. This isn't making life any easier trying to debug the "Archiver eats my machine" problem: self._open_index_file_as_stdout(arcdir, hdr) Any tricks for using pdb with a program that wants to steal stdout? (it's the first invocation of _update_simple_index, the one for the Date index, that takes all the memory/time; I suspect that's just because it's the first one, and builds a wad if in-core data structures that are then reused by the Subject and Author invocations that follow. But it's pathological, whatever it's doing. gc debugging shows a *wad* of objects stuck in generation 2 (i.e., not leaked, and referred to).) From Dale@Newfield.org Sat Nov 2 21:37:07 2002 From: Dale@Newfield.org (Dale Newfield) Date: Sat, 2 Nov 2002 16:37:07 -0500 (EST) Subject: [Mailman-Developers] Help programming MemberAdaptor... In-Reply-To: Message-ID: On Wed, 30 Oct 2002, Martin Whinnery wrote: > > Err, define "populate". Is this a one-time thing? Or do you want the > > list membership to always come from an LDAP lookup? > > The latter. I help run a large educational campus, and we hold all > accounts and groups in LDAP. These groups change membership over time, > and I want to associate mailing lists with some of them. What I don't > need is the headache of remembering to keep the memberships in sync. FYI, This is precisely what's taking the SQL MemberAdaptor so long (besides all my other commitments :-). The designincludes not only normal mailing lists, but also the ability to set up meta-mailing lists. The idea is that there is exactly one "course" mailing list, but each individual course "art-101" is a separate topic for which people have separate subscriptions. That way the creation of additional courses in the DB automatically translates to the creation of additional mailing lists ("course+art-102@birmc.ac.uk", "course+cs-550@birmc.ac.uk", etc.). It is configurable per list whether or not someone can subscribe to "nonMatchingTopics". -Dale From joshuae@bitmine.net Mon Nov 4 02:44:54 2002 From: joshuae@bitmine.net (Joshua Eichen) Date: Sun, 3 Nov 2002 18:44:54 -0800 Subject: [Mailman-Developers] Consistent Capitalization Message-ID: <20021104024454.GA9809@bitmine.net> ---------------------- multipart/mixed attachment The first letter of the second word for the Configuration Categories should= be lowercase and is in most cases. Attached is a patch to change the few=20 Categories where the first letter of the second word was uppercase. This will break the translation of the phrases until the tokens are changed. Joshua Eichen --=20 Bury my heart at Betrand Russellstraat. keyserver: seattle.keyserver.net fingerprint: 363E D1F4 8EC0 DDE3 5DC1 056F E8ED 5163 EE1B 2333 ---------------------- multipart/mixed attachment --- Mailman/Gui/Archive.py.orig Sun Nov 3 16:56:07 2002 +++ Mailman/Gui/Archive.py Sun Nov 3 16:56:21 2002 @@ -22,7 +22,7 @@ =0C class Archive(GUIBase): def GetConfigCategory(self): - return 'archive', _('Archiving Options') + return 'archive', _('Archiving options') =20 def GetConfigInfo(self, mlist, category, subcat=3DNone): if category <> 'archive': --- Mailman/Gui/General.py.orig Sun Nov 3 16:51:16 2002 +++ Mailman/Gui/General.py Sun Nov 3 16:55:36 2002 @@ -29,7 +29,7 @@ =0C class General(GUIBase): def GetConfigCategory(self): - return 'general', _('General Options') + return 'general', _('General options') =20 def GetConfigInfo(self, mlist, category, subcat): if category <> 'general': --- Mailman/Gui/Membership.py.orig Sun Nov 3 17:49:14 2002 +++ Mailman/Gui/Membership.py Sun Nov 3 18:09:33 2002 @@ -23,12 +23,12 @@ =0C class Membership: def GetConfigCategory(self): - return 'members', _('Membership Management') + return 'members', _('Membership management') =20 def GetConfigSubCategories(self, category): if category =3D=3D 'members': - return [('list', _('Membership List')), - ('add', _('Mass Subscription')), - ('remove', _('Mass Removal')), + return [('list', _('Membership list')), + ('add', _('Mass subscription')), + ('remove', _('Mass removal')), ] return None --- Mailman/Cgi/admin.py.orig Sun Nov 3 18:10:35 2002 +++ Mailman/Cgi/admin.py Sun Nov 3 18:10:56 2002 @@ -767,21 +767,21 @@ header =3D Table(width=3D"100%") # If we're in the list subcategory, show the membership list if subcat =3D=3D 'add': + header.AddRow([Center(Header(2, _('Mass subscriptions')))]) - header.AddRow([Center(Header(2, _('Mass Subscriptions')))]) header.AddCellInfo(header.GetCurrentRowIndex(), 0, colspan=3D2, bgcolor=3Dmm_cfg.WEB_HEADER_COLOR) container.AddItem(header) mass_subscribe(mlist, container) return container if subcat =3D=3D 'remove': + header.AddRow([Center(Header(2, _('Mass removals')))]) - header.AddRow([Center(Header(2, _('Mass Removals')))]) header.AddCellInfo(header.GetCurrentRowIndex(), 0, colspan=3D2, bgcolor=3Dmm_cfg.WEB_HEADER_COLOR) container.AddItem(header) mass_remove(mlist, container) return container # Otherwise... + header.AddRow([Center(Header(2, _('Membership list')))]) - header.AddRow([Center(Header(2, _('Membership List')))]) header.AddCellInfo(header.GetCurrentRowIndex(), 0, colspan=3D2, bgcolor=3Dmm_cfg.WEB_HEADER_COLOR) container.AddItem(header) ---------------------- multipart/mixed attachment-- From che@debian.org Mon Nov 4 06:21:02 2002 From: che@debian.org (Ben Gertzfield) Date: Sun, 03 Nov 2002 22:21:02 -0800 Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install Message-ID: <3DC611CE.3030804@debian.org> Barry, Using 2.1b4, my friend ran into an issue where everything in /usr/local/mailman/pythonlib was installed with no group or other permissions; his umask was 077, but bin/check_perms doesn't seem to check the permissions of /usr/local/mailman/pythonlib. So everything seemed fine until he tried to go to the admin web interface, which got a traceback. Basically, since /usr/local/mailman/pythonlib's contents were 600 (700 for directories), scripts/driver's import of paths.py failed when paths.py tried to do 'import japanese' from the non-readable /usr/local/mailman/pythonlib. Could we change the makefile and/or check_perms to ensure that all files in mailman/pythonlib are mode 0644, and all directories are 0755? Let me know if you need more information, it should be pretty easy. Ben From chuqui@plaidworks.com Mon Nov 4 07:44:00 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sun, 3 Nov 2002 23:44:00 -0800 Subject: [Mailman-Developers] CVS glitch. In-Reply-To: <15810.37812.33652.892873@gargle.gargle.HOWL> Message-ID: <2EBF4699-EFC9-11D6-BCBC-0003934516A8@plaidworks.com> On Friday, November 1, 2002, at 06:46 AM, Barry A. Warsaw wrote: > So I still want to know why Chuq finds it necessary to include the -A > flag. Chuq, does your CVS directory have a Tag file in it? > Nope. can't find one anywhere in the source structure. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ The Cliff's Notes Cliff's Notes on Hamlet: And they all died happily ever after From Jost.Krieger+mailman@rub.de Mon Nov 4 12:16:34 2002 From: Jost.Krieger+mailman@rub.de (Jost Krieger) Date: Mon, 4 Nov 2002 13:16:34 +0100 Subject: [Mailman-Developers] Privacy problems with UserNotification Message-ID: <20021104121634.GW8908@ruhr-uni-bochum.de> We are converting a few lists to Mailman 2.1b3 and used add_members with the "-c" flag. It turns out add_members uses UserNotification to send out the "big changes" message and UserNotification puts all the recipients into the To: header. As this was for an "adminstrator only" roster, not a good idea. I have no idea where else this could happen. If nowhere else, a loop in add_members might be enough. Jost -- | Jost.Krieger+sig@ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine am RZ der RUB | | Pluralitas non est ponenda sine necessitate | | William of Ockham (1285-1347/49) | From Dale@Newfield.org Mon Nov 4 15:06:52 2002 From: Dale@Newfield.org (Dale Newfield) Date: Mon, 4 Nov 2002 10:06:52 -0500 (EST) Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install In-Reply-To: <3DC611CE.3030804@debian.org> Message-ID: On Sun, 3 Nov 2002, Ben Gertzfield wrote: > Could we change the makefile and/or check_perms to ensure that all files > in mailman/pythonlib are mode 0644, and all directories are 0755? I've been testing the current CVS on an OSX box running Postfix, and while I've had very few problems, yet, one thing I did notice it that the check_perms script insists on looking at/changing *everything* under $prefix, rather than just those files needed by the installation. For me that meant it wanted to change the permissions on all the source code, too. That seems silly. -Dale From barry@python.org Mon Nov 4 15:51:45 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 10:51:45 -0500 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> <3DC2E1FB.5050201@sun.com> <3DC2E611.3070406@sun.com> <3DC2EC80.5010702@sun.com> <3DC34D07.9020805@sun.com> Message-ID: <15814.38801.227005.537645@gargle.gargle.HOWL> Dan found what is probably the majority of the problem. In the i18n patch, Article instances in HyperArch.py grew an _mlist instance so that means a unique instance of the MailList is pickled and unpickled in every Article in the archive. Ug. I'm working on a fix for that and will see about the template instantiations, but I suspect it's the former that's contributing the bulk of the overhead. Thanks Dan, and everyone else. Keep an eye on cvs... -Barry From gward@python.net Mon Nov 4 16:43:46 2002 From: gward@python.net (Greg Ward) Date: Mon, 4 Nov 2002 11:43:46 -0500 Subject: [Mailman-Developers] More extend.py questions In-Reply-To: References: <20021030181656.GD5220@cthulhu.gerg.ca> Message-ID: <20021104164346.GA1998@cthulhu.gerg.ca> On 30 October 2002, Martin Whinnery said: > And I quote (From NEWS 2.36) > ... > - List Extensibility > o A framework has been added which can be used to specialize > and extend specific mailing lists. If there is a file > called lists//extend.py, it is execfile()'d after > the MailList object is instantiated. The file should > contain a function extend() which will be called with the > MailList instance... > " [...] > def extend(mlist): > mlist = LDAPMailList(mlist) > mlist.__memberadaptor = LDAPMemberships(mlist) > > ----- snip ---------- It's pretty clear to me that you don't really understand how Python passes function parameters around; you definitely need to go do some homework. Although it's a bit out-of-date, I recommend *Learning Python* by Mark Lutz and David Ascher. It worked for me. > Now, what I want is for the Load() and Save() functions defined in > MailList.py to be overridden for this list with my own versions. Right, the rest of your code makes sense. The problem is that by the time Mailman passes the mlist object to your extend() function, it has already instantiated MailList to create mlist. You *might* be able to get away with a noxious and vile hack like this: def extend(mlist): mlist.__class__ = LDAPMailList but don't tell anyone *I* said you could do that. Unfortunately, I don't know enough about Mailman's internals to tell you what the Right Way to do it is. Sorry. Greg -- Greg Ward http://www.gerg.ca/ I haven't lost my mind; I know exactly where I left it. From chuqui@plaidworks.com Mon Nov 4 16:45:12 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Mon, 4 Nov 2002 08:45:12 -0800 Subject: [Mailman-Developers] 2.1b4+ evaluation order glitch. Message-ID: Barry -- looks like 2.1b4 is evaluating messages slightly out of order. If I get a large piece of spam (my message limit is 30K, the spam is, say, 60k), it gets held as too large, before the evaluation can take place that should reject it as being from a non-subscriber. Seems to me these evaluations ought to be reversed... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ He doesn't have ulcers, but he's a carrier. From Daniel.Buchmann@bibsys.no Mon Nov 4 17:34:53 2002 From: Daniel.Buchmann@bibsys.no (Daniel Buchmann) Date: 04 Nov 2002 18:34:53 +0100 Subject: [Mailman-Developers] 2.1b4+ evaluation order glitch. In-Reply-To: References: Message-ID: <1036431295.3459.7.camel@fornax.bibsys.no> ---------------------- multipart/signed attachment I'm also having a problem with the evaluation order. I have messages that get held for approval, even though they would've been auto-discarded by my sender filters. This is probably because I have "Must posts have list named in destination (to, cc) field" set to yes, which is probably evaluated before the sender filters... On Mon, 2002-11-04 at 17:45, Chuq Von Rospach wrote: >=20 > Barry -- >=20 > looks like 2.1b4 is evaluating messages slightly out of order. If I get=20 > a large piece of spam (my message limit is 30K, the spam is, say, 60k),=20 > it gets held as too large, before the evaluation can take place that=20 > should reject it as being from a non-subscriber. Seems to me these=20 > evaluations ought to be reversed... >=20 >=20 > --=20 > Chuq Von Rospach, Architech > chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ >=20 > He doesn't have ulcers, but he's a carrier. >=20 >=20 > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers >=20 >=20 ---------------------- multipart/signed attachment A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021104/ff58b0cf/attachment.bin ---------------------- multipart/signed attachment-- From barry@python.org Mon Nov 4 17:36:17 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 12:36:17 -0500 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> <3DC2E1FB.5050201@sun.com> <3DC2E611.3070406@sun.com> <3DC2EC80.5010702@sun.com> <3DC34D07.9020805@sun.com> Message-ID: <15814.45073.678975.472648@gargle.gargle.HOWL> Here's a patch that eliminates the MailList object from the article index pickle. It also undoes the incomplete hack in MailList for not pickling the lock object (that should have been a major clue). I've done some moderate testing of this patch, and I think it's safe, and probably fixes the majority of the problem. Please give it a shot. It doesn't optimize the loading of the template files -- that comes next. But I'll still bet you find a huge speed up. One outstanding issue: Depending on when you upgraded to 2.1b4 and when/if you regen'd your archives from scratch, your existing article indexes may have pickled MailList instances in them. These should get cleaned up the next time you archive an article, but only for the month (or other division) that the article is being added to. To clean up your entire archive, you'll need to zap the existing one and re-run bin/arch. If that's not acceptable to people, I'll write a little fixer program to fix *-article indices. Oh, and you'll find that not including the MailList object in your article indices can reduce their size by 10x or more. Nice little added benefit, eh? The braver of you can give this a shot, and after a little more testing, I'll check this into cvs. -Barry -------------------- snip snip -------------------- Index: Mailman/MailList.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/MailList.py,v retrieving revision 2.94 diff -u -r2.94 MailList.py --- Mailman/MailList.py 25 Oct 2002 21:10:45 -0000 2.94 +++ Mailman/MailList.py 4 Nov 2002 17:30:22 -0000 @@ -113,23 +113,6 @@ if func: func(self) - # Never pickle our lock object! We need both of these because MailLists - # get pickled by the archiver and this can cause ArchRunner to unlock - # lists at the wrong time. The real fix may be to not pickle MailList - # objects in the archiver, but that's too much work to verify at the - # moment. - LOCKATTR = '_MailList__lock' - - def __getstate__(self): - d = self.__dict__.copy() - del d[self.LOCKATTR] - return d - - def __setstate__(self, d): - if d.has_key(self.LOCKATTR): - del d[self.LOCKATTR] - self.__dict__ = d - def __getattr__(self, name): # Because we're using delegation, we want to be sure that attribute # access to a delegated member function gets passed to the Index: Mailman/Archiver/HyperArch.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v retrieving revision 2.22 diff -u -r2.22 HyperArch.py --- Mailman/Archiver/HyperArch.py 19 Oct 2002 20:59:27 -0000 2.22 +++ Mailman/Archiver/HyperArch.py 4 Nov 2002 17:30:23 -0000 @@ -33,11 +33,14 @@ import types import HyperDatabase import pipermail +import weakref from Mailman import mm_cfg from Mailman import Utils from Mailman import LockFile +from Mailman import MailList from Mailman import EncWord +from Mailman import Errors from Mailman import i18n from Mailman.Logging.Syslog import syslog from Mailman.Mailbox import ArchiverMailbox @@ -234,13 +237,45 @@ if self.charset and self.charset in mm_cfg.VERBATIM_ENCODING: self.quote = unicode_quote + # Mapping of listnames to MailList instances as a weak value dictionary. + _listcache = weakref.WeakValueDictionary() + + def _open_list(self, listname): + # Cache the open list so that any use of the list within this process + # uses the same object. We use a WeakValueDictionary so that when the + # list is no longer necessary, its memory is freed. + mlist = self._listcache.get(listname) + if not mlist: + try: + mlist = MailList.MailList(listname, lock=0) + except Errors.MMListError, e: + syslog('error', 'error opening list: %s\n%s', listname, e) + return None + else: + self._listcache[listname] = mlist + return mlist + + def __getstate__(self): + d = self.__dict__.copy() + # We definitely don't want to pickle the MailList instance, so just + # pickle a reference to it. + del d['_mlist'] + d['__listname'] = self._mlist.internal_name() + # Delete a few other things we don't want in the pickle + for attr in ('prev', 'next', 'body'): + del d[attr] + d['body'] = [] + return d + def __setstate__(self, d): # For loading older Articles via pickle. All this stuff was added # when Simone Piunni and Tokio Kikuchi i18n'ified Pipermail. See SF # patch #594771. self.__dict__ = d - if not d.has_key('_mlist'): - self._mlist = None + listname = d.get('__listname') + if listname: + del d['__listname'] + d['_mlist'] = self._open_list(listname) if not d.has_key('_lang'): if self._mlist is None: self._lang = mm_cfg.DEFAULT_SERVER_LANGUAGE @@ -471,18 +506,6 @@ if line.strip() == '': break self.body.append(line) - - def __getstate__(self): - d={} - for each in self.__dict__.keys(): - if each == "quote": - continue - if each in ['maillist','prev','next','body']: - d[each] = None - else: - d[each] = self.__dict__[each] - d['body']=[] - return d Index: Mailman/Archiver/HyperDatabase.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperDatabase.py,v retrieving revision 2.4 diff -u -r2.4 HyperDatabase.py --- Mailman/Archiver/HyperDatabase.py 16 Mar 2002 06:57:36 -0000 2.4 +++ Mailman/Archiver/HyperDatabase.py 4 Nov 2002 17:30:23 -0000 @@ -19,8 +19,6 @@ # import os import marshal -import string -import sys import time import errno @@ -51,11 +49,11 @@ objects. The object itself is stored using marshal. It would be much simpler, and probably faster, to store the actual objects in the DumbBTree and pickle it. - + TBD: Also needs a more sensible name, like IteratableDictionary or SortedDictionary. """ - + def __init__(self, path): self.current_index = 0 self.path = path @@ -65,7 +63,7 @@ self.dict = {} self.sorted = [] self.load() - + def __repr__(self): return "DumbBTree(%s)" % self.path @@ -74,7 +72,7 @@ self.sorted = self.dict.keys() self.sorted.sort() self.__dirty = 0 - + def lock(self): self.lockfile.lock() @@ -83,28 +81,28 @@ self.lockfile.unlock() except LockFile.NotLockedError: pass - + def __delitem__(self, item): # if first hasn't been called, we can skip the sort if self.current_index == 0: del self.dict[item] self.__dirty = 1 return - try: - ci = self.sorted[self.current_index] - except IndexError: - ci = None - if ci == item: - try: - ci = self.sorted[self.current_index + 1] - except IndexError: - ci = None - del self.dict[item] + try: + ci = self.sorted[self.current_index] + except IndexError: + ci = None + if ci == item: + try: + ci = self.sorted[self.current_index + 1] + except IndexError: + ci = None + del self.dict[item] self.__sort(dirty=1) - if ci is not None: - self.current_index = self.sorted.index(ci) - else: - self.current_index = self.current_index + 1 + if ci is not None: + self.current_index = self.sorted.index(ci) + else: + self.current_index = self.current_index + 1 def clear(self): # bulk clearing much faster than deleting each item, esp. with the @@ -118,22 +116,22 @@ else: key = self.sorted[0] self.current_index = 1 - return key, self.dict[key] + return key, self.dict[key] def last(self): if not self.sorted: raise KeyError else: key = self.sorted[-1] - self.current_index = len(self.sorted) - 1 + self.current_index = len(self.sorted) - 1 return key, self.dict[key] - + def next(self): try: key = self.sorted[self.current_index] except IndexError: raise KeyError - self.current_index = self.current_index + 1 + self.current_index = self.current_index + 1 return key, self.dict[key] def has_key(self, key): @@ -154,10 +152,10 @@ self.dict[item] = val self.__dirty = 1 return - try: - current_item = self.sorted[self.current_index] - except IndexError: - current_item = item + try: + current_item = self.sorted[self.current_index] + except IndexError: + current_item = item self.dict[item] = val self.__sort(dirty=1) self.current_index = self.sorted.index(current_item) @@ -198,48 +196,48 @@ # class HyperDatabase(pipermail.Database): __super_addArticle = pipermail.Database.addArticle - + def __init__(self, basedir): self.__cache = {} - self.__currentOpenArchive = None # The currently open indices - self.basedir = os.path.expanduser(basedir) + self.__currentOpenArchive = None # The currently open indices + self.basedir = os.path.expanduser(basedir) # Recently added articles, indexed only by message ID self.changed={} def firstdate(self, archive): - self.__openIndices(archive) - date = 'None' - try: - datekey, msgid = self.dateIndex.first() - date = time.asctime(time.localtime(string.atof(datekey[0]))) - except KeyError: + self.__openIndices(archive) + date = 'None' + try: + datekey, msgid = self.dateIndex.first() + date = time.asctime(time.localtime(float(datekey[0]))) + except KeyError: pass - return date + return date def lastdate(self, archive): - self.__openIndices(archive) - date = 'None' - try: - datekey, msgid = self.dateIndex.last() - date = time.asctime(time.localtime(string.atof(datekey[0]))) - except KeyError: + self.__openIndices(archive) + date = 'None' + try: + datekey, msgid = self.dateIndex.last() + date = time.asctime(time.localtime(float(datekey[0]))) + except KeyError: pass - return date + return date def numArticles(self, archive): - self.__openIndices(archive) - return len(self.dateIndex) + self.__openIndices(archive) + return len(self.dateIndex) def addArticle(self, archive, article, subject=None, author=None, date=None): - self.__openIndices(archive) + self.__openIndices(archive) self.__super_addArticle(archive, article, subject, author, date) def __openIndices(self, archive): - if self.__currentOpenArchive == archive: + if self.__currentOpenArchive == archive: return - self.__closeIndices() - arcdir = os.path.join(self.basedir, 'database') + self.__closeIndices() + arcdir = os.path.join(self.basedir, 'database') omask = os.umask(0) try: try: @@ -248,38 +246,38 @@ if e.errno <> errno.EEXIST: raise finally: os.umask(omask) - for i in ('date', 'author', 'subject', 'article', 'thread'): - t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) - setattr(self, i + 'Index', t) - self.__currentOpenArchive = archive + for i in ('date', 'author', 'subject', 'article', 'thread'): + t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) + setattr(self, i + 'Index', t) + self.__currentOpenArchive = archive def __closeIndices(self): - for i in ('date', 'author', 'subject', 'thread', 'article'): - attr = i + 'Index' - if hasattr(self, attr): - index = getattr(self, attr) - if i == 'article': - if not hasattr(self, 'archive_length'): + for i in ('date', 'author', 'subject', 'thread', 'article'): + attr = i + 'Index' + if hasattr(self, attr): + index = getattr(self, attr) + if i == 'article': + if not hasattr(self, 'archive_length'): self.archive_length = {} l = len(index) self.archive_length[self.__currentOpenArchive] = l - index.close() - delattr(self, attr) - self.__currentOpenArchive = None - + index.close() + delattr(self, attr) + self.__currentOpenArchive = None + def close(self): - self.__closeIndices() - - def hasArticle(self, archive, msgid): - self.__openIndices(archive) - return self.articleIndex.has_key(msgid) - + self.__closeIndices() + + def hasArticle(self, archive, msgid): + self.__openIndices(archive) + return self.articleIndex.has_key(msgid) + def setThreadKey(self, archive, key, msgid): - self.__openIndices(archive) - self.threadIndex[key]=msgid - + self.__openIndices(archive) + self.threadIndex[key]=msgid + def getArticle(self, archive, msgid): - self.__openIndices(archive) + self.__openIndices(archive) if not self.__cache.has_key(msgid): # get the pickled object out of the DumbBTree buf = self.articleIndex[msgid] @@ -288,50 +286,50 @@ article = self.__cache[msgid] return article - def first(self, archive, index): - self.__openIndices(archive) - index = getattr(self, index + 'Index') - try: - key, msgid = index.first() - return msgid - except KeyError: + def first(self, archive, index): + self.__openIndices(archive) + index = getattr(self, index + 'Index') + try: + key, msgid = index.first() + return msgid + except KeyError: return None - - def next(self, archive, index): - self.__openIndices(archive) - index = getattr(self, index + 'Index') - try: - key, msgid = index.next() - return msgid - except KeyError: + + def next(self, archive, index): + self.__openIndices(archive) + index = getattr(self, index + 'Index') + try: + key, msgid = index.next() + return msgid + except KeyError: return None - + def getOldestArticle(self, archive, subject): - self.__openIndices(archive) - subject=string.lower(subject) - try: - key, tempid=self.subjectIndex.set_location(subject) - self.subjectIndex.next() - [subject2, date]= string.split(key, '\0') - if subject!=subject2: return None - return tempid - except KeyError: - return None + self.__openIndices(archive) + subject = subject.lower() + try: + key, tempid=self.subjectIndex.set_location(subject) + self.subjectIndex.next() + [subject2, date]= key.split('\0') + if subject!=subject2: return None + return tempid + except KeyError: + return None def newArchive(self, archive): pass - + def clearIndex(self, archive, index): - self.__openIndices(archive) + self.__openIndices(archive) if hasattr(self.threadIndex, 'clear'): self.threadIndex.clear() return - finished=0 - try: - key, msgid=self.threadIndex.first() - except KeyError: finished=1 - while not finished: - del self.threadIndex[key] - try: - key, msgid=self.threadIndex.next() - except KeyError: finished=1 + finished=0 + try: + key, msgid=self.threadIndex.first() + except KeyError: finished=1 + while not finished: + del self.threadIndex[key] + try: + key, msgid=self.threadIndex.next() + except KeyError: finished=1 From barry@python.org Mon Nov 4 18:27:54 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 13:27:54 -0500 Subject: [Mailman-Developers] re: Much cpu/memory load References: <29390000.1036088198@modulus.oit.ucsb.edu> <000f01c2811d$f1e55b10$1e00a8c0@onsnet.org> <15809.40590.896001.764415@gargle.gargle.HOWL> <3DC1EF16.6070400@sun.com> <20021101101514.GB2899@ferrara.linux.it> <3DC2E1FB.5050201@sun.com> <3DC2E611.3070406@sun.com> <3DC2EC80.5010702@sun.com> <3DC34D07.9020805@sun.com> Message-ID: <15814.48170.638327.211872@gargle.gargle.HOWL> >>>>> "DM" == Dan Mick writes: DM> Sigh. This isn't making life any easier trying to debug the DM> "Archiver eats my machine" problem: DM> self._open_index_file_as_stdout(arcdir, hdr) DM> Any tricks for using pdb with a program that wants to steal DM> stdout? Rewrite the code so it doesn't steal stdout? ;) Really, this code should be rewritten to use more modern Pythonic style, such as def _open_index_file(self, archdir, index_name): # ... # remove the sys.stdout hackery and then any place that does "print something_useful" should get rewritten as "print >> self.__f, something_useful". I don't have time for that, but I'd accept a patch. -Barry From barry@python.org Mon Nov 4 21:33:05 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 16:33:05 -0500 Subject: [Mailman-Developers] 2.1b4+ evaluation order glitch. References: Message-ID: <15814.59281.873094.676853@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> Barry -- CVR> looks like 2.1b4 is evaluating messages slightly out of CVR> order. If I get a large piece of spam (my message limit is CVR> 30K, the spam is, say, 60k), it gets held as too large, CVR> before the evaluation can take place that should reject it as CVR> being from a non-subscriber. Seems to me these evaluations CVR> ought to be reversed... Here's a cvs log entry for Defaults.py.in: ---------------------------- revision 2.102 date: 2002/08/23 19:56:08; author: bwarsaw; state: Exp; lines: +1 -1 GLOBAL_PIPELINE: Reordering the modules so that Hold comes before Moderate. ---------------------------- so I definitely had a reason for doing this, but now I can't remember exactly what that was. :/ I'm willing to change it back, but I suspect there will be other glitches and my reason will become obvious again. Note that you don't have to wait for me -- you can re-order GLOBAL_PIPELINE in your mm_cfg.py file and see if 'Moderate' before 'Hold' is more satisfying. In the longer term I think we'll need to reorganize how holds are put on messages. I'd like to see Hold.py and Moderate.py simply tag the messages with hold criteria, and then there would be a separate configuration for the precedence of criteria. And in the admindb page, you'd get to see all the reasons why a message is being held. If we do it right, it should be better than the current "first hit wins" rules. But this is just musing for post-MM2.1. -Barry From barry@python.org Mon Nov 4 21:50:10 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 16:50:10 -0500 Subject: [Mailman-Developers] More extend.py questions References: <005c01c28035$99df5e90$c805010a@MARTLAPIBM> Message-ID: <15814.60306.24849.981526@gargle.gargle.HOWL> >>>>> "MW" == Martin Whinnery writes: MW> Please indulge a python virgin. Barry has advised someone to MW> 'overload the Load & Save function' in extend.py . Would MW> someone help me with a little sample? It doesn't need to do MW> anything useful, just replace the original function. Understand that this stuff is a kludge that should make /some/ radical customization of Mailman easier. The specific use case I had in mind was the ability to create different MemberAdaptor implementations, which I think is pretty close to what you're trying to do. Note that you may or may not need to overload MailList.Load() and MailList.Save() unless you also want to customize how list attributes are stored. If all you care about is getting member information out of LDAP, you might only need to set the MailList object's _memberadaptor attribute to something other than an OldStyleMemberships instance. --------- My efforts so far ------------- # /usr/local/mailman/lists/ldaplist/extend.py def extend(mlist): mlist.OldSave = mlist.Save def MySave(self): print "WOOKIE" # So I can see it in withlist mlist.__class__.Save(self) mlist.Save = MySave -------- snip snip ---------------------- I think this is pretty close to what I had in mind, although I'm not sure why you want to call the original Save function in MySave(), and why you wouldn't just call mlist.OldSave() if you really wanted to do that. But when I try m.Save(m) from within "withlist ldaplist", I get a 'NotLocked' error: NotLockedError: : None Did you use the -l option to withlist? Or did you explicit call m.Lock()? If not, getting this exception probably has little to do with extend.py (the list has to be locked in order to Save it). But as I said, I'm not sure you'll need to override Load() and Save() -- unless you're going to allow the writeable methods in the MemberAdaptor interface to be called through Mailman. You'll definitely want to write an implementation of MemberAdaptor that gets its data through LDAP, and then in your extend.py file, do something like -------------------- snip snip -------------------- # extend.py def extend(mlist): # You might want to key off of something other than the list's # internal name. listid = mlist.internal_name() # Get all member info from LDAP mlist._memberadaptor = LDAPMemberAdaptor(listid) -------------------- snip snip -------------------- HTH, -Barry From barry@python.org Mon Nov 4 23:51:57 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 18:51:57 -0500 Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install References: <3DC611CE.3030804@debian.org> Message-ID: <15815.2077.903232.369124@gargle.gargle.HOWL> >>>>> "BG" == Ben Gertzfield writes: BG> Could we change the makefile and/or check_perms to ensure that BG> all files in mailman/pythonlib are mode 0644, and all BG> directories are 0755? Here's a Makefile.in patch that should do the trick. I'll work out a check_perms fix next. -Barry -------------------- snip snip -------------------- Index: Makefile.in =================================================================== RCS file: /cvsroot/mailman/mailman/misc/Makefile.in,v retrieving revision 2.28 diff -u -r2.28 Makefile.in --- Makefile.in 14 Oct 2002 22:21:09 -0000 2.28 +++ Makefile.in 4 Nov 2002 23:51:47 -0000 @@ -87,7 +87,7 @@ for p in $(PACKAGES); \ do \ gunzip -c $$p.tar.gz | tar xf -; \ - (cd $$p ; PYTHONPATH=$(PYTHONLIBDIR) $(PYTHON) $(SETUPCMD)); \ + (cd $$p ; umask 022 ; PYTHONPATH=$(PYTHONLIBDIR) $(PYTHON) $(SETUPCMD)); \ done finish: From barry@python.org Tue Nov 5 00:05:12 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 19:05:12 -0500 Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install References: <3DC611CE.3030804@debian.org> <15815.2077.903232.369124@gargle.gargle.HOWL> Message-ID: <15815.2872.644655.823643@gargle.gargle.HOWL> >>>>> "BAW" == Barry A Warsaw writes: BAW> Here's a Makefile.in patch that should do the trick. I'll BAW> work out a check_perms fix next. On second thought, we'll umask 002. -Barry From che@debian.org Tue Nov 5 00:08:40 2002 From: che@debian.org (Ben Gertzfield) Date: Mon, 04 Nov 2002 16:08:40 -0800 Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install In-Reply-To: <3DC611CE.3030804@debian.org> References: <3DC611CE.3030804@debian.org> <15815.2077.903232.369124@gargle.gargle.HOWL> Message-ID: <3DC70C08.70702@debian.org> Barry A. Warsaw wrote: >Here's a Makefile.in patch that should do the trick. I'll work out a >check_perms fix next. > > Barry, the change seems okay, but there may be a more fundamental, simpler problem we haven't addressed -- the user may not be aware of how critically important it is to run bin/check_perms first thing before even starting mailmanctl! Maybe we can just put a message at the end of make install that says in BIG CAPITAL LETTERS to definitely run bin/check_perms as root. Ben From terri@zone12.com Tue Nov 5 00:27:30 2002 From: terri@zone12.com (Terri Oda) Date: Mon, 4 Nov 2002 19:27:30 -0500 Subject: [Mailman-Developers] 2.1b4+ evaluation order glitch. In-Reply-To: <15814.59281.873094.676853@gargle.gargle.HOWL> References: <15814.59281.873094.676853@gargle.gargle.HOWL> Message-ID: <20021105002730.GA704@ostraya.zone12.com> > In the longer term I think we'll need to reorganize how holds are put > on messages. I'd like to see Hold.py and Moderate.py simply tag the > messages with hold criteria, and then there would be a separate > configuration for the precedence of criteria. And in the admindb > page, you'd get to see all the reasons why a message is being held. > If we do it right, it should be better than the current "first hit > wins" rules. Ohoh, having *all* the reasons is something my list admins ask me for every once in a while. I think I've gotten them all trained to read the message and figure it out themselves, though, so we can wait 'till post 2.1 :) Might be interesting to set it up with rankings a la spamassassin and have it autoreject instead of sending if the message fits a whole lot of criteria. (eg: a big attachment by a non-subscriber tends to be a copy of Klez.) Terri From barry@python.org Tue Nov 5 01:53:50 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 20:53:50 -0500 Subject: [Mailman-Developers] 2.1b4+ evaluation order glitch. References: <15814.59281.873094.676853@gargle.gargle.HOWL> <20021105002730.GA704@ostraya.zone12.com> Message-ID: <15815.9390.846650.48840@gargle.gargle.HOWL> >>>>> "TO" == Terri Oda writes: TO> Might be interesting to set it up with rankings a la TO> spamassassin and have it autoreject instead of sending if the TO> message fits a whole lot of criteria. (eg: a big attachment TO> by a non-subscriber tends to be a copy of Klez.) That's a very interesting idea! -Barry From barry@python.org Tue Nov 5 03:05:10 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 22:05:10 -0500 Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install References: <3DC611CE.3030804@debian.org> <15815.2077.903232.369124@gargle.gargle.HOWL> <3DC70C08.70702@debian.org> Message-ID: <15815.13670.747432.404403@gargle.gargle.HOWL> >>>>> "BG" == Ben Gertzfield writes: >> Here's a Makefile.in patch that should do the trick. I'll work >> out a check_perms fix next. BG> Barry, the change seems okay, but there may be a more BG> fundamental, simpler problem we haven't addressed -- the user BG> may not be aware of how critically important it is to run BG> bin/check_perms first thing before even starting mailmanctl! BG> Maybe we can just put a message at the end of make install BG> that says in BIG CAPITAL LETTERS to definitely run BG> bin/check_perms as root. Is it really necessary to do more advertising for check_perms? It's in the README, and FAQ, and all over the mailing list. ;) -Barry From noreply@sourceforge.net Tue Nov 5 03:59:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 04 Nov 2002 19:59:41 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-633618 ] checkdbs fails with error Message-ID: Bugs item #633618, was opened at 2002-11-04 19:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=633618&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs fails with error Initial Comment: Installed 2.1b4. Running checkdbs results in an error: [root@mail mailman]# /usr/bin/python2 -S /usr/share/mailman/ cron/checkdbs Traceback (most recent call last): File "/usr/share/mailman/cron/checkdbs", line 26, in ? from email.Charset import Charset ImportError: No module named email.Charset This means that the admin does not get daily reminders of pending admin requests, either. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=633618&group_id=103 From che@debian.org Tue Nov 5 06:31:59 2002 From: che@debian.org (Ben Gertzfield) Date: Mon, 04 Nov 2002 22:31:59 -0800 Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install In-Reply-To: <3DC611CE.3030804@debian.org> References: <3DC611CE.3030804@debian.org> <15815.2077.903232.369124@gargle.gargle.HOWL> <3DC70C08.70702@debian.org> <15815.13670.747432.404403@gargle.gargle.HOWL> Message-ID: <3DC765DF.2010700@debian.org> Barry A. Warsaw wrote: >>>>>>"BG" == Ben Gertzfield writes: >>>>>> >>>>>> > > > BG> Maybe we can just put a message at the end of make install > BG> that says in BIG CAPITAL LETTERS to definitely run > BG> bin/check_perms as root. > >Is it really necessary to do more advertising for check_perms? It's >in the README, and FAQ, and all over the mailing list. ;) > > I honestly think your estimation of how many people read the documentation is highly overestimated ;) Could it really hurt to put a note at the end of make install -- something like 'You should now run $prefix/bin/check_perms to see if any files or directories just installed need permission fixes.' Ben From satyap@satya.virtualave.net Tue Nov 5 09:31:14 2002 From: satyap@satya.virtualave.net (Satya) Date: Tue, 5 Nov 2002 01:31:14 -0800 (PST) Subject: [Mailman-Developers] [2.1b4] /usr/local/mailman/pythonlib has wrong permissions after make install In-Reply-To: <3DC765DF.2010700@debian.org> Message-ID: On Nov 4, 2002 at 22:31, Ben Gertzfield wrote: >I honestly think your estimation of how many people read the >documentation is highly overestimated ;) What do they think the documentation is for, inflating the tarball size? But, yeah, I don't read docs either, until there's a problem. No excuse for not skimming through the READMEs and INSTALLs, though. >Could it really hurt to put a note at the end of make install -- >something like 'You should now run $prefix/bin/check_perms to see if any >files or directories just installed need permission fixes.' You might as well cat out manual.txt, then, because if it's not check_install it's crontab. Or --with[cgi|mail]-gid. Or aliases. No, perhaps a note at the end of make install saying 'Read the README. Really. We mean it." would have the same effect. -- Satya. Pound forehead on keyboard to continue. From loewis@informatik.hu-berlin.de Tue Nov 5 13:42:38 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: Tue, 5 Nov 2002 14:42:38 +0100 (CET) Subject: [Mailman-Developers] Archiving multipart/alternative messages Message-ID: <200211051342.gA5DgclS003471@paros.informatik.hu-berlin.de> It appears that shawn's archiving problems all originate from the processing of multipart/alternative messages in pipermail. For reference, please have a look at http://digitiy.com/posts/list1.mbox/list1.mbox and the corresponding message http://digitiy.com/posts/list1/2002-November/000000.html I would suggest that pipermail looks for a text-plain part in the message, and tries to render that into HTML, ignoring all other parts. Regards, Martin From mburton@jo.birdsense.com Tue Nov 5 05:34:42 2002 From: mburton@jo.birdsense.com (Mike Burton) Date: Mon, 04 Nov 2002 21:34:42 -0800 Subject: [Mailman-Developers] Error??? Message-ID: <5.1.1.5.2.20021104212951.00b19138@10.10.10.1> Hi folks, Running Mailman 2.1b4 with Postfix on SuSE 8.0 here. Things were working fine for over a week and then I started getting "unpickling stack underflow" errors. Updated to the latest CVS files and the problem persists. Any clues would sure be greatly appreciated. Here's what I see after the update (approximately the same error as before the update. I didn't note it before, sorry): Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/listinfo.py", line 47, in main mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 101, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 587, in Load dict, e = self.__load(file) File "/usr/local/mailman/Mailman/MailList.py", line 560, in __load dict = loadfunc(fp) UnpicklingError: unpickling stack underflow Thanks in advance, MikeFrom sergio@behemot.it Tue Nov 5 02:00:02 2002 From: sergio@behemot.it (Sergio Perani) Date: Tue, 05 Nov 2002 03:00:02 +0100 Subject: [Mailman-Developers] An open source software for browsing and searching mails ordownloading attachments Message-ID: <3DC72622.7030700@behemot.it> I do not know if this is the right mailing list for this type of message, but I think it could be interesting for you. I would to present a preview of an open source software we are developing, which allows to: - browse mailing lists contents - download attachment - full-text search The preview, called Gabriel, can be downloaded at http://www.opheliadev.org/dist/Gabriel0.1.1.jar (11meg) In the near future we will add more functionalities: - specialized search engine (for instance look for the author of a word document in a attachment) - tight integration in the development environments Gabriel is a subproject of the larger Ophelia project, which studies how to improve the integration between tools into a distributed development environment. More information can be found at http://www.opheliadev.org, even if the site contents will be refreshed in the next weeks. I will appreciate if you could send some comments or add a link on your FAQ page. Thanks, Sergio Perani sergio@behemot.it From mss@mawhrin.net Tue Nov 5 15:30:32 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Tue, 5 Nov 2002 15:30:32 +0000 Subject: [Mailman-Developers] import errors Message-ID: <20021105153032.GA1726@mawhrin.net> ---------------------- multipart/signed attachment I just rebooted my computer (which worked for three months without any reboot). On it I have mailman 2.1b3+, which worked fine. Now I've got a lot of errors like this: Starting Mailman's master qrunner. Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Could somebody suggest what is wrong? Thanks -- Misha PS I'd like to avoid upgrade if possible, but it'd be better to do that _after_ I resolve this problem. ---------------------- multipart/signed attachment A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021105/29c97926/attachment.bin ---------------------- multipart/signed attachment-- From barry@python.org Tue Nov 5 16:26:40 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 5 Nov 2002 11:26:40 -0500 Subject: [Mailman-Developers] import errors References: <20021105153032.GA1726@mawhrin.net> Message-ID: <15815.61760.108530.197276@gargle.gargle.HOWL> >>>>> "MS" == Mikhail Sobolev writes: MS> I just rebooted my computer (which worked for three months MS> without any reboot). On it I have mailman 2.1b3+, which MS> worked fine. MS> Now I've got a lot of errors like this: | Starting Mailman's master qrunner. | Could not find platform independent libraries | Could not find platform dependent libraries | Consider setting $PYTHONHOME to [:] MS> Could somebody suggest what is wrong? These are errors coming from Python, so somehow your Python installation (or at least the one that Mailman was told to use) got corrupted. -Barry From mradamlacey@hotmail.com Tue Nov 5 17:06:37 2002 From: mradamlacey@hotmail.com (Adam Lacey) Date: Tue, 05 Nov 2002 11:06:37 -0600 Subject: [Mailman-Developers] getting mailman to see a new python install Message-ID: I am trying to get Mailman to "know" that I have a different version of python for it to use to run its scripts. Specifically I compiled in the MySQLdb into python 2.2 and want Mailman to be able to import that module... I can run /usr/bin/python and "import MySQLdb" just fine, but when i add that line of code into any Mailman python class it tells me that it cant import it. So do I need to reinstall mailman with a different configure option to "see" my new version of python? ( dont remember if used that option when installed mailman 2.0) I just used a python2.2.1 rpm to install python by the way. Also, should I just upgrade to mailman 2.1 or the newest release? thanks _________________________________________________________________ Unlimited Internet access -- and 2 months free!  Try MSN. http://resourcecenter.msn.com/access/plans/2monthsfree.asp From noreply@sourceforge.net Tue Nov 5 17:14:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 05 Nov 2002 09:14:58 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-633618 ] checkdbs fails with error Message-ID: Bugs item #633618, was opened at 2002-11-04 22:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=633618&group_id=103 Category: command line scripts Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs fails with error Initial Comment: Installed 2.1b4. Running checkdbs results in an error: [root@mail mailman]# /usr/bin/python2 -S /usr/share/mailman/ cron/checkdbs Traceback (most recent call last): File "/usr/share/mailman/cron/checkdbs", line 26, in ? from email.Charset import Charset ImportError: No module named email.Charset This means that the admin does not get daily reminders of pending admin requests, either. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-05 12:14 Message: Logged In: YES user_id=12800 This is fixed in CVS and will be fixed in 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=633618&group_id=103 From barry@python.org Tue Nov 5 17:31:08 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 5 Nov 2002 12:31:08 -0500 Subject: [Mailman-Developers] getting mailman to see a new python install References: Message-ID: <15816.92.47284.101818@gargle.gargle.HOWL> >>>>> "AL" == Adam Lacey writes: AL> I am trying to get Mailman to "know" that I have a different AL> version of python for it to use to run its scripts. ./configure --with-python=/path/to/python -Barry From mss@mawhrin.net Tue Nov 5 19:47:23 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Tue, 5 Nov 2002 19:47:23 +0000 Subject: [Mailman-Developers] import errors In-Reply-To: <15815.61760.108530.197276@gargle.gargle.HOWL> References: <20021105153032.GA1726@mawhrin.net> <15815.61760.108530.197276@gargle.gargle.HOWL> Message-ID: <20021105194722.GA2861@mawhrin.net> ---------------------- multipart/signed attachment On Tue, Nov 05, 2002 at 11:26:40AM -0500, Barry A. Warsaw wrote: > >>>>> "MS" =3D=3D Mikhail Sobolev writes: >=20 > MS> I just rebooted my computer (which worked for three months > MS> without any reboot). On it I have mailman 2.1b3+, which > MS> worked fine. >=20 > MS> Now I've got a lot of errors like this: >=20 > | Starting Mailman's master qrunner. > | Could not find platform independent libraries > | Could not find platform dependent libraries > | Consider setting $PYTHONHOME to [:] >=20 > MS> Could somebody suggest what is wrong? > These are errors coming from Python, so somehow your Python > installation (or at least the one that Mailman was told to use) got > corrupted. Do you have any hints on how to determine what exactly is wrong? I do not want to just re-install mailman (as python seems to be ok) to "fix" it. -- Misha ---------------------- multipart/signed attachment A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021105/d92b6488/attachment.bin ---------------------- multipart/signed attachment-- From noreply@sourceforge.net Tue Nov 5 20:25:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 05 Nov 2002 12:25:46 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634026 ] Spurious option text on subscription GUI Message-ID: Bugs item #634026, was opened at 2002-11-05 15:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634026&group_id=103 Category: Web/CGI Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Spurious option text on subscription GUI Initial Comment: Mailman version 2.0.13 Nondigest option: nondigestable = 1 Subscription Page with option text without radio button confuses subscriber. Would you like to receive list mail batched in a daily digest? No Yes ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634026&group_id=103 From noreply@sourceforge.net Tue Nov 5 22:20:15 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 05 Nov 2002 14:20:15 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634109 ] Decode text parts in multipart messages Message-ID: Patches item #634109, was opened at 2002-11-05 23:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634109&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Decode text parts in multipart messages Initial Comment: This patch improves the processing in multipart messages, in particular multipart/alternative. It does so by concatenating all text/plain parts after scrubbing (scrubbing should only leave text/plain parts), and replacing the type of the original multipart message with text/plain. Concatenation of the text parts tries to recode everything into the "main" encoding, which is the encoding of the text/plain part. This could be improved by recoding everything to UTF-8 if switching the main encoding to UTF-8 if some part cannot be recoded to the main encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634109&group_id=103 From spacey-mailman@lenin.nu Wed Nov 6 05:33:20 2002 From: spacey-mailman@lenin.nu (Peter C. Norton) Date: Tue, 5 Nov 2002 21:33:20 -0800 Subject: [Mailman-Developers] Problem with my auto-bounce patch for 2.0.8 in 2.0.13 Message-ID: <20021106053318.GC8849@lenin.nu> I applied the auto-bounce hack I created for 2.0.8 to 2.0.13, and the patch applied cleanly and the install went fine. However, I've created a bug in the privacy options page. For some reason, changes I made to the MailList class in MailList.py (adding the attribute self.auto_reject_nonmembers) isn't reflected in the HandlerAPI.py call to do_pipeline(mlist, msg, msgdata). Here's the message from the error log: Nov 06 00:27:02 2002 (23713) Delivery exception: auto_reject_nonmembers Nov 06 00:27:02 2002 (23713) Traceback (innermost last): File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/Hold.py", line 152, in process if mlist.auto_reject_nonmembers: AttributeError: auto_reject_nonmembers I'm not sure what a Delivery exception is caused by, but I'm inferring from the AttributeError that it can't find mlist.auto_reject_nonmembers. how cna this be? Is there somewhere else besides MailList.py where MailList objects are created? Or is there somewhere special that HandlerAPI.py or Hold.py is doing? Help? I can't suppress obnoxios posters for now, and the prospect of having to moderate posts from non-members is too horrible to contempate. -Peter -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. From noreply@sourceforge.net Wed Nov 6 06:34:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 05 Nov 2002 22:34:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634274 ] Some digest seems to have a wrong Message-ID: Bugs item #634274, was opened at 2002-11-06 06:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: divine rites (divinerites) Assigned to: Nobody/Anonymous (nobody) Summary: Some digest seems to have a wrong Initial Comment: Some Zope digests looks ugly with Evolution. Some digests on some lists are concerned. Not predictable. Digest should look like all normal ones (like for all digests who works fine in evolution) This link give the whole explanation for the digest problem from the evolution point of view. It seems that the mail has some wrong type. http://bugzilla.ximian.com/show_bug.cgi?id=33282 I don't know what Mailman version it is but i guess zope lists use a brand new mailman ;-)) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_id=103 From noreply@sourceforge.net Wed Nov 6 08:28:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 06 Nov 2002 00:28:00 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634303 ] Recode pipermail templates Message-ID: Patches item #634303, was opened at 2002-11-06 09:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Recode pipermail templates Initial Comment: This patch transparently recodes the pipermail templates and messages if the article and index files have a different encoding than the template language If necessary, HTML character references are generate. If recoding fails, it will proceed without exception, but produce garbage. For messages, this uses a method self._, which first invokes _, then does the recoding. This makes it necessary for _ to go back more than one frame, so the number of frames is now an optional parameter (defaulting to 1). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 From rommel@suse.de Wed Nov 6 11:37:26 2002 From: rommel@suse.de (Heiko Rommel) Date: Wed, 6 Nov 2002 12:37:26 +0100 (CET) Subject: [Mailman-Developers] re-import bug in 2.1b4+ (CVS from Tuesday) Message-ID: Hi, re-importing a list's configuration seems to change the subscribe_policy. config_list -o /tmp/old mylist config_list -i /tmp/old mylist config_list -o /tmp/new mylist diff /tmp/new /tmp/old 2c2 < ## captured on Wed Nov 6 11:23:11 2002 --- > ## captured on Wed Nov 6 11:13:17 2002 263c263 < new_member_options = 0 --- > new_member_options = 256 560c560 < subscribe_policy = 3 --- > subscribe_policy = 2 Is this a bug or feature ? Heiko Rommel phone +49-911-740 53 696 SuSE Linux AG fax +49-911-741 77 55 Deutschherrnstr. 15-19 mail rommel@suse.de 90429 Nuernberg www http://www.suse.de/ Germany From danny@terweij.nl Wed Nov 6 13:00:18 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 6 Nov 2002 14:00:18 +0100 Subject: [Mailman-Developers] Typo Message-ID: <015801c28594$7518aa80$1e00a8c0@onsnet.org> Hi, At : http://domain/mailman/admin/list/?VARHELP=nondigest/personalize There is a typo at : ******* These additional substitution variables will be available for your headers and footers, when this feature is enabled: user_address - The address of the user, coerced to lower case. ******** I do not know the word "coerced", should this not be the word "forced" ? Danny Terweij. From barry@python.org Wed Nov 6 13:07:37 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 6 Nov 2002 08:07:37 -0500 Subject: [Mailman-Developers] Problem with my auto-bounce patch for 2.0.8 in 2.0.13 References: <20021106053318.GC8849@lenin.nu> Message-ID: <15817.5145.200744.86446@gargle.gargle.HOWL> >>>>> "PCN" == Peter C Norton writes: PCN> However, I've created a bug in the privacy options page. For PCN> some reason, changes I made to the MailList class in PCN> MailList.py (adding the attribute PCN> self.auto_reject_nonmembers) isn't reflected in the PCN> HandlerAPI.py call to do_pipeline(mlist, msg, msgdata). PCN> AttributeError: auto_reject_nonmembers PCN> I'm not sure what a Delivery exception is caused by, but I'm PCN> inferring from the AttributeError that it can't find PCN> mlist.auto_reject_nonmembers. how cna this be? Is there PCN> somewhere else besides MailList.py where MailList objects are PCN> created? Or is there somewhere special that HandlerAPI.py or PCN> Hold.py is doing? PCN> Help? I can't suppress obnoxios posters for now, and the PCN> prospect of having to moderate posts from non-members is too PCN> horrible to contempate. Remember that existing lists get their state unpickled from the config.db file, so just adding `auto_reject_nonmembers' in the MailList constructor isn't enough. New lists will pick up that attribute, but existing lists won't have it. You have two choices: either you can conditionalize the getting of the auto_reject_nonmembers attribute with something like: if getattr(mlist, 'auto_reject_nonmembers', 0): or you can add it to existing lists via the schema update mechanisms in version.py. See NewVars() and remember that you'll have to bump DATA_FILE_VERSION in Version.py. -Barry From rcm@sasaska.net Tue Nov 5 15:22:14 2002 From: rcm@sasaska.net (Rafael Cordones Marcos) Date: Tue, 5 Nov 2002 16:22:14 +0100 (CET) Subject: [Mailman-Developers] Translation in E-mail Message-ID: <4600.213.100.45.224.1036509734.squirrel@sasaska.net> Hi folks, I have been searching the Mailman website and have not found any reference to what I am looking for, i.e. translating e-mail. I am not talking about translating the Mailman software or documentation (i18n) but translating the e-mails that people send to the mailing list. I am looking for the following functionality in a mailing list software: - As an administrator: - set up some default machine translation (MT) engine. For example, I want to use Babelfish for translating between English and Spanish but I wat to use some other engine for translating between German and Swedish. - specify the subject of the mailing list and thus improving the translation results. For instance, I can specify that the mailing list is about "Technical -> Operating Systems -> Minix" (just kidding). - As a user: - I want to subscribe to the mailing list and specify my language (natural) language preferences. Say I want specify {Catalan, Spanish, German}. - e-mail going to the list gets sent to a machine translation before it gets sent to me. I can optionaly say to the mailing list software that I want to receive also the original message. - If I do not like the translation of an e-mail I can choose some other machine translation engine. I may decide that some other translation engine does a better job or even pay to get get better translations. Maybe the administrator forgot to specify a machine translation engine for Euskera<->Farsi and I know of one that just started operating. I would appreciate any information you may have on this topic. Maybe somebody has started implementing this in Mailman or is already implemented? Send me any comments, problems you see on the aforementioned working schema, flames, ... Thanks a lot for your time! Rafa -- Link of the week: Der flexible Mensch. Robert Kurtz. [es] http://www.rebelion.org/economia/rkurz011002.htm [de] http://www.krisis.org/r-kurz_flexible-mensch_folha.html [en] If you find it, tell me! From barry@python.org Wed Nov 6 13:37:12 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 6 Nov 2002 08:37:12 -0500 Subject: [Mailman-Developers] Typo References: <015801c28594$7518aa80$1e00a8c0@onsnet.org> Message-ID: <15817.6920.590033.338198@gargle.gargle.HOWL> >>>>> "DT" == Danny Terweij writes: DT> I do not know the word "coerced", should this not be the word DT> "forced" ? "force" is a good synonym for "coerce" but it has a slightly different connotation. http://www.dictionary.com/search?q=coerce&db=* -Barry From les@2pi.org Wed Nov 6 14:07:13 2002 From: les@2pi.org (Les Niles) Date: Wed, 6 Nov 2002 06:07:13 -0800 Subject: [Mailman-Developers] Translation in E-mail In-Reply-To: <4600.213.100.45.224.1036509734.squirrel@sasaska.net> (rcm@sasaska.net) References: <4600.213.100.45.224.1036509734.squirrel@sasaska.net> Message-ID: <200211061407.GAA12071@2pi.org> Last year I hacked a simple translating filter into Mailman's delivery pipeline. The underlying engine was AltaVista's babelfish. It didn't have all the user-definable bells and whistles you mention, but did have an entertaining twist: Most messages went through untranslated, but those from selected senders were occassionally translated into a randomly-selected language. This was by design, intended for amusement purposes. It got only a very limited deployment. :) I'd be happy to send the code, but am not sure how useful it would be since most of what you need to implement has to do with adding user- and list-specific options, which my implementation didn't deal with at all. Adding such options is pretty easy, though, because of the nice design of Mailman. One thing you don't mention, but which I think you'll need to deal with, is identifying the source language of each message. That'll be needed unless senders will register the language in which they'll be posting and can be counted on to always post in that language. I've played around a bit with text-based language identification. The algorithms do pretty well, even on messages just a sentence or two in length, but the error rates are on the order of several percent. (I was looking at distinguishing between a dozen or so common European languages.) Occassionally mis- identifying the source language will add an element of randomness to the whole process, which from my experience last year I can tell you can be somewhat amusing. Another complication will be dealing with HTML-encoded email. If the translating engine itself can handle HTML, great, otherwise you'll probably need to strip or convert the HTML parts, to just translate and produce plain text. -les On Tue, 5 Nov 2002 16:22:14 +0100 (CET) "Rafael Cordones Marcos" wrote: >Hi folks, > >I have been searching the Mailman website and have not found any reference >to what I am looking for, i.e. translating e-mail. I am not talking about >translating the Mailman software or documentation (i18n) but translating >the e-mails that people send to the mailing list. > >I am looking for the following functionality in a mailing list software: > > - As an administrator: > > - set up some default machine translation (MT) engine. > For example, I want to use Babelfish for translating between English >and Spanish but I wat to use some other engine for > translating between German and Swedish. > > - specify the subject of the mailing list and thus improving the > translation results. For instance, I can specify that the > mailing list is about "Technical -> Operating Systems -> Minix" >(just kidding). > > - As a user: > > - I want to subscribe to the mailing list and specify my > language (natural) language preferences. Say I want specify > {Catalan, Spanish, German}. > > - e-mail going to the list gets sent to a machine translation > before it gets sent to me. I can optionaly say to the > mailing list software that I want to receive also the original message. > > - If I do not like the translation of an e-mail I can choose some > other machine translation engine. I may decide that some other >translation engine does a better job or even pay to get > get better translations. Maybe the administrator forgot to > specify a machine translation engine for Euskera<->Farsi and I know >of one that just started operating. > >I would appreciate any information you may have on this topic. Maybe >somebody has started implementing this in Mailman or is already >implemented? Send me any comments, problems you see on the aforementioned >working schema, flames, ... > >Thanks a lot for your time! > >Rafa From spacey-mailman@lenin.nu Wed Nov 6 16:21:09 2002 From: spacey-mailman@lenin.nu (Peter C. Norton) Date: Wed, 6 Nov 2002 08:21:09 -0800 Subject: [Mailman-Developers] Problem with my auto-bounce patch for 2.0.8 in 2.0.13 In-Reply-To: <15817.5145.200744.86446@gargle.gargle.HOWL> References: <20021106053318.GC8849@lenin.nu> <15817.5145.200744.86446@gargle.gargle.HOWL> Message-ID: <20021106162109.GS2733@lenin.nu> On Wed, Nov 06, 2002 at 08:07:37AM -0500, Barry A. Warsaw wrote: > > >>>>> "PCN" == Peter C Norton writes: > > PCN> However, I've created a bug in the privacy options page. For > PCN> some reason, changes I made to the MailList class in > PCN> MailList.py (adding the attribute > PCN> self.auto_reject_nonmembers) isn't reflected in the > PCN> HandlerAPI.py call to do_pipeline(mlist, msg, msgdata). > PCN> AttributeError: auto_reject_nonmembers > > PCN> I'm not sure what a Delivery exception is caused by, but I'm > PCN> inferring from the AttributeError that it can't find > PCN> mlist.auto_reject_nonmembers. how cna this be? Is there > PCN> somewhere else besides MailList.py where MailList objects are > PCN> created? Or is there somewhere special that HandlerAPI.py or > PCN> Hold.py is doing? > > PCN> Help? I can't suppress obnoxios posters for now, and the > PCN> prospect of having to moderate posts from non-members is too > PCN> horrible to contempate. > > Remember that existing lists get their state unpickled from the > config.db file, so just adding `auto_reject_nonmembers' in the > MailList constructor isn't enough. New lists will pick up that > attribute, but existing lists won't have it. The list did have that attribute, though. I created it with the patch under 2.0.8. Is there a chance that it got re-set in the upgrade. > You have two choices: either you can conditionalize the getting of the > auto_reject_nonmembers attribute with something like: > > if getattr(mlist, 'auto_reject_nonmembers', 0): > > or you can add it to existing lists via the schema update mechanisms > in version.py. See NewVars() and remember that you'll have to bump > DATA_FILE_VERSION in Version.py. I did that last time. I guess I can try that again. Perhaps my patch put in the wrong (lower) version. -Peter -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. From barry@python.org Wed Nov 6 18:15:12 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 6 Nov 2002 13:15:12 -0500 Subject: [Mailman-Developers] Problem with my auto-bounce patch for 2.0.8 in 2.0.13 References: <20021106053318.GC8849@lenin.nu> <15817.5145.200744.86446@gargle.gargle.HOWL> <20021106162109.GS2733@lenin.nu> Message-ID: <15817.23600.161851.780730@gargle.gargle.HOWL> >>>>> "PCN" == Peter C Norton writes: >> contempate. Remember that existing lists get their state >> unpickled from the config.db file, so just adding >> `auto_reject_nonmembers' in the MailList constructor isn't >> enough. New lists will pick up that attribute, but existing >> lists won't have it. PCN> The list did have that attribute, though. I created it with PCN> the patch under 2.0.8. Is there a chance that it got re-set PCN> in the upgrade. It's possible, but doubtful. As long as you don't prefix your attribute with underscore, it should get pickled and unpickled just fine. -Barry From martin.whinnery@blueyonder.co.uk Wed Nov 6 18:29:31 2002 From: martin.whinnery@blueyonder.co.uk (Martin Whinnery) Date: Wed, 6 Nov 2002 18:29:31 -0000 Subject: [Mailman-Developers] Embarrasingly pre-Alpha LDAP Member Adaptor Message-ID: <000601c285c2$75496890$e6faa8c0@MARTLAPIBM> Hi folks. First off - Thanks to Greg and Barry (in particular) for helping me get this far... Right. I've thrown together a first go at a pretty generic LDAP member adaptor for mailman 2.1b4. "It implements a read-only membership interface for a list, implemented as generically as possible, in an attempt to handle in a freindly way the various ways people handle grouping in general and mail grouping in particular with LDAP. WARNING!!!WARNING!!!WARNING!!!WARNING!!!WARNING!!!WARNING!!!WARNING!!! This is DEEPLY ALPHA code. It will almost certainly cause your genitalia to shrivel and your breath to smell, if used in a production environment. If this, or anything else bad happens because you ignored this, please let me know. I'll try not to say 'I told you so'." I'm looking for comments, whether on the assumptions I've made about how people want to handle the interface between LDAP and mailman lists, or on my coding. I am using this in a purely test environment at the moment. As soon as MM 2.1 gets to be stable, I'll be using this or something better at work, for real. So I suppose this is a call for help. Either help me get my code right, or save me having to use it!! Martin Whinnery 'Merely the Assistant' Network Manager South Birmingham College Whoah. Nearly forget the 'meat'. http://www.offal.homelinux.org/python/mailman/LDAPMemberAdaptor/V0.1/ind ex.html Is where the stuff's at. From jarrell@vt.edu Thu Nov 7 00:03:10 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Wed, 6 Nov 2002 19:03:10 -0500 (EST) Subject: [Mailman-Developers] hyperarch error w/2.1b4 Message-ID: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> I'd file a bug report on this, but I'm on my out the door and won't be online the rest of the night, and will likely forget about it until the next time I look at the errorlog... This is after applying updates *yesterday*, although nothing checked in so far today would seem to apply.. Only happened once, although plenty of messages have gone through different lists that would have archived. Nov 06 18:19:09 2002 qrunner(13969): Traceback (most recent call last): Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/Archiver.py", line 213, in ArchiveMail Nov 06 18:19:09 2002 qrunner(13969): h.close() Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close Nov 06 18:19:09 2002 qrunner(13969): self.update_dirty_archives() Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1074, in update_dirty_archives Nov 06 18:19:09 2002 qrunner(13969): self.__super_update_dirty_archives() Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives Nov 06 18:19:09 2002 qrunner(13969): self.update_archive(i) Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1077, in update_archive Nov 06 18:19:09 2002 qrunner(13969): self.__super_update_archive(archive) Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/pipermail.py", line 423, in update_archive Nov 06 18:19:09 2002 qrunner(13969): self._update_simple_index(hdr, archive, arcdir) Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/pipermail.py", line 439, in _update_simple_index Nov 06 18:19:09 2002 qrunner(13969): article = self.database.getArticle(self.archive, msgid) Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/HyperDatabase.py", line 284, in getArticle Nov 06 18:19:09 2002 qrunner(13969): article = self.__cache[msgid] = pickle.loads(buf) Nov 06 18:19:09 2002 qrunner(13969): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 314, in __setstate__ Nov 06 18:19:09 2002 qrunner(13969): if self._mlist is None: Nov 06 18:19:09 2002 qrunner(13969): AttributeError: Article instance has no attribute '_mlist' From noreply@sourceforge.net Thu Nov 7 00:05:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 06 Nov 2002 16:05:41 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634737 ] . in message body Message-ID: Bugs item #634737, was opened at 2002-11-07 01:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634737&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Luca De Santis (lucadex) Assigned to: Nobody/Anonymous (nobody) Summary: . in message body Initial Comment: I looked in the bugs archive but couldn't find anything similar reported, so I write down something about it, hoping it could be of any help. I experienced a problem with Mailman 2.0.11 when a mail posted to the list contained the sequence . (eg. \n.\n) in the middle of the message body. This is the normal char sequence used to indicate the end of the body message (cfr RFC821). In my Mailman installation I use Sendmail for the actual delivery. If a similar message was sent to the list, the qrunner script crashed and I found the following errors in the log: Nov 06 02:05:02 2002 (16085) Delivery exception: [Errno 32] Broken pipe Nov 06 02:05:02 2002 (16085) Traceback (innermost last): File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/Sendmail.py", line 86, in process fp.write(msgtext) IOError: [Errno 32] Broken pipe It seems like the . in the body of the message was interpreted as the end of the message by Sendmail, so it closed the pipe causing the errors above. All the subscrivers of the list received only the portion of the mail just before the .. Now, since the message was not removed from the qfiles directory, it was resent over and over again to the list. To solve the problem I patched the Handlers/Sendmail.py script adding the following function: def cleanPeriod(str): pattern = re.compile(r"^\.$(.+)", re.DOTALL|re.MULTILINE) return (pattern.sub(r'. \1', str)) and changing line 80 from: msgtext = str(msg) to msgtext = cleanPeriod(str(msg)) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634737&group_id=103 From dan.mick@sun.com Thu Nov 7 00:19:05 2002 From: dan.mick@sun.com (Dan Mick) Date: Wed, 06 Nov 2002 16:19:05 -0800 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <3DC9B179.3000102@sun.com> Yeah, I saw one of these too. I dropped a note to Barry about it but haven't heard back: -=-=-=-=- I got an error last night that made me wonder whether this should be present for "transition" archives: $ cvs diff HyperArch.py Index: HyperArch.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v retrieving revision 2.24 diff -r2.24 HyperArch.py 314c314 < if self._mlist is None: --- > if not hasattr(self, "_mlist") or self._mlist is None: $ -=-=-=-=- Ron Jarrell wrote: > I'd file a bug report on this, but I'm on my out the door and won't be > online the rest of the night, and will likely forget about it until the > next time I look at the errorlog... This is after applying updates > *yesterday*, although nothing checked in so far today would seem > to apply.. Only happened once, although plenty of messages have > gone through different lists that would have archived. > > Nov 06 18:19:09 2002 qrunner(13969): Traceback (most recent call last): > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/Archiver.py", line 213, in ArchiveMail > Nov 06 18:19:09 2002 qrunner(13969): h.close() > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close > Nov 06 18:19:09 2002 qrunner(13969): self.update_dirty_archives() > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/HyperArch.py", line 1074, in > update_dirty_archives > Nov 06 18:19:09 2002 qrunner(13969): self.__super_update_dirty_archives() > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in > update_dirty_archives > Nov 06 18:19:09 2002 qrunner(13969): self.update_archive(i) > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/HyperArch.py", line 1077, in update_archive > Nov 06 18:19:09 2002 qrunner(13969): self.__super_update_archive(archive) > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/pipermail.py", line 423, in update_archive > Nov 06 18:19:09 2002 qrunner(13969): self._update_simple_index(hdr, > archive, arcdir) > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/pipermail.py", line 439, in > _update_simple_index > Nov 06 18:19:09 2002 qrunner(13969): article = > self.database.getArticle(self.archive, msgid) > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/HyperDatabase.py", line 284, in getArticle > Nov 06 18:19:09 2002 qrunner(13969): article = self.__cache[msgid] = > pickle.loads(buf) > Nov 06 18:19:09 2002 qrunner(13969): File > "/home/mailman/Mailman/Archiver/HyperArch.py", line 314, in __setstate__ > Nov 06 18:19:09 2002 qrunner(13969): if self._mlist is None: > Nov 06 18:19:09 2002 qrunner(13969): AttributeError: Article instance has > no attribute '_mlist' From noreply@sourceforge.net Thu Nov 7 17:27:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 09:27:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634737 ] . in message body Message-ID: Bugs item #634737, was opened at 2002-11-06 19:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634737&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Luca De Santis (lucadex) Assigned to: Nobody/Anonymous (nobody) Summary: . in message body Initial Comment: I looked in the bugs archive but couldn't find anything similar reported, so I write down something about it, hoping it could be of any help. I experienced a problem with Mailman 2.0.11 when a mail posted to the list contained the sequence . (eg. \n.\n) in the middle of the message body. This is the normal char sequence used to indicate the end of the body message (cfr RFC821). In my Mailman installation I use Sendmail for the actual delivery. If a similar message was sent to the list, the qrunner script crashed and I found the following errors in the log: Nov 06 02:05:02 2002 (16085) Delivery exception: [Errno 32] Broken pipe Nov 06 02:05:02 2002 (16085) Traceback (innermost last): File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/Sendmail.py", line 86, in process fp.write(msgtext) IOError: [Errno 32] Broken pipe It seems like the . in the body of the message was interpreted as the end of the message by Sendmail, so it closed the pipe causing the errors above. All the subscrivers of the list received only the portion of the mail just before the .. Now, since the message was not removed from the qfiles directory, it was resent over and over again to the list. To solve the problem I patched the Handlers/Sendmail.py script adding the following function: def cleanPeriod(str): pattern = re.compile(r"^\.$(.+)", re.DOTALL|re.MULTILINE) return (pattern.sub(r'. \1', str)) and changing line 80 from: msgtext = str(msg) to msgtext = cleanPeriod(str(msg)) ---------------------------------------------------------------------- Comment By: Greg Ward (gward) Date: 2002-11-07 12:27 Message: Logged In: YES user_id=14422 A possibly cleaner fix is to run sendmail with the "-oi" switch. I'm not sure if all MTAs recognize this, but I think at least Sendmail proper and Exim do. Here's what Exim's man page has to say: -oi This option, which has the same effect as -i, spec­ ifies that a dot on a line by itself should not terminate an incoming, non-SMTP message. This is the default if Exim is called as rmail. So maybe "-i" is the portable way to specify this option? I wonder how Mailman handles such messages when SMTP is used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634737&group_id=103 From noreply@sourceforge.net Thu Nov 7 20:41:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 12:41:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634737 ] . in message body Message-ID: Bugs item #634737, was opened at 2002-11-06 19:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634737&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Luca De Santis (lucadex) Assigned to: Nobody/Anonymous (nobody) Summary: . in message body Initial Comment: I looked in the bugs archive but couldn't find anything similar reported, so I write down something about it, hoping it could be of any help. I experienced a problem with Mailman 2.0.11 when a mail posted to the list contained the sequence . (eg. \n.\n) in the middle of the message body. This is the normal char sequence used to indicate the end of the body message (cfr RFC821). In my Mailman installation I use Sendmail for the actual delivery. If a similar message was sent to the list, the qrunner script crashed and I found the following errors in the log: Nov 06 02:05:02 2002 (16085) Delivery exception: [Errno 32] Broken pipe Nov 06 02:05:02 2002 (16085) Traceback (innermost last): File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/Sendmail.py", line 86, in process fp.write(msgtext) IOError: [Errno 32] Broken pipe It seems like the . in the body of the message was interpreted as the end of the message by Sendmail, so it closed the pipe causing the errors above. All the subscrivers of the list received only the portion of the mail just before the .. Now, since the message was not removed from the qfiles directory, it was resent over and over again to the list. To solve the problem I patched the Handlers/Sendmail.py script adding the following function: def cleanPeriod(str): pattern = re.compile(r"^\.$(.+)", re.DOTALL|re.MULTILINE) return (pattern.sub(r'. \1', str)) and changing line 80 from: msgtext = str(msg) to msgtext = cleanPeriod(str(msg)) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-07 15:41 Message: Logged In: YES user_id=12800 Please note that Sendmail.py is not safe to use. Is there some reason why you can't switch to SMTPDeliver.py? Also, in MM2.1, Sendmail.py is deliberately sabotaged so you can't use it unless you hack the source (and acknowledge the security holes). ---------------------------------------------------------------------- Comment By: Greg Ward (gward) Date: 2002-11-07 12:27 Message: Logged In: YES user_id=14422 A possibly cleaner fix is to run sendmail with the "-oi" switch. I'm not sure if all MTAs recognize this, but I think at least Sendmail proper and Exim do. Here's what Exim's man page has to say: -oi This option, which has the same effect as -i, spec­ ifies that a dot on a line by itself should not terminate an incoming, non-SMTP message. This is the default if Exim is called as rmail. So maybe "-i" is the portable way to specify this option? I wonder how Mailman handles such messages when SMTP is used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634737&group_id=103 From noreply@sourceforge.net Thu Nov 7 20:44:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 12:44:56 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634274 ] Some digest seems to have a wrong Message-ID: Bugs item #634274, was opened at 2002-11-06 01:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_id=103 Category: mail delivery >Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: divine rites (divinerites) Assigned to: Nobody/Anonymous (nobody) Summary: Some digest seems to have a wrong Initial Comment: Some Zope digests looks ugly with Evolution. Some digests on some lists are concerned. Not predictable. Digest should look like all normal ones (like for all digests who works fine in evolution) This link give the whole explanation for the digest problem from the evolution point of view. It seems that the mail has some wrong type. http://bugzilla.ximian.com/show_bug.cgi?id=33282 I don't know what Mailman version it is but i guess zope lists use a brand new mailman ;-)) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-07 15:44 Message: Logged In: YES user_id=12800 Actually the Zope lists use Mailman 2.0. I've tested this for MM2.1 plaintext (RFC 1153) digest and can't verify it, so I suspct it's no longer a bug. If it's happening in MM2.0 I can't see it in the code, but I doubt it will get fixed in that branch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_id=103 From barry@python.org Thu Nov 7 22:34:53 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 7 Nov 2002 17:34:53 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <15818.60045.559452.189545@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> I'd file a bug report on this, but I'm on my out the door and RJ> won't be online the rest of the night, and will likely forget RJ> about it until the next time I look at the errorlog... This is RJ> after applying updates *yesterday*, although nothing checked RJ> in so far today would seem to apply.. Only happened once, RJ> although plenty of messages have gone through different lists RJ> that would have archived. Okay, I just checked in some fixes for this, I believe. See the bin/b4b5-archfix script. Do a normal update then run this as specified in the docstring (use --help for details). I've done a little testing with this but will verify with more lists momentarily. -Barry From barry@python.org Thu Nov 7 22:37:36 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 7 Nov 2002 17:37:36 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> <15818.60045.559452.189545@gargle.gargle.HOWL> Message-ID: <15818.60208.962906.802456@gargle.gargle.HOWL> >>>>> "BAW" == Barry A Warsaw writes: BAW> Okay, I just checked in some fixes for this, I believe. See BAW> the bin/b4b5-archfix script. Do a normal update then run BAW> this as specified in the docstring (use --help for details). BAW> I've done a little testing with this but will verify with BAW> more lists momentarily. Oh yeah, you'll need to re-run configure (not config.status) when doing the make install. -Barry From noreply@sourceforge.net Thu Nov 7 22:44:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 14:44:23 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635227 ] [PATCH] CGI doesn't handle sigterm Message-ID: Bugs item #635227, was opened at 2002-11-07 14:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635227&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Hardie (thardie) Assigned to: Nobody/Anonymous (nobody) Summary: [PATCH] CGI doesn't handle sigterm Initial Comment: If a connection is closed to a CGI script, the web server terminates the script with a sigterm, which results in a traceback. admin(6564): [----- Mailman Version: 2.1b4 -----] admin(6564): [----- Traceback ------] admin(6564): Traceback (most recent call last): admin(6564): File "/usr/local/mailman/scripts/driver", line 88, in run_main admin(6564): sys.__stdout__.write (tempstdout.getvalue()) admin(6564): File "/usr/local/mailman/Mailman/Cgi/options.py", line 322, in sigterm_handler admin(6564): sys.exit(0) admin(6564): NameError: global name 'sys' is not defined admin(6564): [----- Python Information -----] admin(6564): sys.version = 2.1.3 (#1, Jul 29 2002, 22:34:51) [GCC 2.95.4 20011002 (Debian prerelease)] admin(6564): sys.executable = /usr/bin/python admin(6564): sys.prefix = /usr admin(6564): sys.exec_prefix = /usr admin(6564): sys.path = /usr admin(6564): sys.platform = linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635227&group_id=103 From barry@python.org Thu Nov 7 23:08:49 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 7 Nov 2002 18:08:49 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> <15818.60045.559452.189545@gargle.gargle.HOWL> <15818.60208.962906.802456@gargle.gargle.HOWL> Message-ID: <15818.62081.452837.965550@gargle.gargle.HOWL> >>>>> "BAW" == Barry A Warsaw writes: BAW> Oh yeah, you'll need to re-run configure (not config.status) BAW> when doing the make install. Blah, blah, blah. Please ignore, this is a test. ;) -Barry From noreply@sourceforge.net Thu Nov 7 23:14:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 15:14:34 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635227 ] [PATCH] CGI doesn't handle sigterm Message-ID: Bugs item #635227, was opened at 2002-11-07 17:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635227&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Terry Hardie (thardie) Assigned to: Nobody/Anonymous (nobody) Summary: [PATCH] CGI doesn't handle sigterm Initial Comment: If a connection is closed to a CGI script, the web server terminates the script with a sigterm, which results in a traceback. admin(6564): [----- Mailman Version: 2.1b4 -----] admin(6564): [----- Traceback ------] admin(6564): Traceback (most recent call last): admin(6564): File "/usr/local/mailman/scripts/driver", line 88, in run_main admin(6564): sys.__stdout__.write (tempstdout.getvalue()) admin(6564): File "/usr/local/mailman/Mailman/Cgi/options.py", line 322, in sigterm_handler admin(6564): sys.exit(0) admin(6564): NameError: global name 'sys' is not defined admin(6564): [----- Python Information -----] admin(6564): sys.version = 2.1.3 (#1, Jul 29 2002, 22:34:51) [GCC 2.95.4 20011002 (Debian prerelease)] admin(6564): sys.executable = /usr/bin/python admin(6564): sys.prefix = /usr admin(6564): sys.exec_prefix = /usr admin(6564): sys.path = /usr admin(6564): sys.platform = linux2 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-07 18:14 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635227&group_id=103 From noreply@sourceforge.net Fri Nov 8 00:07:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 16:07:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-620032 ] cmd_confirm: no lstrip Message-ID: Bugs item #620032, was opened at 2002-10-07 22:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: cmd_confirm: no lstrip Initial Comment: Sep 23 18:45:41 2002 (574) Uncaught runner exception: 'NoneType' object has no attribute 'lstrip' Sep 23 18:45:41 2002 (574) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 198, in _dispose res.process() File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 93, in process stop = self.do_command(cmd, args) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 119, in do_command return handler.process(self, args) File "/home/mailman/Mailman/Commands/cmd_co nfirm.py", line 72, in process if line.lstrip() == match: AttributeError: 'NoneType' object has no attribute 'lstrip' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 From jarrell@vt.edu Fri Nov 8 05:33:50 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:33:50 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <15818.60045.559452.189545@gargle.gargle.HOWL> References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> At 05:34 PM 11/7/02 -0500, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell writes: > > RJ> I'd file a bug report on this, but I'm on my out the door and > RJ> won't be online the rest of the night, and will likely forget > RJ> about it until the next time I look at the errorlog... This is > RJ> after applying updates *yesterday*, although nothing checked > RJ> in so far today would seem to apply.. Only happened once, > RJ> although plenty of messages have gone through different lists > RJ> that would have archived. > >Okay, I just checked in some fixes for this, I believe. See the >bin/b4b5-archfix script. Do a normal update then run this as >specified in the docstring (use --help for details). > >I've done a little testing with this but will verify with more lists >momentarily. Hey, Barry, or did your testing not include actually *doing* a -h? :-) Given that it causes a traceback, because b4b5-archfix is missing a from Mailman.i18n import _ From jarrell@vt.edu Fri Nov 8 05:54:43 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:54:43 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> References: <15818.60045.559452.189545@gargle.gargle.HOWL> <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108005344.04604060@lennier.cc.vt.edu> >>Okay, I just checked in some fixes for this, I believe. See the >>bin/b4b5-archfix script. Do a normal update then run this as >>specified in the docstring (use --help for details). Then run check_perms -f, because b4b5-archfix will step all over your permissions, unless you happen to run it *as* the mailman user... From noreply@sourceforge.net Fri Nov 8 12:13:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 04:13:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color Message-ID: Bugs item #635462, was opened at 2002-11-08 12:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marcin Orlowski (carl-os) Assigned to: Nobody/Anonymous (nobody) Summary: Admin pages HTML does not set TEXT color Initial Comment: Mailman admin pages believe that TEXT color is always black and does not set it to, hoping nobody changes the defaults. And this is false assumption ;-) For testing purposes my defaults are black bg color and yellow text. And since admin pages sets bg to white it now exposes yellow fonts on white background here. Kinda unreadable. Solution -> fix template/css/whatever to set up text color to black. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 From Dale@Newfield.org Fri Nov 8 14:37:24 2002 From: Dale@Newfield.org (Dale Newfield) Date: Fri, 8 Nov 2002 09:37:24 -0500 (EST) Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: Message-ID: On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: > Admin pages HTML does not set TEXT color Why is it mailman's job to protect stupid users from their own browser settings? -Dale From barry@python.org Fri Nov 8 15:32:09 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 8 Nov 2002 10:32:09 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> Message-ID: <15819.55545.885253.249455@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> Hey, Barry, or did your testing not include actually *doing* a RJ> -h? :-) RJ> Given that it causes a traceback, because b4b5-archfix is RJ> missing a from Mailman.i18n import _ Fixed, thanks. I also added a nice reminder printed when finished that check_perms should be run. -Barry From noreply@sourceforge.net Fri Nov 8 15:38:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 07:38:48 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError Message-ID: Bugs item #635542, was opened at 2002-11-08 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught MMNoSuchUserError Initial Comment: I found an unsubscribe confirmation message in the shunt directory. The error log suggests that someone used both the web and the reply to unsubscribe, but when the email confirmation arrived, he was already gone and qrunner faulted. I'm running a CVS build about a week old. Here's the traceback: Nov 08 05:29:33 2002 (23820) Uncaught runner exception: Nov 08 05:29:33 2002 (23820) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 199, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 117, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1107, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/mailman/Mailman/MailList.py", line 936, in ApprovedDeleteMember raise Errors.MMNoSuchUserError MMNoSuchUserError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 From jwblist@olympus.net Sat Nov 9 07:43:26 2002 From: jwblist@olympus.net (John W Baxter) Date: Fri, 8 Nov 2002 23:43:26 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: References: Message-ID: At 9:37 -0500 11/8/2002, Dale Newfield wrote: >On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: >> Admin pages HTML does not set TEXT color > >Why is it mailman's job to protect stupid users from their own browser >settings? This one sounded like it was posted not from a stupid user but from a careful tester. If mailman has an intended appearance, it should cause that appearance to happen unless the user--in a browser which will--has refused to allow the site to override her local style sheet. Personally, I liked the old days, when the user's browser settings were allowed to control appearance details, and HTML described content. Of course, one could hardly hire out as a "designer" following that idea, so it didn't last long. --John (one of the few who remembers that the first T in HTTP stands for Text) -- John Baxter Port Ludlow, WA USA Always allow for the innate perversity of inanimate matter. From noreply@sourceforge.net Sun Nov 10 21:57:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 13:57:54 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-636363 ] Delete all pending messages Message-ID: Feature Requests item #636363, was opened at 2002-11-10 21:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: Delete all pending messages Initial Comment: Been hunting high and low for a script or patch to go into all my mailing lists and delete all pending posts.. There is one group of spammers who have managed to get ahold of the list email addresses and all the posts come from them.. We also block all HTML email so we have a lot of posts from those people which could be deleted as well. Really would like some kind of commandline utility for doing this, and I don't know python. Just an idea. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 From noreply@sourceforge.net Mon Nov 11 00:39:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 16:39:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Mon Nov 11 00:42:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 16:42:18 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-636363 ] Delete all pending messages Message-ID: Feature Requests item #636363, was opened at 2002-11-10 21:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: Delete all pending messages Initial Comment: Been hunting high and low for a script or patch to go into all my mailing lists and delete all pending posts.. There is one group of spammers who have managed to get ahold of the list email addresses and all the posts come from them.. We also block all HTML email so we have a lot of posts from those people which could be deleted as well. Really would like some kind of commandline utility for doing this, and I don't know python. Just an idea. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-11-11 00:42 Message: Logged In: YES user_id=67709 I hope this script helps; https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 From noreply@sourceforge.net Mon Nov 11 01:37:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 17:37:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-11 01:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Fri Nov 8 00:07:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 16:07:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-620032 ] cmd_confirm: no lstrip Message-ID: Bugs item #620032, was opened at 2002-10-07 22:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: cmd_confirm: no lstrip Initial Comment: Sep 23 18:45:41 2002 (574) Uncaught runner exception: 'NoneType' object has no attribute 'lstrip' Sep 23 18:45:41 2002 (574) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 198, in _dispose res.process() File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 93, in process stop = self.do_command(cmd, args) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 119, in do_command return handler.process(self, args) File "/home/mailman/Mailman/Commands/cmd_co nfirm.py", line 72, in process if line.lstrip() == match: AttributeError: 'NoneType' object has no attribute 'lstrip' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 From jarrell@vt.edu Fri Nov 8 05:33:50 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:33:50 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <15818.60045.559452.189545@gargle.gargle.HOWL> References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> At 05:34 PM 11/7/02 -0500, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell writes: > > RJ> I'd file a bug report on this, but I'm on my out the door and > RJ> won't be online the rest of the night, and will likely forget > RJ> about it until the next time I look at the errorlog... This is > RJ> after applying updates *yesterday*, although nothing checked > RJ> in so far today would seem to apply.. Only happened once, > RJ> although plenty of messages have gone through different lists > RJ> that would have archived. > >Okay, I just checked in some fixes for this, I believe. See the >bin/b4b5-archfix script. Do a normal update then run this as >specified in the docstring (use --help for details). > >I've done a little testing with this but will verify with more lists >momentarily. Hey, Barry, or did your testing not include actually *doing* a -h? :-) Given that it causes a traceback, because b4b5-archfix is missing a from Mailman.i18n import _ From jarrell@vt.edu Fri Nov 8 05:54:43 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:54:43 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> References: <15818.60045.559452.189545@gargle.gargle.HOWL> <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108005344.04604060@lennier.cc.vt.edu> >>Okay, I just checked in some fixes for this, I believe. See the >>bin/b4b5-archfix script. Do a normal update then run this as >>specified in the docstring (use --help for details). Then run check_perms -f, because b4b5-archfix will step all over your permissions, unless you happen to run it *as* the mailman user... From noreply@sourceforge.net Fri Nov 8 12:13:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 04:13:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color Message-ID: Bugs item #635462, was opened at 2002-11-08 12:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marcin Orlowski (carl-os) Assigned to: Nobody/Anonymous (nobody) Summary: Admin pages HTML does not set TEXT color Initial Comment: Mailman admin pages believe that TEXT color is always black and does not set it to, hoping nobody changes the defaults. And this is false assumption ;-) For testing purposes my defaults are black bg color and yellow text. And since admin pages sets bg to white it now exposes yellow fonts on white background here. Kinda unreadable. Solution -> fix template/css/whatever to set up text color to black. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 From Dale@Newfield.org Fri Nov 8 14:37:24 2002 From: Dale@Newfield.org (Dale Newfield) Date: Fri, 8 Nov 2002 09:37:24 -0500 (EST) Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: Message-ID: On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: > Admin pages HTML does not set TEXT color Why is it mailman's job to protect stupid users from their own browser settings? -Dale From barry@python.org Fri Nov 8 15:32:09 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 8 Nov 2002 10:32:09 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> Message-ID: <15819.55545.885253.249455@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> Hey, Barry, or did your testing not include actually *doing* a RJ> -h? :-) RJ> Given that it causes a traceback, because b4b5-archfix is RJ> missing a from Mailman.i18n import _ Fixed, thanks. I also added a nice reminder printed when finished that check_perms should be run. -Barry From noreply@sourceforge.net Fri Nov 8 15:38:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 07:38:48 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError Message-ID: Bugs item #635542, was opened at 2002-11-08 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught MMNoSuchUserError Initial Comment: I found an unsubscribe confirmation message in the shunt directory. The error log suggests that someone used both the web and the reply to unsubscribe, but when the email confirmation arrived, he was already gone and qrunner faulted. I'm running a CVS build about a week old. Here's the traceback: Nov 08 05:29:33 2002 (23820) Uncaught runner exception: Nov 08 05:29:33 2002 (23820) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 199, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 117, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1107, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/mailman/Mailman/MailList.py", line 936, in ApprovedDeleteMember raise Errors.MMNoSuchUserError MMNoSuchUserError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 From noreply@sourceforge.net Fri Nov 8 00:07:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 16:07:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-620032 ] cmd_confirm: no lstrip Message-ID: Bugs item #620032, was opened at 2002-10-07 22:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: cmd_confirm: no lstrip Initial Comment: Sep 23 18:45:41 2002 (574) Uncaught runner exception: 'NoneType' object has no attribute 'lstrip' Sep 23 18:45:41 2002 (574) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 198, in _dispose res.process() File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 93, in process stop = self.do_command(cmd, args) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 119, in do_command return handler.process(self, args) File "/home/mailman/Mailman/Commands/cmd_co nfirm.py", line 72, in process if line.lstrip() == match: AttributeError: 'NoneType' object has no attribute 'lstrip' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 From jarrell@vt.edu Fri Nov 8 05:33:50 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:33:50 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <15818.60045.559452.189545@gargle.gargle.HOWL> References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> At 05:34 PM 11/7/02 -0500, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell writes: > > RJ> I'd file a bug report on this, but I'm on my out the door and > RJ> won't be online the rest of the night, and will likely forget > RJ> about it until the next time I look at the errorlog... This is > RJ> after applying updates *yesterday*, although nothing checked > RJ> in so far today would seem to apply.. Only happened once, > RJ> although plenty of messages have gone through different lists > RJ> that would have archived. > >Okay, I just checked in some fixes for this, I believe. See the >bin/b4b5-archfix script. Do a normal update then run this as >specified in the docstring (use --help for details). > >I've done a little testing with this but will verify with more lists >momentarily. Hey, Barry, or did your testing not include actually *doing* a -h? :-) Given that it causes a traceback, because b4b5-archfix is missing a from Mailman.i18n import _ From jarrell@vt.edu Fri Nov 8 05:54:43 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:54:43 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> References: <15818.60045.559452.189545@gargle.gargle.HOWL> <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108005344.04604060@lennier.cc.vt.edu> >>Okay, I just checked in some fixes for this, I believe. See the >>bin/b4b5-archfix script. Do a normal update then run this as >>specified in the docstring (use --help for details). Then run check_perms -f, because b4b5-archfix will step all over your permissions, unless you happen to run it *as* the mailman user... From noreply@sourceforge.net Fri Nov 8 12:13:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 04:13:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color Message-ID: Bugs item #635462, was opened at 2002-11-08 12:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marcin Orlowski (carl-os) Assigned to: Nobody/Anonymous (nobody) Summary: Admin pages HTML does not set TEXT color Initial Comment: Mailman admin pages believe that TEXT color is always black and does not set it to, hoping nobody changes the defaults. And this is false assumption ;-) For testing purposes my defaults are black bg color and yellow text. And since admin pages sets bg to white it now exposes yellow fonts on white background here. Kinda unreadable. Solution -> fix template/css/whatever to set up text color to black. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 From Dale@Newfield.org Fri Nov 8 14:37:24 2002 From: Dale@Newfield.org (Dale Newfield) Date: Fri, 8 Nov 2002 09:37:24 -0500 (EST) Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: Message-ID: On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: > Admin pages HTML does not set TEXT color Why is it mailman's job to protect stupid users from their own browser settings? -Dale From barry@python.org Fri Nov 8 15:32:09 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 8 Nov 2002 10:32:09 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> Message-ID: <15819.55545.885253.249455@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> Hey, Barry, or did your testing not include actually *doing* a RJ> -h? :-) RJ> Given that it causes a traceback, because b4b5-archfix is RJ> missing a from Mailman.i18n import _ Fixed, thanks. I also added a nice reminder printed when finished that check_perms should be run. -Barry From noreply@sourceforge.net Fri Nov 8 15:38:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 07:38:48 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError Message-ID: Bugs item #635542, was opened at 2002-11-08 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught MMNoSuchUserError Initial Comment: I found an unsubscribe confirmation message in the shunt directory. The error log suggests that someone used both the web and the reply to unsubscribe, but when the email confirmation arrived, he was already gone and qrunner faulted. I'm running a CVS build about a week old. Here's the traceback: Nov 08 05:29:33 2002 (23820) Uncaught runner exception: Nov 08 05:29:33 2002 (23820) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 199, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 117, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1107, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/mailman/Mailman/MailList.py", line 936, in ApprovedDeleteMember raise Errors.MMNoSuchUserError MMNoSuchUserError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 From jwblist@olympus.net Sat Nov 9 07:43:26 2002 From: jwblist@olympus.net (John W Baxter) Date: Fri, 8 Nov 2002 23:43:26 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: References: Message-ID: At 9:37 -0500 11/8/2002, Dale Newfield wrote: >On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: >> Admin pages HTML does not set TEXT color > >Why is it mailman's job to protect stupid users from their own browser >settings? This one sounded like it was posted not from a stupid user but from a careful tester. If mailman has an intended appearance, it should cause that appearance to happen unless the user--in a browser which will--has refused to allow the site to override her local style sheet. Personally, I liked the old days, when the user's browser settings were allowed to control appearance details, and HTML described content. Of course, one could hardly hire out as a "designer" following that idea, so it didn't last long. --John (one of the few who remembers that the first T in HTTP stands for Text) -- John Baxter Port Ludlow, WA USA Always allow for the innate perversity of inanimate matter. From noreply@sourceforge.net Sun Nov 10 21:57:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 13:57:54 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-636363 ] Delete all pending messages Message-ID: Feature Requests item #636363, was opened at 2002-11-10 21:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: Delete all pending messages Initial Comment: Been hunting high and low for a script or patch to go into all my mailing lists and delete all pending posts.. There is one group of spammers who have managed to get ahold of the list email addresses and all the posts come from them.. We also block all HTML email so we have a lot of posts from those people which could be deleted as well. Really would like some kind of commandline utility for doing this, and I don't know python. Just an idea. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 From noreply@sourceforge.net Mon Nov 11 00:39:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 16:39:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Mon Nov 11 00:42:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 16:42:18 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-636363 ] Delete all pending messages Message-ID: Feature Requests item #636363, was opened at 2002-11-10 21:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: Delete all pending messages Initial Comment: Been hunting high and low for a script or patch to go into all my mailing lists and delete all pending posts.. There is one group of spammers who have managed to get ahold of the list email addresses and all the posts come from them.. We also block all HTML email so we have a lot of posts from those people which could be deleted as well. Really would like some kind of commandline utility for doing this, and I don't know python. Just an idea. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-11-11 00:42 Message: Logged In: YES user_id=67709 I hope this script helps; https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 From noreply@sourceforge.net Mon Nov 11 01:37:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 17:37:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-11 01:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Fri Nov 8 00:07:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 16:07:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-620032 ] cmd_confirm: no lstrip Message-ID: Bugs item #620032, was opened at 2002-10-07 22:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: cmd_confirm: no lstrip Initial Comment: Sep 23 18:45:41 2002 (574) Uncaught runner exception: 'NoneType' object has no attribute 'lstrip' Sep 23 18:45:41 2002 (574) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 198, in _dispose res.process() File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 93, in process stop = self.do_command(cmd, args) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 119, in do_command return handler.process(self, args) File "/home/mailman/Mailman/Commands/cmd_co nfirm.py", line 72, in process if line.lstrip() == match: AttributeError: 'NoneType' object has no attribute 'lstrip' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 From noreply@sourceforge.net Mon Nov 11 08:15:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 11 Nov 2002 00:15:12 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636504 ] Configurable absolute URLs for scripts Message-ID: Patches item #636504, was opened at 2002-11-11 09:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636504&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable absolute URLs for scripts Initial Comment: In my Mailman setup I want to use http for some URLs (most of them, including the archives) for less CPU usage on the server, and https on some URLs (login with password, list administration) for better (if not good, since the passwords go in cleartext over mail anyway) security. One way of accomplishing this is to make script URLs absolute, and set DEFAULT_URL to a https hostname. This patch makes it possible to configure if GetScriptURL should by default return an absolute URL using a variable in Default.py/mm_cfg.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636504&group_id=103 From noreply@sourceforge.net Fri Nov 8 00:07:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 07 Nov 2002 16:07:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-620032 ] cmd_confirm: no lstrip Message-ID: Bugs item #620032, was opened at 2002-10-07 22:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: cmd_confirm: no lstrip Initial Comment: Sep 23 18:45:41 2002 (574) Uncaught runner exception: 'NoneType' object has no attribute 'lstrip' Sep 23 18:45:41 2002 (574) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 198, in _dispose res.process() File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 93, in process stop = self.do_command(cmd, args) File "/home/mailman/Mailman/Queue/CommandRu nner.py", line 119, in do_command return handler.process(self, args) File "/home/mailman/Mailman/Commands/cmd_co nfirm.py", line 72, in process if line.lstrip() == match: AttributeError: 'NoneType' object has no attribute 'lstrip' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620032&group_id=103 From jarrell@vt.edu Fri Nov 8 05:33:50 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:33:50 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <15818.60045.559452.189545@gargle.gargle.HOWL> References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> At 05:34 PM 11/7/02 -0500, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell writes: > > RJ> I'd file a bug report on this, but I'm on my out the door and > RJ> won't be online the rest of the night, and will likely forget > RJ> about it until the next time I look at the errorlog... This is > RJ> after applying updates *yesterday*, although nothing checked > RJ> in so far today would seem to apply.. Only happened once, > RJ> although plenty of messages have gone through different lists > RJ> that would have archived. > >Okay, I just checked in some fixes for this, I believe. See the >bin/b4b5-archfix script. Do a normal update then run this as >specified in the docstring (use --help for details). > >I've done a little testing with this but will verify with more lists >momentarily. Hey, Barry, or did your testing not include actually *doing* a -h? :-) Given that it causes a traceback, because b4b5-archfix is missing a from Mailman.i18n import _ From jarrell@vt.edu Fri Nov 8 05:54:43 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 08 Nov 2002 00:54:43 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 In-Reply-To: <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> References: <15818.60045.559452.189545@gargle.gargle.HOWL> <200211070003.gA703A1h028267@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20021108005344.04604060@lennier.cc.vt.edu> >>Okay, I just checked in some fixes for this, I believe. See the >>bin/b4b5-archfix script. Do a normal update then run this as >>specified in the docstring (use --help for details). Then run check_perms -f, because b4b5-archfix will step all over your permissions, unless you happen to run it *as* the mailman user... From noreply@sourceforge.net Fri Nov 8 12:13:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 04:13:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color Message-ID: Bugs item #635462, was opened at 2002-11-08 12:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marcin Orlowski (carl-os) Assigned to: Nobody/Anonymous (nobody) Summary: Admin pages HTML does not set TEXT color Initial Comment: Mailman admin pages believe that TEXT color is always black and does not set it to, hoping nobody changes the defaults. And this is false assumption ;-) For testing purposes my defaults are black bg color and yellow text. And since admin pages sets bg to white it now exposes yellow fonts on white background here. Kinda unreadable. Solution -> fix template/css/whatever to set up text color to black. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 From Dale@Newfield.org Fri Nov 8 14:37:24 2002 From: Dale@Newfield.org (Dale Newfield) Date: Fri, 8 Nov 2002 09:37:24 -0500 (EST) Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: Message-ID: On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: > Admin pages HTML does not set TEXT color Why is it mailman's job to protect stupid users from their own browser settings? -Dale From barry@python.org Fri Nov 8 15:32:09 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 8 Nov 2002 10:32:09 -0500 Subject: [Mailman-Developers] hyperarch error w/2.1b4 References: <200211070003.gA703A1h028267@babylon5.cc.vt.edu> <5.1.0.14.2.20021108003211.09fb59b0@lennier.cc.vt.edu> Message-ID: <15819.55545.885253.249455@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> Hey, Barry, or did your testing not include actually *doing* a RJ> -h? :-) RJ> Given that it causes a traceback, because b4b5-archfix is RJ> missing a from Mailman.i18n import _ Fixed, thanks. I also added a nice reminder printed when finished that check_perms should be run. -Barry From noreply@sourceforge.net Fri Nov 8 15:38:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 08 Nov 2002 07:38:48 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError Message-ID: Bugs item #635542, was opened at 2002-11-08 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught MMNoSuchUserError Initial Comment: I found an unsubscribe confirmation message in the shunt directory. The error log suggests that someone used both the web and the reply to unsubscribe, but when the email confirmation arrived, he was already gone and qrunner faulted. I'm running a CVS build about a week old. Here's the traceback: Nov 08 05:29:33 2002 (23820) Uncaught runner exception: Nov 08 05:29:33 2002 (23820) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 199, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 117, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1107, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/mailman/Mailman/MailList.py", line 936, in ApprovedDeleteMember raise Errors.MMNoSuchUserError MMNoSuchUserError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 From jwblist@olympus.net Sat Nov 9 07:43:26 2002 From: jwblist@olympus.net (John W Baxter) Date: Fri, 8 Nov 2002 23:43:26 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color In-Reply-To: References: Message-ID: At 9:37 -0500 11/8/2002, Dale Newfield wrote: >On Fri, 8 Nov 2002 noreply@sourceforge.net wrote: >> Admin pages HTML does not set TEXT color > >Why is it mailman's job to protect stupid users from their own browser >settings? This one sounded like it was posted not from a stupid user but from a careful tester. If mailman has an intended appearance, it should cause that appearance to happen unless the user--in a browser which will--has refused to allow the site to override her local style sheet. Personally, I liked the old days, when the user's browser settings were allowed to control appearance details, and HTML described content. Of course, one could hardly hire out as a "designer" following that idea, so it didn't last long. --John (one of the few who remembers that the first T in HTTP stands for Text) -- John Baxter Port Ludlow, WA USA Always allow for the innate perversity of inanimate matter. From noreply@sourceforge.net Sun Nov 10 21:57:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 13:57:54 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-636363 ] Delete all pending messages Message-ID: Feature Requests item #636363, was opened at 2002-11-10 21:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: Delete all pending messages Initial Comment: Been hunting high and low for a script or patch to go into all my mailing lists and delete all pending posts.. There is one group of spammers who have managed to get ahold of the list email addresses and all the posts come from them.. We also block all HTML email so we have a lot of posts from those people which could be deleted as well. Really would like some kind of commandline utility for doing this, and I don't know python. Just an idea. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 From noreply@sourceforge.net Mon Nov 11 00:39:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 16:39:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Mon Nov 11 00:42:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 16:42:18 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-636363 ] Delete all pending messages Message-ID: Feature Requests item #636363, was opened at 2002-11-10 21:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: Delete all pending messages Initial Comment: Been hunting high and low for a script or patch to go into all my mailing lists and delete all pending posts.. There is one group of spammers who have managed to get ahold of the list email addresses and all the posts come from them.. We also block all HTML email so we have a lot of posts from those people which could be deleted as well. Really would like some kind of commandline utility for doing this, and I don't know python. Just an idea. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-11-11 00:42 Message: Logged In: YES user_id=67709 I hope this script helps; https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636363&group_id=103 From noreply@sourceforge.net Mon Nov 11 01:37:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 10 Nov 2002 17:37:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-11 01:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Mon Nov 11 08:15:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 11 Nov 2002 00:15:12 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636504 ] Configurable absolute URLs for scripts Message-ID: Patches item #636504, was opened at 2002-11-11 09:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636504&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable absolute URLs for scripts Initial Comment: In my Mailman setup I want to use http for some URLs (most of them, including the archives) for less CPU usage on the server, and https on some URLs (login with password, list administration) for better (if not good, since the passwords go in cleartext over mail anyway) security. One way of accomplishing this is to make script URLs absolute, and set DEFAULT_URL to a https hostname. This patch makes it possible to configure if GetScriptURL should by default return an absolute URL using a variable in Default.py/mm_cfg.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636504&group_id=103 From carson@taltos.org Mon Nov 11 14:40:29 2002 From: carson@taltos.org (Carson Gaspar) Date: Mon, 11 Nov 2002 09:40:29 -0500 Subject: [Mailman-Developers] CGI error in latest CVS (2002-11-11) Message-ID: <976800109.1037007629@[192.168.20.2]> I just tried upgrading to the latest CVS (as 2.1b4 had some nasty bugs reported), and got the following when trying to go to an admin page: Bug in Mailman version 2.1b4+ 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 "/Tools/SunOS_5.8_i86pc/mailman-2.1-cvs-20021111/scripts/driver", line 68, in run_main immediate=1) File "/Tools/SunOS_5.8_i86pc/mailman-2.1-cvs-20021111/Mailman/Logging/StampedLog ger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/Tools/SunOS_5.8_i86pc/mailman-2.1-cvs-20021111/Mailman/Logging/Logger.py" , line 49, in __init__ self.__get_f() File "/Tools/SunOS_5.8_i86pc/mailman-2.1-cvs-20021111/Mailman/Logging/Logger.py" , line 68, in __get_f except codecs.LookupError: AttributeError: 'module' object has no attribute 'LookupError' --------------------------------------------------------------------------- ----- Python information: Variable Value sys.version 2.2.1 (#1, Jun 17 2002, 18:08:33) [GCC 3.1] sys.executable /usr/local/bin/python sys.prefix /tools/python sys.exec_prefix /tools/python sys.path /tools/python sys.platform sunos5 --------------------------------------------------------------------------- ----- Environment variables: Variable Value PYTHONPATH /Tools/SunOS_5.8_i86pc/mailman-2.1-cvs-20021111 SCRIPT_FILENAME /tools/mailman/cgi-bin/admindb SERVER_SOFTWARE Apache/2.0.39 (Unix) mod_ssl/2.0.39 OpenSSL/0.9.6d SERVER_ADMIN webmaster@taltos.org SCRIPT_NAME /mailman/admindb SERVER_SIGNATURE REQUEST_METHOD GET HTTP_HOST www.taltos.org PATH_INFO /bluefeather SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_CONNECTION Keep-Alive REQUEST_URI /mailman/admindb/bluefeather HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) TZ US/Eastern SERVER_NAME www.taltos.org REMOTE_ADDR 192.168.20.2 REMOTE_PORT 3985 HTTP_ACCEPT_LANGUAGE en-ca PATH_TRANSLATED /var/apache2/default-site/htdocs/taltos_org/bluefeather SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR 66.93.85.36 DOCUMENT_ROOT /var/apache2/default-site/htdocs/taltos_org From barry@python.org Mon Nov 11 14:51:32 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 11 Nov 2002 09:51:32 -0500 Subject: [Mailman-Developers] CGI error in latest CVS (2002-11-11) References: <976800109.1037007629@[192.168.20.2]> Message-ID: <15823.50164.40272.497736@gargle.gargle.HOWL> Typo. LookupError is builtin. -Barry -------------------- snip snip -------------------- Index: Logger.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Logging/Logger.py,v retrieving revision 2.4 diff -u -r2.4 Logger.py --- Logger.py 17 Sep 2002 21:57:27 -0000 2.4 +++ Logger.py 11 Nov 2002 14:51:09 -0000 @@ -65,7 +65,7 @@ f = codecs.open( self.__filename, 'a+', self.__encoding, 'replace', 1) - except codecs.LookupError: + except LookupError: f = open(self.__filename, 'a+', 1) self.__fp = f finally: From carson@taltos.org Mon Nov 11 16:02:26 2002 From: carson@taltos.org (Carson Gaspar) Date: Mon, 11 Nov 2002 11:02:26 -0500 Subject: [Mailman-Developers] CGI error in latest CVS (2002-11-11) In-Reply-To: <15823.50164.40272.497736@gargle.gargle.HOWL> References: <976800109.1037007629@[192.168.20.2]> <15823.50164.40272.497736@gargle.gargle.HOWL> Message-ID: <981716187.1037012546@[192.168.20.2]> --On Monday, November 11, 2002 9:51 AM -0500 "Barry A. Warsaw" wrote: > Typo. LookupError is builtin. Thanks! Much better - everything looks good so far. -- Carson From noreply@sourceforge.net Tue Nov 12 21:39:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 12 Nov 2002 13:39:36 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-637403 ] remove from multilists. Message-ID: Feature Requests item #637403, was opened at 2002-11-12 21:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637403&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: remove from multilists. Initial Comment: You guys were fantastic with my last request.. here is another one.. I run 7 mailing lists which all revolve around the same topic, just each one is a little different. it is not uncommon for people to sign up on each list. so generally when they have their email bounces or want to be removed it has to be done on every list.. is there a way to or is there a script out there that can basically do like /usr/local/mailman/bin/remove_members * someone@somewhere.com the * meaning all lists. and have it remove that from every list on the system? Just checking, I didn't see it in the help. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637403&group_id=103 From noreply@sourceforge.net Tue Nov 12 21:58:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 12 Nov 2002 13:58:50 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637410 ] autorespond_requests "w/discard" ignored Message-ID: Bugs item #637410, was opened at 2002-11-12 21:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: autorespond_requests "w/discard" ignored Initial Comment: Gui/Autoresponse.py makes a distinction between autorespond_requests == 1 or == 2, but that's implemented in the MailCommandHandler.py module, which is unreferenced in b3 and gone in b4. CommandRunner._dispose could check for this after it calls Replybot.process(), I think. Or if the feature was intentionally left out, it could be left out of the web interface too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_id=103 From noreply@sourceforge.net Wed Nov 13 00:49:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 12 Nov 2002 16:49:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637494 ] typo in README.SENDMAIL (CVS 2.4) Message-ID: Bugs item #637494, was opened at 2002-11-13 01:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: typo in README.SENDMAIL (CVS 2.4) Initial Comment: The README.SENDMAIL section on INTEGRATION has a typo: ...such that Sendmail will automatically recognize and delivery I presume it must be without the "y" in "delivery". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_id=103 From noreply@sourceforge.net Wed Nov 13 00:52:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 12 Nov 2002 16:52:27 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-637403 ] remove from multilists. Message-ID: Feature Requests item #637403, was opened at 2002-11-12 21:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637403&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: remove from multilists. Initial Comment: You guys were fantastic with my last request.. here is another one.. I run 7 mailing lists which all revolve around the same topic, just each one is a little different. it is not uncommon for people to sign up on each list. so generally when they have their email bounces or want to be removed it has to be done on every list.. is there a way to or is there a script out there that can basically do like /usr/local/mailman/bin/remove_members * someone@somewhere.com the * meaning all lists. and have it remove that from every list on the system? Just checking, I didn't see it in the help. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-11-13 00:52 Message: Logged In: YES user_id=10725 --fromall already exists, at least in 2.1b4; that seems like just what you want. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637403&group_id=103 From noreply@sourceforge.net Wed Nov 13 02:40:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 12 Nov 2002 18:40:43 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637531 ] Request: populate Real Name from mail Message-ID: Bugs item #637531, was opened at 2002-11-12 18:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637531&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Request: populate Real Name from mail Initial Comment: It would be nice to have the option of letting Mailman automatically populate the Real Name field of a list's subscribers db from mail headers passing through the system. For example, if no Real Name exists for an email address and a post is received from that address, Mailman can just yank the Real Name (or whatever is supplied) from the mail header (ie From: field, etc). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637531&group_id=103 From noreply@sourceforge.net Wed Nov 13 10:24:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 02:24:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-637686 ] Simple members-in-LDAP support. Message-ID: Patches item #637686, was opened at 2002-11-13 11:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=637686&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Simple members-in-LDAP support. Initial Comment: In an organization where all users are in a LDAP directory, fetching data about members of a mailing list from the directory is sometimes a good idea. For example, in my directory, I can find out all members of a certain organizational unit using a LDAP search. I still want all the other features of Mailman - archives, restrict posting to members, etc.. This patch makes it possible to define a LDAP search URI (RFC2255) in the configuration. When posting to the list, the search is executed and the resulting mail addresses are added to the normal list members. It's configurable on a per-installation-level if the ldap search configuration should be displayed. The python-ldap module is needed in order for this to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=637686&group_id=103 From noreply@sourceforge.net Wed Nov 13 13:08:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 05:08:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637747 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637747, was opened at 2002-11-13 16:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 From noreply@sourceforge.net Wed Nov 13 13:08:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 05:08:28 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637748 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637748, was opened at 2002-11-13 16:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637748&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637748&group_id=103 From noreply@sourceforge.net Wed Nov 13 14:18:51 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 06:18:51 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637747 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637747, was opened at 2002-11-13 08:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) >Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 09:18 Message: Logged In: YES user_id=12800 Oleg, have you tried this with MM2.1? I think there's code in there that tries to decode the header first before searching for the prefix. I'm not surprised MM2.0 doesn't do the right thing, but MM2.1 should. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 From noreply@sourceforge.net Wed Nov 13 14:29:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 06:29:14 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637747 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637747, was opened at 2002-11-13 16:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) >Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2002-11-13 17:29 Message: Logged In: YES user_id=4799 Mailman 2.1 is still in beta. I don't dare to recommend it to sysadmins - these are not my mailing lists, nor my hosts. But it's good to know there is a fix. I'll give it a try when you release 2.1-final. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 17:18 Message: Logged In: YES user_id=12800 Oleg, have you tried this with MM2.1? I think there's code in there that tries to decode the header first before searching for the prefix. I'm not surprised MM2.0 doesn't do the right thing, but MM2.1 should. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 From noreply@sourceforge.net Wed Nov 13 14:29:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 06:29:33 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637747 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637747, was opened at 2002-11-13 16:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) >Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2002-11-13 17:29 Message: Logged In: YES user_id=4799 Mailman 2.1 is still in beta. I don't dare to recommend it to sysadmins - these are not my mailing lists, nor my hosts. But it's good to know there is a fix. I'll give it a try when you release 2.1-final. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2002-11-13 17:29 Message: Logged In: YES user_id=4799 Mailman 2.1 is still in beta. I don't dare to recommend it to sysadmins - these are not my mailing lists, nor my hosts. But it's good to know there is a fix. I'll give it a try when you release 2.1-final. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 17:18 Message: Logged In: YES user_id=12800 Oleg, have you tried this with MM2.1? I think there's code in there that tries to decode the header first before searching for the prefix. I'm not surprised MM2.0 doesn't do the right thing, but MM2.1 should. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 From blair@orcaware.com Wed Nov 13 16:19:43 2002 From: blair@orcaware.com (Blair Zajac) Date: Wed, 13 Nov 2002 08:19:43 -0800 Subject: [Mailman-Developers] no digest buttons on mailman-announce web page Message-ID: <3DD27B9F.2037DDD3@orcaware.com> Hi, Just checked the web page http://mail.python.org/mailman/listinfo/mailman-announce and where it says: "Would you like to receive list mail batched in a daily digest? No Yes" there are no radio buttons. The web page http://mail.python.org/mailman/listinfo/mailman-users does have then. Best, Blair -- Blair Zajac Web and OS performance plots - http://www.orcaware.com/orca/ From noreply@sourceforge.net Wed Nov 13 16:40:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 08:40:08 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634109 ] Decode text parts in multipart messages Message-ID: Patches item #634109, was opened at 2002-11-05 17:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634109&group_id=103 Category: Pipermail >Group: Mailman 2.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Martin v. Löwis (loewis) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Decode text parts in multipart messages Initial Comment: This patch improves the processing in multipart messages, in particular multipart/alternative. It does so by concatenating all text/plain parts after scrubbing (scrubbing should only leave text/plain parts), and replacing the type of the original multipart message with text/plain. Concatenation of the text parts tries to recode everything into the "main" encoding, which is the encoding of the text/plain part. This could be improved by recoding everything to UTF-8 if switching the main encoding to UTF-8 if some part cannot be recoded to the main encoding. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 11:40 Message: Logged In: YES user_id=12800 I like this patch and plan to apply it, after minor tweaks and some testing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634109&group_id=103 From noreply@sourceforge.net Wed Nov 13 17:40:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 13 Nov 2002 09:40:41 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634109 ] Decode text parts in multipart messages Message-ID: Patches item #634109, was opened at 2002-11-05 17:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634109&group_id=103 Category: Pipermail Group: Mailman 2.1 >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Decode text parts in multipart messages Initial Comment: This patch improves the processing in multipart messages, in particular multipart/alternative. It does so by concatenating all text/plain parts after scrubbing (scrubbing should only leave text/plain parts), and replacing the type of the original multipart message with text/plain. Concatenation of the text parts tries to recode everything into the "main" encoding, which is the encoding of the text/plain part. This could be improved by recoding everything to UTF-8 if switching the main encoding to UTF-8 if some part cannot be recoded to the main encoding. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 12:40 Message: Logged In: YES user_id=12800 Applied to Scrubber.py 2.16 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 11:40 Message: Logged In: YES user_id=12800 I like this patch and plan to apply it, after minor tweaks and some testing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634109&group_id=103 From chuqui@plaidworks.com Wed Nov 13 18:10:30 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Wed, 13 Nov 2002 10:10:30 -0800 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... Message-ID: <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> Having run with the personalization for a while (and only now getting around to updating to CVS so I can turn off the header mods), I have three reasons why doing the to/from personalization turn out to be a bad idea.. FYI. 1) One of my lists has been hit badly by a couple of subscribers with the Klez virus that evidently didn't know it and weren't fixing their machines. I finally posted a note to the list telling everyone to check their frigging machines and to run anti-virus software, because if I had to track down the sites sending the viruses to the list, those sites would be banned (FWIW, I did end up putting IP blocks against two sites, which stopped most of the noise). One subscriber, a few days later, wrote back to me demanding a personal apology on the list. She thought that since her name was in the "to" line, I'd accused HER PERSONALLY of being virus ridden on the list. I nicely pointed out that if she looked at any message sent through the list over the last few weeks, they all were formatted that way, and that I didn't see that an apology was necessary. she hasn't responded to that message. 2) I'm learning just how many people write vacation bots that filter responses based on assumptions of what the To/CC lines will say. I know they're not supposed to do that. I tell them that. But a lot of people do, and so a lot of "I'm out of the office" blats are going out to people posting to mailing lists because of it. 3) I can't prove this, but... Since I went to To/From header personalization, I've started getting complaints about mail not getting to AOL users. It's intermittent. My logs clearly show AOL accepting the mail. And then it -- disappears. So it looks like something about those headers makes AOL suspicious. I had a fair number of complaints just after the upgrade which I took to either being confusion causd by the header changes or AOL not catching things right, and then it more or less went away, but now, I'm again seeing occasional complaints from people who I don't think are confused or mistaken. So it looks like that to/from combo isn't totally compatible with whatever AOL is doing as far as spam sniffing. FWIW. I'm turning it back off, because the feedback I've gotten from users has been generally pretty negative. message personalization seems to be a good thing, but those header changes just didn't go over with my users, and I've given it extra time to make sure it's not just a case of "new and different, therefore icky". -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Very funny, Scotty. Now beam my clothes down here, will you? From barry@python.org Wed Nov 13 18:45:40 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 13 Nov 2002 13:45:40 -0500 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... References: <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> Message-ID: <15826.40404.915878.880717@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> I'm turning it back off, because the feedback I've gotten CVR> from users has been generally pretty negative. message CVR> personalization seems to be a good thing, but those header CVR> changes just didn't go over with my users, and I've given it CVR> extra time to make sure it's not just a case of "new and CVR> different, therefore icky". Thanks for the feedback Chuq. That's the first real data point we can go by, so it's greatly appreciated. BTW, were those discussion or announce lists? I suspect that an announce list might be the only place where header personalization might still be appropriate (but only "might"). -Barry From chuqui@plaidworks.com Wed Nov 13 18:54:11 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Wed, 13 Nov 2002 10:54:11 -0800 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... In-Reply-To: <15826.40404.915878.880717@gargle.gargle.HOWL> Message-ID: <4C300D7C-F739-11D6-B6BE-0003934516A8@plaidworks.com> On Wednesday, November 13, 2002, at 10:45 AM, Barry A. Warsaw wrote: > BTW, were those discussion or announce lists? I suspect that an > announce list might be the only place where header personalization > might still be appropriate (but only "might"). > all discussion. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ IMHO: Jargon. Acronym for In My Humble Opinion. Used to flag as an opinion something that is clearly from context an opinion to everyone except the mentally dense. Opinions flagged by IMHO are actually rarely humble. IMHO. (source: third unabridged dictionary of chuqui-isms). From bob@nleaudio.com Wed Nov 13 19:30:40 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Wed, 13 Nov 2002 14:30:40 -0500 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... References: <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> Message-ID: <3DD2A860.AFB780E2@nleaudio.com> > 3) I can't prove this, but... Since I went to To/From header > personalization, I've started getting complaints about mail not getting > to AOL users. It's intermittent. My logs clearly show AOL accepting the > mail. And then it -- disappears. Actually, I've experienced exactly the opposite. In fact, you'll see a number of spam filters that will specifically reject messages that are not TO: the destination person, ignoring the envelope. I've had three cases of AOL users rejecting mail from my lists because I don't have personalization. Bob From sb.list@sb.org Wed Nov 13 19:35:30 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Wed, 13 Nov 2002 14:35:30 -0500 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... In-Reply-To: <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> Message-ID: On 11/13/02 1:10 PM, "Chuq Von Rospach" wrote: > I'm turning it back off, because the feedback I've gotten from users > has been generally pretty negative. message personalization seems to be > a good thing, but those header changes just didn't go over with my > users, and I've given it extra time to make sure it's not just a case > of "new and different, therefore icky". Are you keeping the Reply-to personalization and just turning off the To munging? - Stoney From chuqui@plaidworks.com Wed Nov 13 19:44:42 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Wed, 13 Nov 2002 11:44:42 -0800 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... In-Reply-To: Message-ID: <5A7FEB0E-F740-11D6-B6BE-0003934516A8@plaidworks.com> On Wednesday, November 13, 2002, at 11:35 AM, Stonewall Ballard wrote: > Are you keeping the Reply-to personalization and just turning off the > To > munging? > I'm turning off the to/cc re-arranging. I don't coerce reply-to anyway, so that shouldn't change. > -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek From claw@kanga.nu Wed Nov 13 22:06:38 2002 From: claw@kanga.nu (J C Lawrence) Date: Wed, 13 Nov 2002 14:06:38 -0800 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... In-Reply-To: Message from Chuq Von Rospach <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> References: <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> Message-ID: <26696.1037225198@kanga.nu> On Wed, 13 Nov 2002 10:10:30 -0800 Chuq Von Rospach wrote: > Having run with the personalization for a while (and only now getting > around to updating to CVS so I can turn off the header mods), I have > three reasons why doing the to/from personalization turn out to be a > bad idea.. FYI. I'd narrow that statement to: "...a Bad Idea for discussion lists." It would seem to remain useful for announcement and marketing list. > 1) One of my lists has been hit badly by a couple of subscribers with > the Klez virus that evidently didn't know it and weren't fixing their > machines. I finally posted a note to the list telling everyone to > check their frigging machines and to run anti-virus software, because > if I had to track down the sites sending the viruses to the list, > those sites would be banned (FWIW, I did end up putting IP blocks > against two sites, which stopped most of the noise). FWVLIW I avoid the problem (and the moderation/list load) by stripping those MIME parts and then silently discarding messages which are too short after stripping (ie nothing left after offensive payload removed). Very little gets past that. Another approach of course is to front your list with a virus stripper. > 3) I can't prove this, but... Since I went to To/From header > personalization, I've started getting complaints about mail not > getting to AOL users. Yeah, this is not terribly surprising. I suspect you're running afoul of their SPAM filters and Mailman's new header personalisation is hitting a corner case in their dupe filters (personally addressed now being common). -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From andrew.clark@ucsb.edu Wed Nov 13 22:39:19 2002 From: andrew.clark@ucsb.edu (Andrew D. Clark) Date: Wed, 13 Nov 2002 14:39:19 -0800 Subject: [Mailman-Developers] next release? Message-ID: <24940000.1037227159@minimod.oit.ucsb.edu> I'm wondering how soon I might expect Mailman2.1b5 (or 2.1 final!) to be cut loose. I'm running 2.1b3 and, AFAIK, the bugs I'm looking to have fixed (poor archrunner performance, esp) aren't fixed in 2.1b4, but I'm a bit leery of a CVS build on a production mailing list system. Can Barry, or anyone else, supply me with a realistic ETA? -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark@ucsb.edu (805) 893-5311 From barry@python.org Wed Nov 13 22:41:42 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 13 Nov 2002 17:41:42 -0500 Subject: [Mailman-Developers] next release? References: <24940000.1037227159@minimod.oit.ucsb.edu> Message-ID: <15826.54566.238151.238257@gargle.gargle.HOWL> >>>>> "ADC" == Andrew D Clark writes: ADC> I'm wondering how soon I might expect Mailman2.1b5 (or 2.1 ADC> final!) to be cut loose. I'm running 2.1b3 and, AFAIK, the ADC> bugs I'm looking to have fixed (poor archrunner performance, ADC> esp) aren't fixed in 2.1b4, but I'm a bit leery of a CVS ADC> build on a production mailing list system. Can Barry, or ADC> anyone else, supply me with a realistic ETA? Unless unforseen circumstances arise, 2.1b5 by the end of this week. BTW, I usually run current cvs on my personal domains, and very nearly cvs on python.org, so if there's a serious regression in cvs, I usually find out about it pretty quickly. -Barry From chuqui@plaidworks.com Wed Nov 13 22:54:01 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Wed, 13 Nov 2002 14:54:01 -0800 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... In-Reply-To: <26696.1037225198@kanga.nu> Message-ID: On Wednesday, November 13, 2002, at 02:06 PM, J C Lawrence wrote: > > I'd narrow that statement to: "...a Bad Idea for discussion lists." It > would seem to remain useful for announcement and marketing list. true. >> those sites would be banned (FWIW, I did end up putting IP blocks >> against two sites, which stopped most of the noise). > > FWVLIW I avoid the problem (and the moderation/list load) by stripping > those MIME parts and then silently discarding messages which are too > short after stripping (ie nothing left after offensive payload > removed). > Very little gets past that. > > Another approach of course is to front your list with a virus stripper. sorry, but there's the issue of solving my problem, and the bigger issue of getting these people to fix their stupid machines. it's fairly trivial to make that stuff a non-issue for me personally, but those things don't do much for the larger issue of convincing people to rmeove the viruses from their stupid computers. IP blocks are one way of getting their attention, or at least trying, by denying them access to something they evidently want. Which will hopefully ocnovince them to get their act together and quit spreading viruses amongst all of their friends and neighbors. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Yes, I am an agent of Satan, but my duties are largely ceremonial. From dan.mick@sun.com Wed Nov 13 23:21:09 2002 From: dan.mick@sun.com (Dan Mick) Date: Wed, 13 Nov 2002 15:21:09 -0800 Subject: [Mailman-Developers] next release? In-Reply-To: <24940000.1037227159@minimod.oit.ucsb.edu> References: <24940000.1037227159@minimod.oit.ucsb.edu> <15826.54566.238151.238257@gargle.gargle.HOWL> Message-ID: <3DD2DE65.3000304@sun.com> > > BTW, I usually run current cvs on my personal domains, and very nearly > cvs on python.org, so if there's a serious regression in cvs, I > usually find out about it pretty quickly. Echoed. I've been current-or-two-days-behind CVS for the last two years now, and happy as a clam most of the time. From barry@python.org Wed Nov 13 23:40:22 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 13 Nov 2002 18:40:22 -0500 Subject: [Mailman-Developers] next release? References: <24940000.1037227159@minimod.oit.ucsb.edu> <15826.54566.238151.238257@gargle.gargle.HOWL> <3DD2DE65.3000304@sun.com> Message-ID: <15826.58086.262365.600664@gargle.gargle.HOWL> >>>>> "DM" == Dan Mick writes: >> BTW, I usually run current cvs on my personal domains, and very >> nearly cvs on python.org, so if there's a serious regression in >> cvs, I usually find out about it pretty quickly. DM> Echoed. I've been current-or-two-days-behind CVS for the last DM> two years now, and happy as a clam most of the time. Hey, I just had an idea. Screw the release. We'll just distribute an "installer" that does an anonymous cvs update. And a cron job that does an update every night. It'll never break! kidding-ly y'rs, -Barry From andrew.clark@ucsb.edu Wed Nov 13 23:45:22 2002 From: andrew.clark@ucsb.edu (Andrew D. Clark) Date: Wed, 13 Nov 2002 15:45:22 -0800 Subject: [Mailman-Developers] next release? In-Reply-To: <15826.58086.262365.600664@gargle.gargle.HOWL> References: <24940000.1037227159@minimod.oit.ucsb.edu> <3DD2DE65.3000304@sun.com> <15826.58086.262365.600664@gargle.gargle.HOWL> Message-ID: <32320000.1037231122@minimod.oit.ucsb.edu> --On Wednesday, November 13, 2002 18:40:22 -0500 "Barry A. Warsaw" wrote: > >>>>>> "DM" == Dan Mick writes: > > >> BTW, I usually run current cvs on my personal domains, and very > >> nearly cvs on python.org, so if there's a serious regression in > >> cvs, I usually find out about it pretty quickly. > > DM> Echoed. I've been current-or-two-days-behind CVS for the last > DM> two years now, and happy as a clam most of the time. > > Hey, I just had an idea. Screw the release. We'll just distribute an > "installer" that does an anonymous cvs update. And a cron job that > does an update every night. It'll never break! except when it does :) -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark@ucsb.edu (805) 893-5311 From jarrell@vt.edu Wed Nov 13 23:45:13 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Wed, 13 Nov 2002 18:45:13 -0500 Subject: [Mailman-Developers] next release? In-Reply-To: <3DD2DE65.3000304@sun.com> References: <24940000.1037227159@minimod.oit.ucsb.edu> <24940000.1037227159@minimod.oit.ucsb.edu> <15826.54566.238151.238257@gargle.gargle.HOWL> Message-ID: <5.1.0.14.2.20021113184422.09392d40@lennier.cc.vt.edu> At 03:21 PM 11/13/02 -0800, you wrote: >>BTW, I usually run current cvs on my personal domains, and very nearly >>cvs on python.org, so if there's a serious regression in cvs, I >>usually find out about it pretty quickly. > > >Echoed. I've been current-or-two-days-behind CVS for the last two years now, and happy as a clam most of the time. Yup. Although I learned to wait for at least three hours to go by with silence when Barry starts one of his commit-storms :-). From barry@python.org Wed Nov 13 23:48:55 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 13 Nov 2002 18:48:55 -0500 Subject: [Mailman-Developers] next release? References: <24940000.1037227159@minimod.oit.ucsb.edu> <15826.54566.238151.238257@gargle.gargle.HOWL> <5.1.0.14.2.20021113184422.09392d40@lennier.cc.vt.edu> Message-ID: <15826.58599.155926.830140@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> Yup. Although I learned to wait for at least three hours to RJ> go by with silence when Barry starts one of his commit-storms RJ> :-). LOL! From carson@taltos.org Thu Nov 14 11:04:06 2002 From: carson@taltos.org (Carson Gaspar) Date: Thu, 14 Nov 2002 06:04:06 -0500 Subject: [Mailman-Developers] next release? In-Reply-To: <15826.54566.238151.238257@gargle.gargle.HOWL> References: <24940000.1037227159@minimod.oit.ucsb.edu> <15826.54566.238151.238257@gargle.gargle.HOWL> Message-ID: <1229014343.1037253846@[192.168.20.2]> --On Wednesday, November 13, 2002 5:41 PM -0500 "Barry A. Warsaw" wrote: > BTW, I usually run current cvs on my personal domains, and very nearly > cvs on python.org, so if there's a serious regression in cvs, I > usually find out about it pretty quickly. He fixed my "2.1b4 has nasty bugs, so I guess I'll run CVS" bug in under 5 minutes . YMMV ;-) -- Carson From goofrider303@yahoo.com Tue Nov 12 13:05:35 2002 From: goofrider303@yahoo.com (Jeff da Goofrider) Date: Tue, 12 Nov 2002 05:05:35 -0800 (PST) Subject: [Mailman-Developers] Wishlist: GUI reader Message-ID: <20021112130535.39240.qmail@web9406.mail.yahoo.com> Is there any exisiting effort in making a GUI reader for Mailman? Kinda like a Usenet offline newsreader, a GUI Mailman reader can download the GZ archives, cache them, and then allow a user to read and search the lists offline. Just a thought. If I could write it myself, I would. :) - Jeff __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 From marilyn@deliberate.com Wed Nov 6 20:02:36 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Wed, 6 Nov 2002 12:02:36 -0800 (PST) Subject: [Mailman-Developers] mailman and voting Message-ID: Hi, I am the developer of eVote/Clerk, which hooks onto a maillist-server in the alias file and looks for commands in the incoming mail that start with "eVote". These are diverted and parsed by eVote and allow any of the members to poll the group and administer the poll. It has other super-democratic features, like you can change your vote if you change your mind, you can see others' votes (if the poll is initialized as "public"), you can democratically spend budgets. I'm in a sudden panic because I've been running it with majordomo and that's old stuff. The Linux Journal wants to run an article about eVote/Clerk but they want it to be running with Mailman. My deadline is in a few weeks. Theoretically, it should be a simple thing to switch. I don't touch majordomo's code at all. (I wouldn't mind touching Mailman's because I love Python.) I'm hoping that some Mailman expert(s) might be available to help me. Maybe it'll be easy. eVote/Clerk source code is at sourceforge.net, if anyone wants to give it a shot. The current state of the cvs tree is ready for release, even though I have not done an official release of it. Thanks for listening. Marilyn Davis, Ph.D marilyn@deliberate.com -1 650 965-7121 Author of eVote(R)/Clerk http://www.deliberate.com Board of Advisors, National Initiative for Democracy http://www.ni4d.org From rcm@sasaska.net Fri Nov 8 10:45:52 2002 From: rcm@sasaska.net (Rafael Cordones Marcos) Date: Fri, 8 Nov 2002 11:45:52 +0100 Subject: [Mailman-Developers] Translingual Mailing List Functionality In-Reply-To: <200211061407.GAA12071@2pi.org> References: <4600.213.100.45.224.1036509734.squirrel@sasaska.net> <200211061407.GAA12071@2pi.org> Message-ID: <20021108114552.17a34cb7.rcm@sasaska.net> On Wed, 6 Nov 2002 06:07:13 -0800 les@2pi.org (Les Niles) wrote: > I'd be happy to send the code, but am not sure how useful it would > be since most of what you need to implement has to do with adding > user- and list-specific options, which my implementation didn't > deal with at all. Adding such options is pretty easy, though, > because of the nice design of Mailman. Send it then!! Thanks! = = > One thing you don't mention, but which I think you'll need to deal > with, is identifying the source language of each message. That'll > be needed unless senders will register the language in which > they'll be posting and can be counted on to always post in that > language. I've played around a bit with text-based language Yes, my idea was for users to register which language they will be posting in and receiving e-mails in. But you are write, a user may in some occasion decide to post in another language and the software should detect that. > identification. The algorithms do pretty well, even on messages > just a sentence or two in length, but the error rates are on the > order of several percent. (I was looking at distinguishing between > a dozen or so common European languages.) Occassionally mis- > identifying the source language will add an element of randomness > to the whole process, which from my experience last year I can tell > you can be somewhat amusing. I will take into account. > Another complication will be dealing with HTML-encoded email. If > the translating engine itself can handle HTML, great, otherwise > you'll probably need to strip or convert the HTML parts, to just > translate and produce plain text. In fact, the way I see it I will either way have to deal with chuncks of e-mails. For example, User A writes the following e-mail *in* Language English: I have two questions: 1.- How do I print a string in Python? 2.- Are we alone in the galaxy? = Thanks for your answers, /User A User B (who has chosen to receive all e-mails from the list in Spanish gets the translation and answers like: User A escribi=F3: > 1.- =BFC=F3mo imprimo una cadena de car=E1cteres en Python? tmp_string =3D "Hello, world!"; string.print(tmp_string); = > 2.- =BFEstamos solos en la galaxia? =A1Pues la verdad es que esta es una pregunta complicada de resolver! > Gracias por sus respuestas, =A1De nada! /User B = User A should receive *not the translation* of the previous e-mail back to English but only what User B added in Spanish translated to English. That is, User A should receive the pieces of her original e-mail with the answers (translated to English) of User B. This gets much more complicated when User C (using Chinese) writes to both A and B telling them that User B's answer to the first question is plain wrong. To begin with, in Python we do not use ";" to end a line. Well, maybe, I am talking nonsense here but what I am aiming is at extending Mailman so it could be possible (in the long future) to merge, for instance, debian-users-* into a single list. Insted of having separate mailing lists for different languages, having just one. Thanks for your time! /rafa > On Tue, 5 Nov 2002 16:22:14 +0100 (CET) "Rafael Cordones Marcos" > wrote: > >Hi folks, > > > >I have been searching the Mailman website and have not found any > >reference to what I am looking for, i.e. translating e-mail. I am not > >talking about translating the Mailman software or documentation > >(i18n) but translating the e-mails that people send to the mailing > >list. > > > >I am looking for the following functionality in a mailing list > >software: > > > > - As an administrator: > > > > - set up some default machine translation (MT) engine. > > For example, I want to use Babelfish for translating between > > English > >and Spanish but I wat to use some other engine for > > translating between German and Swedish. > > > > - specify the subject of the mailing list and thus improving the > > translation results. For instance, I can specify that the > > mailing list is about "Technical -> Operating Systems -> Minix" > >(just kidding). > > > > - As a user: > > > > - I want to subscribe to the mailing list and specify my > > language (natural) language preferences. Say I want specify > > {Catalan, Spanish, German}. > > > > - e-mail going to the list gets sent to a machine translation > > before it gets sent to me. I can optionaly say to the > > mailing list software that I want to receive also the original > > message. > > > > - If I do not like the translation of an e-mail I can choose some > > other machine translation engine. I may decide that some other > >translation engine does a better job or even pay to get > > get better translations. Maybe the administrator forgot to > > specify a machine translation engine for Euskera<->Farsi and I > > know > >of one that just started operating. > > > >I would appreciate any information you may have on this topic. Maybe > >somebody has started implementing this in Mailman or is already > >implemented? Send me any comments, problems you see on the > >aforementioned working schema, flames, ... > > > >Thanks a lot for your time! > > > >Rafa From gward@python.net Thu Nov 14 21:35:51 2002 From: gward@python.net (Greg Ward) Date: Thu, 14 Nov 2002 16:35:51 -0500 Subject: [Mailman-Developers] Wishlist: GUI reader In-Reply-To: <20021112130535.39240.qmail@web9406.mail.yahoo.com> References: <20021112130535.39240.qmail@web9406.mail.yahoo.com> Message-ID: <20021114213551.GA4989@cthulhu.gerg.ca> On 12 November 2002, Jeff da Goofrider said: > Is there any exisiting effort in making a GUI reader > for Mailman? Kinda like a Usenet offline newsreader, a > GUI Mailman reader can download the GZ archives, cache > them, and then allow a user to read and search the > lists offline. Sure, it's called "your mail reader". Mailman's archives are stored in mbox format, which is the bog-standard format for Unix mailboxes. As long as the Mailman server in question lets you download the mbox archive, you're in business. Greg -- Greg Ward http://www.gerg.ca/ I had a ploughman's lunch the other day. He wasn't very happy. From tkikuchi@is.kochi-u.ac.jp Fri Nov 15 04:11:53 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 15 Nov 2002 13:11:53 +0900 Subject: [Mailman-Developers] next release? References: <24940000.1037227159@minimod.oit.ucsb.edu> <15826.54566.238151.238257@gargle.gargle.HOWL> Message-ID: <3DD47409.4090504@is.kochi-u.ac.jp> Barry A. Warsaw wrote: > Unless unforseen circumstances arise, 2.1b5 by the end of this week. FYI, JapaneseCodecs 1.4.9 was released on October 8. http://ftp.python.jp/pub/JapaneseCodecs/JapaneseCodecs-1.4.9.tar.gz -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From chuqui@plaidworks.com Fri Nov 15 08:47:53 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Fri, 15 Nov 2002 00:47:53 -0800 Subject: [Mailman-Developers] thinking out loud... Message-ID: Take a look at this: http://philringnalda.com/archives/002388.php doesn't this idea (baked vs. fried) seem to be a perfect setup for mailing list archives? one of my big frustrations with mhonarc is it builds all of the archives every time you update a file or add a message, and changing your look and feel is a horrendous problem. Lots of CPU goes to maknig stuff ready in case someone wants something. Wouldn't archives make more sense doing a "build when requested" model instead? -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ The Cliff's Notes Cliff's Notes on Hamlet: And they all died happily ever after From fil@rezo.net Fri Nov 15 09:24:39 2002 From: fil@rezo.net (Fil) Date: Fri, 15 Nov 2002 10:24:39 +0100 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: References: Message-ID: <20021115092439.GH13762@rezo.net> > one of my big frustrations with mhonarc is it builds all of the > archives every time you update a file or add a message, and changing > your look and feel is a horrendous problem. Lots of CPU goes to maknig > stuff ready in case someone wants something. > > Wouldn't archives make more sense doing a "build when requested" model > instead? Absolutely; even better, maybe, store the messages in a database for fast ("on the fly") index generation. -- Fil From barry@python.org Fri Nov 15 14:26:29 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 15 Nov 2002 09:26:29 -0500 Subject: [Mailman-Developers] thinking out loud... References: Message-ID: <15829.1045.321151.899084@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> Wouldn't archives make more sense doing a "build when CVR> requested" model instead? +1. I wonder if you couldn't largely acheive those results by fronting your archive w/ squid (he says, having never set up a squid server). Say your archives are always built on demand, but squid thinks they're static and feeds them out if they're in its cache. To regen from scratch you blow away the cache and let it warm up again. -Barry From mss@mawhrin.net Fri Nov 15 14:48:13 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Fri, 15 Nov 2002 14:48:13 +0000 Subject: [Mailman-Developers] import errors In-Reply-To: <20021105194722.GA2861@mawhrin.net> References: <20021105153032.GA1726@mawhrin.net> <15815.61760.108530.197276@gargle.gargle.HOWL> <20021105194722.GA2861@mawhrin.net> Message-ID: <20021115144813.GA10919@mawhrin.net> I still have those problems (I had to put the whole thing aside for a couple of weeks). What I have: up-to-date (as of now) cvs version of Mailman checked out Debian Linux system (unstable) python2.2 installed on it The problem: While starting the mailman (mailmanctl -s -q start) I receive a whole lot of the error messages like these: Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] 'import site' failed; use -v for traceback What I did: Run strace (strace -ff python2.2 mailmanctl -s -q start) It looks like qrunner's processes do not have the proper os.path as they are unable to find os.py{,c} file: stat64("/usr/local/sbin/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) stat64("/usr/local/bin/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) stat64("/usr/sbin/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) stat64("/usr/bin/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) stat64("/sbin/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) stat64("/bin/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) stat64("/usr/bin/X11/qrunner", 0xbffff834) = -1 ENOENT (No such file or directory) getcwd("/var/home/mailman", 1024) = 18 readlink("/var/home/mailman/", 0xbffff430, 1024) = -1 EINVAL (Invalid argument) stat64("/var/home/mailman/Modules/Setup", 0xbffff378) = -1 ENOENT (No such file or directory) stat64("/var/home/mailman/lib/python2.2/os.py", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/var/home/mailman/lib/python2.2/os.pyc", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/var/home/lib/python2.2/os.py", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/var/home/lib/python2.2/os.pyc", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/var/lib/python2.2/os.py", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/var/lib/python2.2/os.pyc", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/home/packages/python2.2/python2.2-2.2.2/debian/tmp/usr/lib/python2.2/os.py", 0xbffff2e8) = -1 ENOENT (No such file or directory) stat64("/home/packages/python2.2/python2.2-2.2.2/debian/tmp/usr/lib/python2.2/os.pyc", 0xbffff2e8) = -1 ENOENT (No such file or directory) write(2, "Could not find platform independ"..., 55) = 55 (python installed files are in /usr/lib/python2.2) What to do: That's, actually, the question. :) I did reinstall mailman, but this did not help. Thank you in advance, -- Misha -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021115/2bd8b8fd/attachment.bin From barry@python.org Fri Nov 15 15:32:05 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 15 Nov 2002 10:32:05 -0500 Subject: [Mailman-Developers] import errors References: <20021105153032.GA1726@mawhrin.net> <15815.61760.108530.197276@gargle.gargle.HOWL> <20021105194722.GA2861@mawhrin.net> <20021115144813.GA10919@mawhrin.net> Message-ID: <15829.4981.430887.31626@gargle.gargle.HOWL> >>>>> "MS" == Mikhail Sobolev writes: | Could not find platform independent libraries | Could not find platform dependent libraries | Consider setting $PYTHONHOME to [:] | 'import site' failed; use -v for traceback Re-installing Mailman won't help because this is a Python problem. By try doing the following: % python2.2 -v [long spew...look for errors] >>> import site >>> site.__file__ '/usr/local/lib/python2.2/site.pyc' >>> ^D [long spew...look for errors] Somewhere in that first long spew of output you should see errors that make it evident where your Python installation is broken. -Barry From slc@publicus.net Fri Nov 15 17:07:34 2002 From: slc@publicus.net (Steven Clift) Date: Fri, 15 Nov 2002 11:07:34 -0600 Subject: [Mailman-Developers] Translingual Mailing List Functionality In-Reply-To: <20021108114552.17a34cb7.rcm@sasaska.net> References: <200211061407.GAA12071@2pi.org> Message-ID: <3DD4D576.21366.4CB94B5@localhost> To further develop your idea you might want to contact that folks that put together JuniorSummit at MIT: http://www.jrsummit.net Back in 1998 they used the lyris e-list server and machine translation to connect hundreds of kids all using different languages. Their general approach was to allow all users to indicate their preferred first language. All posts in a different language were translated with the post in the original language sent along below the translation. Apparently kids figured out how to make this work for them and it was considered a success. I am interested in if anyone knows of similar approaches. With E- Democracy we'd like to host a Spanish-English discussion list using mailman. Steven Clift http://www.publicus.net From chuqui@plaidworks.com Fri Nov 15 17:06:17 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Fri, 15 Nov 2002 09:06:17 -0800 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: <15829.1045.321151.899084@gargle.gargle.HOWL> Message-ID: <8DDB59B7-F8BC-11D6-8EBC-0003934516A8@plaidworks.com> On Friday, November 15, 2002, at 06:26 AM, Barry A. Warsaw wrote: > +1. I wonder if you couldn't largely acheive those results by > fronting your archive w/ squid (he says, having never set up a squid > server). Say your archives are always built on demand, but squid > thinks they're static and feeds them out if they're in its cache. To > regen from scratch you blow away the cache and let it warm up again. > You run into the "how many things do you want to force an admin to build, maintain and rely on"? I won't argue against it, but it's not the way I'd take it. I'd rather stuff things into a database and build static pages out of them as requested. Or perhaps a better way would be to store messages static, meta-data in a database, and build indexes on the fly, since the messages won't change.... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From spacey-mailman@lenin.nu Fri Nov 15 17:48:11 2002 From: spacey-mailman@lenin.nu (Peter C. Norton) Date: Fri, 15 Nov 2002 09:48:11 -0800 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: <15829.1045.321151.899084@gargle.gargle.HOWL> References: <15829.1045.321151.899084@gargle.gargle.HOWL> Message-ID: <20021115174810.GD4290@lenin.nu> On Fri, Nov 15, 2002 at 09:26:29AM -0500, Barry A. Warsaw wrote: > +1. I wonder if you couldn't largely acheive those results by > fronting your archive w/ squid (he says, having never set up a squid > server). Say your archives are always built on demand, but squid > thinks they're static and feeds them out if they're in its cache. To > regen from scratch you blow away the cache and let it warm up again. Squid probably isn't the tool to do this right. Its a good web cache, but its only really good at saving pages. Literally blowing away the squid cache is a time-consuming process. Its designed around being long-lived, and it usually contains in the order of a few thousand files that need to be unlinked. For a small cache. Also, since to force caching of pages you'd have to force the cache to ignore if-modified-since headers and date heders, you lose the normal method to expire an object from the cache. Using a database of some kind is probably a more flexible idea, and more possible to implement sanely. -Peter -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. From fil@rezo.net Fri Nov 15 20:14:04 2002 From: fil@rezo.net (Fil) Date: Fri, 15 Nov 2002 21:14:04 +0100 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: <8DDB59B7-F8BC-11D6-8EBC-0003934516A8@plaidworks.com> References: <15829.1045.321151.899084@gargle.gargle.HOWL> <8DDB59B7-F8BC-11D6-8EBC-0003934516A8@plaidworks.com> Message-ID: <20021115201404.GH8084@rezo.net> > Or perhaps a better way would be to store messages static, > meta-data in a database, and build indexes on the fly, since the > messages won't change.... Why shouldn't the messages change? People have the right to send me an email saying "please delete my name from the archives" - usually it's their telephone number, or their employer's domain name ;) So, suppose the master file is the mbox: you just need a script to scan it and output whatever is needed. What's wrong with that approach? CPU? Then keep the metadata in a cache (pickle) file, and check its mtime against the mbox mtime. The webscript should issue the correct expiration dates (ie not the mbox mtime). I don't think reading an mbox will take that long on modern servers, especially if you know where to get the contents you need. Then you have it: no database to maintain, minimal disk footprint, no big script. Just one tiny script that echoes your mailbox content. Like IMAP: it just works. If it becomes too heavy, add a cache. It could well prove less heavy than to regenerate all indexes for each incoming mail. And much much more handy... I'd try a go at it, but that would have to be php or perl ;-( -- Fil From gward@python.net Fri Nov 15 21:06:47 2002 From: gward@python.net (Greg Ward) Date: Fri, 15 Nov 2002 16:06:47 -0500 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: <20021115201404.GH8084@rezo.net> References: <15829.1045.321151.899084@gargle.gargle.HOWL> <8DDB59B7-F8BC-11D6-8EBC-0003934516A8@plaidworks.com> <20021115201404.GH8084@rezo.net> Message-ID: <20021115210647.GA7475@cthulhu.gerg.ca> On 15 November 2002, Fil said: > I'd try a go at it, but that would have to be php or perl ;-( Umm, it *is* possible to do web development in Python, you know. ;-) I'm partial to Quixote myself: www.mems-exchange.org/software/quixote/ . Greg -- Greg Ward http://www.gerg.ca/ A hairstyle's not a lifestyle / Imagine Sid Vicious at 35 -- Dead Kennedys From bjoernk@gmx.net Fri Nov 15 21:46:40 2002 From: bjoernk@gmx.net (bjoernk@gmx.net) Date: Fri, 15 Nov 2002 22:46:40 +0100 (MET) Subject: [Mailman-Developers] CVS update Message-ID: <2182.1037396800@www21.gmx.net> Hello! I would like to make an update via CVS to my Mailman 2.1b4 production system. I tried the following: "cvs -d:pserver:anonymous@cvs.mailman.sourceforge.net:/cvsroot/mailman login" and then simply hit "enter". Then, I tried to use the following command: "cvs update" and then CVS tells me: no CVSROOT set. What path shall I use? Thanks for your help! BJ -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! From gward@python.net Fri Nov 15 21:55:32 2002 From: gward@python.net (Greg Ward) Date: Fri, 15 Nov 2002 16:55:32 -0500 Subject: [Mailman-Developers] CVS update In-Reply-To: <2182.1037396800@www21.gmx.net> References: <2182.1037396800@www21.gmx.net> Message-ID: <20021115215532.GA7684@cthulhu.gerg.ca> On 15 November 2002, bjoernk@gmx.net said: > I would like to make an update via CVS to my Mailman 2.1b4 production > system. I tried the following: > > "cvs -d:pserver:anonymous@cvs.mailman.sourceforge.net:/cvsroot/mailman > login" > > and then simply hit "enter". > > Then, I tried to use the following command: > > "cvs update" > > and then CVS tells me: no CVSROOT set. What path shall I use? You can't update until you have checked out. The correct sequence is cvs -d ... login cvs -d ... checkout mailman [... time passes, changes get checked in ...] cd mailman && cvs update Note that the argument you passed to -d needs to be repeated for the 'checkout' command! Greg -- Greg Ward http://www.gerg.ca/ A closed mouth gathers no foot. From barry@python.org Fri Nov 15 21:58:44 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 15 Nov 2002 16:58:44 -0500 Subject: [Mailman-Developers] CVS update References: <2182.1037396800@www21.gmx.net> Message-ID: <15829.28180.893584.423796@gargle.gargle.HOWL> >>>>> "bjoernk" == writes: bjoernk> Then, I tried to use the following command: bjoernk> "cvs update" bjoernk> and then CVS tells me: no CVSROOT set. What path shall I bjoernk> use? You need to provide the -d option on both the login and the initial co commands. Once you have a working directory with CVS subdirs, you don't need the -d any more. -Barry From bjoernk@gmx.net Fri Nov 15 22:00:52 2002 From: bjoernk@gmx.net (bjoernk@gmx.net) Date: Fri, 15 Nov 2002 23:00:52 +0100 (MET) Subject: [Mailman-Developers] CVS update References: <20021115215532.GA7684@cthulhu.gerg.ca> Message-ID: <17617.1037397652@www41.gmx.net> Greg, > You can't update until you have checked out. The correct sequence is > > cvs -d ... login > cvs -d ... checkout mailman > [... time passes, changes get checked in ...] > cd mailman && cvs update > > Note that the argument you passed to -d needs to be repeated for the > 'checkout' command! Thanks, Greg. But how do I know CVS is going to checkout the right Mailman version? Don't I have to tell CVS my CVSROOT in order to make it clear that it checks out Mailman Version 2.1b4 instead of the old Version 2.0.x ? It is a production system, so I just want to make sure everything is gonna be fine after that .... ;-)) Thanks for you help. BJ -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! From barry@python.org Fri Nov 15 22:05:04 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 15 Nov 2002 17:05:04 -0500 Subject: [Mailman-Developers] CVS update References: <20021115215532.GA7684@cthulhu.gerg.ca> <17617.1037397652@www41.gmx.net> Message-ID: <15829.28560.685709.133692@gargle.gargle.HOWL> >>>>> "bjoernk" == writes: bjoernk> Thanks, Greg. But how do I know CVS is going to checkout bjoernk> the right Mailman version? Don't I have to tell CVS my bjoernk> CVSROOT in order to make it clear that it checks out bjoernk> Mailman Version 2.1b4 instead of the old Version 2.0.x ? By default, cvs always checks out the trunk of the tree, unless you provide a -r option to check out a specific tag or branch. My development style is for all development of the next version to happen on the trunk, so with no -r you'll get my latest code. It ought to be stable, modulo bugs , or unfortunate timing of doing an update during a checkin storm. -Barry From gward@python.net Fri Nov 15 22:05:55 2002 From: gward@python.net (Greg Ward) Date: Fri, 15 Nov 2002 17:05:55 -0500 Subject: [Mailman-Developers] CVS update In-Reply-To: <17200.1037397636@www41.gmx.net> References: <20021115215532.GA7684@cthulhu.gerg.ca> <17200.1037397636@www41.gmx.net> Message-ID: <20021115220554.GB7461@cthulhu.gerg.ca> [please keep this sort of thing on the public list -- at the very least, it should be archived for future reference. And I'm not the only CVS expert who can help you out.] On 15 November 2002, bjoernk@gmx.net said: > Thanks, Greg. But how do I know CVS is going to checkout the right > Mailman version? Don't I have to tell CVS my CVSROOT in order to make > it clear that it checks out Mailman Version 2.1b4 instead of the old > Version 2.0.x ? CVSROOT has nothing to do with the version you're checking out. CVSROOT just tells CVS which repository to contact. Supplying the -d option is equivalent to setting CVSROOT. As for the version to checkout: the precise rules depend on how a given project manages releases and tags and branches and all that stuff. Most projects I'm familiar with, including Mailman, make the latest development code the trunk of the CVS tree. So when you do "checkout mailman", you're getting the latest bleeding edge code. You have to take special action if you want to checkout the 2.0.x branch. > It is a production system, so I just want to make sure everything is gonna > be fine after that .... ;-)) With all due respect, may I suggest you become a tad more familiar with CVS before running a CVS version of Mailman on a production server? Greg -- Greg Ward http://www.gerg.ca/ A day without sunshine is like night. From bjoernk@gmx.net Fri Nov 15 22:15:50 2002 From: bjoernk@gmx.net (bjoernk@gmx.net) Date: Fri, 15 Nov 2002 23:15:50 +0100 (MET) Subject: [Mailman-Developers] CVS update References: <20021115220554.GB7461@cthulhu.gerg.ca> Message-ID: <5316.1037398550@www41.gmx.net> Thank you all very much for your support! > With all due respect, may I suggest you become a tad more familiar with > CVS before running a CVS version of Mailman on a production server? Actually I just have rarely used CVS up to now... I know... I am a greenhorn. Sorry for that! :) I feel ashamed. BJ -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! From chuqui@plaidworks.com Fri Nov 15 23:03:49 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Fri, 15 Nov 2002 15:03:49 -0800 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: <20021115201404.GH8084@rezo.net> Message-ID: <803E21B3-F8EE-11D6-B243-0003934516A8@plaidworks.com> On Friday, November 15, 2002, at 12:14 PM, Fil wrote: >> Or perhaps a better way would be to store messages static, >> meta-data in a database, and build indexes on the fly, since the >> messages won't change.... > > Why shouldn't the messages change? People have the right to send me an > email > saying "please delete my name from the archives" - usually it's their > telephone number, or their employer's domain name ;) > And ym answer is that you don't unpublish a newspaper. I only modify archives for issues of legal liability. your mileage may vary there... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ The first rule of holes: If you are in one, stop digging. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ He doesn't have ulcers, but he's a carrier. From claw@kanga.nu Fri Nov 15 23:41:45 2002 From: claw@kanga.nu (J C Lawrence) Date: Fri, 15 Nov 2002 15:41:45 -0800 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: Message from Chuq Von Rospach <803E21B3-F8EE-11D6-B243-0003934516A8@plaidworks.com> References: <803E21B3-F8EE-11D6-B243-0003934516A8@plaidworks.com> Message-ID: <3387.1037403705@kanga.nu> On Fri, 15 Nov 2002 15:03:49 -0800 Chuq Von Rospach wrote: > On Friday, November 15, 2002, at 12:14 PM, Fil wrote: >>> Or perhaps a better way would be to store messages static, meta-data >>> in a database, and build indexes on the fly, since the messages >>> won't change.... >> Why shouldn't the messages change? People have the right to send me >> an email saying "please delete my name from the archives" - usually >> it's their telephone number, or their employer's domain name ;) > And ym answer is that you don't unpublish a newspaper. I only modify > archives for issues of legal liability. > your mileage may vary there... More simply: Yes, you have the right to send me such a request. I also have the right to ignore your request. FWLIW I don't believe in rewriting history. For that reason and others related to it I don't remove messages from archives, or do anything more with X-No-Archive other than laughing while I ignore it. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From fil@rezo.net Sat Nov 16 00:02:46 2002 From: fil@rezo.net (Fil) Date: Sat, 16 Nov 2002 01:02:46 +0100 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: <3387.1037403705@kanga.nu> References: <803E21B3-F8EE-11D6-B243-0003934516A8@plaidworks.com> <3387.1037403705@kanga.nu> Message-ID: <20021116000246.GA14970@rezo.net> > FWLIW I don't believe in rewriting history. For that reason and others > related to it I don't remove messages from archives, or do anything more > with X-No-Archive other than laughing while I ignore it. Why not. I was talking about technical issues: is it efficient to generate the pages "on the fly"? are plain-html archives the right answer or just a legacy of majordomo? ... but if, by "rewriting history", you mean that someone would do it if she can overwrite files on her computer, history must be at a high risk today - even HyperArch can rewrite the past ;) As for cultural context, in France we have a law about "computers and freedom" (better termed "electronic privacy" now, but that law was passed in the 1980's, after Chirac, then 1st minister, had decided to set up a big centralized database containing fiscal records and such... the big database was called SAFARI, funny hey?) Under this privacy law, people have a right to know which files contain data about them, see what data there is, correct the information, and even request to be removed (of course there are many exceptions, for obvious reasons, but publicly accessible email archives certainly fall under this law). Is the law working? Maybe, in terms of percentage of people "caught by the police", not much more than traffic laws; but it certainly has an impact: I'm getting most of the spam from the USA ;) -- Fil From claw@kanga.nu Sat Nov 16 00:55:04 2002 From: claw@kanga.nu (J C Lawrence) Date: Fri, 15 Nov 2002 16:55:04 -0800 Subject: [Mailman-Developers] thinking out loud... In-Reply-To: Message from Fil of "Sat, 16 Nov 2002 01:02:46 +0100." <20021116000246.GA14970@rezo.net> References: <803E21B3-F8EE-11D6-B243-0003934516A8@plaidworks.com> <3387.1037403705@kanga.nu> <20021116000246.GA14970@rezo.net> Message-ID: <4295.1037408104@kanga.nu> On Sat, 16 Nov 2002 01:02:46 +0100 fil wrote: >> FWLIW I don't believe in rewriting history. For that reason and >> others related to it I don't remove messages from archives, or do >> anything more with X-No-Archive other than laughing while I ignore >> it. > Why not. The past is immutable, ergo, records which purport to (accurately) represent the past should be immutable (at the content level). > I was talking about technical issues: is it efficient to generate the > pages "on the fly"? are plain-html archives the right answer or just a > legacy of majordomo? ... but if, by "rewriting history", you mean that > someone would do it if she can overwrite files on her computer, > history must be at a high risk today - even HyperArch can rewrite the > past ;) Frankly I find this an uninteresting question and problem. Yes, you can pre-calculate, just-in-time calculate, or just-in-time calculate and cache etc. Those are questions and activities of optimisation, not basic processing, and from my position, they're questions of optimisation for a resource which is not particularly limited or contested. Disk is cheap and at this level, CPU is cheaper. Heck, Goggle spiders all my boxes every few weeks guaranteeing that everything gets generated if I do some sort of just-in-time form. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From barry@python.org Sat Nov 16 05:49:26 2002 From: barry@python.org (Barry A. Warsaw) Date: Sat, 16 Nov 2002 00:49:26 -0500 Subject: [Mailman-Developers] mailman and voting References: Message-ID: <15829.56422.922114.542043@gargle.gargle.HOWL> Hi Marilyn, >>>>> "MD" == Marilyn Davis writes: MD> I am the developer of eVote/Clerk, which hooks onto a MD> maillist-server in the alias file and looks for commands in MD> the incoming mail that start with "eVote". These are diverted MD> and parsed by eVote and allow any of the members to poll the MD> group and administer the poll. It has other super-democratic MD> features, like you can change your vote if you change your MD> mind, you can see others' votes (if the poll is initialized as MD> "public"), you can democratically spend budgets. Sounds cool! MD> I'm in a sudden panic because I've been running it with MD> majordomo and that's old stuff. The Linux Journal wants to MD> run an article about eVote/Clerk but they want it to be MD> running with Mailman. Yay :) MD> My deadline is in a few weeks. Ouch. MD> Theoretically, it should be a simple thing to switch. I don't MD> touch majordomo's code at all. (I wouldn't mind touching MD> Mailman's because I love Python.) Yay :) MD> I'm hoping that some Mailman expert(s) might be available to MD> help me. MD> Maybe it'll be easy. It might be. I actually can't get to your SF pages right now. It looks like SF is under maintenance. Can you give us a run down of what code you do have? Is it already in Python? Is it a standalone thing, or does it have deeper ties with the MLM? How do you see eVote hooking into Mailman? MD> eVote/Clerk source code is at sourceforge.net, if anyone wants MD> to give it a shot. The current state of the cvs tree is ready MD> for release, even though I have not done an official release MD> of it. It sounds like a great cause, but I'm not sure how much direct help I can provide. I'm pretty swamped right now. I don't know if there are any others on this list that might be able to lend a hand. OTOH, I /can/ give advice or help out if you get stuck on something. Why not give it a shot and see how it goes? If you have questions or run into problems, post to this list and we'll try to help out. -Barry From barry@python.org Sat Nov 16 06:13:14 2002 From: barry@python.org (Barry A. Warsaw) Date: Sat, 16 Nov 2002 01:13:14 -0500 Subject: [Mailman-Developers] no digest buttons on mailman-announce web page References: <3DD27B9F.2037DDD3@orcaware.com> Message-ID: <15829.57850.888858.186362@gargle.gargle.HOWL> >>>>> "BZ" == Blair Zajac writes: BZ> Just checked the web page BZ> http://mail.python.org/mailman/listinfo/mailman-announce BZ> and where it says: BZ> "Would you like to receive list mail batched in a daily BZ> digest? No Yes" BZ> there are no radio buttons. BZ> The web page BZ> http://mail.python.org/mailman/listinfo/mailman-users BZ> does have then. This was a u/i nit for when no choice is given between digest and regular delivery. I just implemented a hackaround which will have to get translated to all the language templates. But it definitely does look better. -Barry From marc_news@merlins.org Sat Nov 16 06:20:39 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Fri, 15 Nov 2002 22:20:39 -0800 Subject: [Mailman-Developers] Reasons why personalization of the To/From are a bad idea... In-Reply-To: <26696.1037225198@kanga.nu> References: <31AA582B-F733-11D6-B6BE-0003934516A8@plaidworks.com> <26696.1037225198@kanga.nu> Message-ID: <20021116062038.GE28796@merlins.org> On Wed, Nov 13, 2002 at 02:06:38PM -0800, J C Lawrence wrote: > > 3) I can't prove this, but... Since I went to To/From header > > personalization, I've started getting complaints about mail not > > getting to AOL users. > > Yeah, this is not terribly surprising. I suspect you're running afoul > of their SPAM filters and Mailman's new header personalisation is > hitting a corner case in their dupe filters (personally addressed now > being common). AOL is doing very stupid things with blocking. They take your mail and drop it on the floor, you'll never get any indication that they did that. For that matter, they blocked google.com (where I work now) for 2 weeks and independantly Emailed us to complain that we weren't answering their business Emails (answers that they were dropping on the floor)... You have to call them to get that fixed, they are reasonably good once you get them on the phone. In our case (and probably all/most others), they never told us why we had been blocked in the first place, except that they had fixed it. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From marc_news@merlins.org Sat Nov 16 06:22:49 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Fri, 15 Nov 2002 22:22:49 -0800 Subject: [Mailman-Developers] notification d'abonnement de Powerteam_fr Message-ID: <20021116062249.GF28796@merlins.org> Is/was there a bug with expanding strings for foreign languages? (my mailman is probably cvs as of 5-6 weeks ago) ----- Forwarded message from mailman-owner-owner@merlins.org ----- Subject: notification d'abonnement de Powerteam_fr From: mailman-owner-owner@merlins.org To: powerteam_fr-owner@merlins.org X-List-Administrivia: yes %(member)s a été abonné à %(listname)s avec succès. ----- End forwarded message ----- -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From carson@taltos.org Sat Nov 16 06:29:51 2002 From: carson@taltos.org (Carson Gaspar) Date: Sat, 16 Nov 2002 01:29:51 -0500 Subject: [Mailman-Developers] 2 mailman queries Message-ID: <69720906.1037410191@[192.168.20.2]> A few questions have come up from one of my list users that I can't answer (without delving into python source, anyway ;-). I've mentioned the first one before, but I'm hoping the answer may have changed with new code - is there any way to force line breaks in messages without leaving a blank line? The substitution process appears to re-wrap all text. The second one is easier - is there an easy way to suppress bounce notifications? Or unsubscribe notifications? -- Carson From marilyn@deliberate.com Sat Nov 16 07:32:11 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Fri, 15 Nov 2002 23:32:11 -0800 (PST) Subject: [Mailman-Developers] Re: mailman and voting (fwd) Message-ID: Excuse me. I didn't realize that reply-to's didn't go to the whole list. Now I realize. ---------- Forwarded message ---------- Date: Thu, 14 Nov 2002 16:32:02 -0800 (PST) From: Marilyn Davis To: David Champion Subject: Re: mailman and voting On Thu, 14 Nov 2002, David Champion wrote: > > I probably can't help much with the problem, but something in your > message really grabbed at my lapels. My message is a week old. Because I'm new here, I was quarantined, I guess. My panic has worn off, she says, smoothing your lapels. Thank you for you concern and your thoughts. > > * On 2002.11.06, in , > * "Marilyn Davis" wrote: > > > > I'm in a sudden panic because I've been running it with majordomo and > > that's old stuff. The Linux Journal wants to run an article about > > eVote/Clerk but they want it to be running with Mailman. My deadline > > is in a few weeks. > > Do I understand correctly that Linux Journal is pressuring you to adapt > your software to use another component, one that they favor over the one > you're using? It sounds like LJ is pushing an agenda of some kind, and > using publication as the enticement to leverage their favoritism. That > makes me most wary of Linux Journal. I think his agenda is to please his readers and he thinks they won't like reading about majordomo. He's right. I've been wishing for a mailman interface for years but I don't really have the resources to do much. But the Linux Journal carrot has got me moving. Let's hope he really publishes my article after all this. > > Hmm -- as I've been writing, I've also been thinking about your problem. > If I understood, you essentially need a mechanism for diverting the > messages containing "eVote". Since (in most cases) Mailman works via > mail aliases, just like Majordomo, it seems you could do this with a > front-end wrapper around the Mailman script. If your Majordomo works the > same way, it might even be the same script, mostly. > > Here are some aliases set up for a test list on my server, so you can > see what it looks like: > testlist: "|/opt/pkgs/mailman/mail/wrapper post testlist" > testlist-admin: "|/opt/pkgs/mailman/mail/wrapper mailowner testlist" > testlist-request: "|/opt/pkgs/mailman/mail/wrapper mailcmd testlist" > owner-testlist: testlist-admin > testlist-owner: testlist-admin You're right. I have modified mailman's wrapper to also exec to eVote_insert and eVote_petition. I have added a little bit in MailList.py so that eVote is sent notification of the addition and subtraction of members. I am using withlist to check the admin password and to find a list of members for syncronizing. It's turning out to be pretty fun because the mailman code is so nice and I love Python. I guess, when it's all done, and the holidays are over, I'll see about incorporating my changes into the sources at sourceforge, if anyone likes them. Thank you again. Marilyn Davis > > -- > -D. dgc@uchicago.edu NSIT University of Chicago > From marilyn@deliberate.com Sat Nov 16 08:13:33 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Sat, 16 Nov 2002 00:13:33 -0800 (PST) Subject: [Mailman-Developers] mailman and voting In-Reply-To: <15829.56422.922114.542043@gargle.gargle.HOWL> Message-ID: Thank you Barry. I'm so glad you find it interesting. A copy of the article that they are (finally) going to publish (maybe) is at http://www.deliberate.com/eVote/papers/ljarticle.html. You can see that it talks about "majordomo" and I am to search-and-replace with "mailman" and make it work. I do have a question. To milk mailman for password verification and the list of addresses, I fork and exec to withlist, attaching withlist's stdout to eVote's stdin to collect my answers. (eVote is written in C.) But withlist also writes to stderr - when there is no error. Might the mailman authors consider only writing to stderr when there's an error? It would be easier for me. Or maybe you folks can provide an argument to withlist that suppresses the stderr messages that aren't errors. (I haven't figured out how to direct both streams into my stdin within my C code.) Another thought I'm having is that it would be nifty to carry eVote through to the web interface. Maybe we can do that one day. For exim, because mailman is turned-on in the configuration file rather than on a list-by-list basis, eVote comes to all the lists or none. Is this a bad thing? Should the admin be allowed to toggle it on her configuration page? I'm feeling very good about this project. Thank you so much for your support. Marilyn From bjoernk@gmx.net Sat Nov 16 10:46:26 2002 From: bjoernk@gmx.net (bjoernk@gmx.net) Date: Sat, 16 Nov 2002 11:46:26 +0100 (MET) Subject: [Mailman-Developers] footer bug or feature? Message-ID: <7635.1037443586@www51.gmx.net> Hi! I am using Mailman 2.1b4+ now (thanks for the CVS info yesterday!) and I was actually hoping that the footer thing I noticed with 2.1b4 would be gone, but it is still there. Here is my question: A footer message for the mailing list is defined. But it only appears every 2nd or 3rd e-mail. I tried to figure out a regular basis on which it appears or not, but I couldn't figure it out yet. It seems like it is sort of a "chaotic" behaviour. Maybe it is a feature? I mean, it does appear every so and so often. Is there another configuration parameter that interferes with the footer message? Thanks & bye, BJ -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! From pioppo@ferrara.linux.it Sat Nov 16 12:37:49 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Sat, 16 Nov 2002 13:37:49 +0100 Subject: [Mailman-Developers] notification d'abonnement de Powerteam_fr In-Reply-To: <20021116062249.GF28796@merlins.org> References: <20021116062249.GF28796@merlins.org> Message-ID: <20021116123748.GA2795@ferrara.linux.it> On Fri, Nov 15, 2002 at 10:22:49PM -0800, Marc MERLIN wrote: > Is/was there a bug with expanding strings for foreign languages? > (my mailman is probably cvs as of 5-6 weeks ago) Yes, this is broken since at least 2.1b4, and AFAIK is still broken in CVS. Please see bug report SF #631774 -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From barry@python.org Sat Nov 16 15:15:30 2002 From: barry@python.org (Barry A. Warsaw) Date: Sat, 16 Nov 2002 10:15:30 -0500 Subject: [Mailman-Developers] mailman and voting References: <15829.56422.922114.542043@gargle.gargle.HOWL> Message-ID: <15830.24850.578032.290150@gargle.gargle.HOWL> >>>>> "MD" == Marilyn Davis writes: MD> Thank you Barry. I'm so glad you find it interesting. MD> A copy of the article that they are (finally) going to publish MD> (maybe) is at MD> http://www.deliberate.com/eVote/papers/ljarticle.html. You MD> can see that it talks about "majordomo" and I am to MD> search-and-replace with "mailman" and make it work. Cool. I've only just skimmed the article, but it looks interesting. I think MM2.1 might provide a very nice platform for eVote. For example, MM2.1 supports virtual lists, so you could do something like, set up one or a small number of voting lists, and manipulate the recipients via the Mailman/Post.py interface. MD> I do have a question. To milk mailman for password MD> verification and the list of addresses, I fork and exec to MD> withlist, attaching withlist's stdout to eVote's stdin to MD> collect my answers. (eVote is written in C.) But withlist MD> also writes to stderr - when there is no error. Might the MD> mailman authors consider only writing to stderr when there's MD> an error? I'm thinking that withlist might be a hammer when you need a screwdriver. Remember that there really isn't anything special about withlist -- it just imports a few Python modules and manipulates those modules. So there's certainly nothing stopping you from writing a script that is much more appropriate for your task. MD> It would be easier for me. Or maybe you folks can MD> provide an argument to withlist that suppresses the stderr MD> messages that aren't errors. (I haven't figured out how to MD> direct both streams into my stdin within my C code.) I can think of a couple of approaches. If eVote has an RPC mechanism, it's likely there either exists or you could easily write, a Python interface to that RPC, and have eVote and Mailman communicate over that link. Or you might consider embedding Python in the C code for eVote, and then it would be trivial for eVote to directly import and call Mailman code. MD> Another thought I'm having is that it would be nifty to carry MD> eVote through to the web interface. Maybe we can do that one MD> day. MD> For exim, because mailman is turned-on in the configuration MD> file rather than on a list-by-list basis, eVote comes to all MD> the lists or none. Is this a bad thing? Should the admin be MD> allowed to toggle it on her configuration page? It's not a bad thing, but you could certainly add some smarts to Mailman to configure that per-list. For example, you could write a small handler module (e.g. Mailman/Handlers/Acknowledge.py) that hands the message off to eVote. It would be easy to write a little gui glue for your new handler too. See examples in Mailman/Gui/*.py Or you could add new email commands, and set Mailman up so that only certain lists respond to those commands. The commands could be as simple as just handing the message off to eVote. See examples in Mailman/Commands/cmd_*.py. MD> I'm feeling very good about this project. Thank you so much MD> for your support. No problem. It should work out well, and because Python is so malleable and interfaces nicely with C programs, I think you can have a much tighter integration between the two systems, if you want. Cheers, -Barry From barry@python.org Sat Nov 16 15:21:22 2002 From: barry@python.org (Barry A. Warsaw) Date: Sat, 16 Nov 2002 10:21:22 -0500 Subject: [Mailman-Developers] footer bug or feature? References: <7635.1037443586@www51.gmx.net> Message-ID: <15830.25202.352466.923980@gargle.gargle.HOWL> >>>>> "bjoernk" == writes: bjoernk> I am using Mailman 2.1b4+ now (thanks for the CVS info bjoernk> yesterday!) and I was actually hoping that the footer bjoernk> thing I noticed with 2.1b4 would be gone, but it is still bjoernk> there. Here is my question: bjoernk> A footer message for the mailing list is defined. But it bjoernk> only appears every 2nd or 3rd e-mail. I tried to figure bjoernk> out a regular basis on which it appears or not, but I bjoernk> couldn't figure it out yet. It seems like it is sort of a bjoernk> "chaotic" behaviour. Maybe it is a feature? I mean, it bjoernk> does appear every so and so often. bjoernk> Is there another configuration parameter that interferes bjoernk> with the footer message? Headers and footers won't be added if they can't be done in a MIME-safe way. That means the original message must: - be a text/plain with a charset matching the list's preferred language, with no Content-Transfer-Encoding of base64 - be a multipart/mixed There have been some recent discussions about how to expand those criteria, but I haven't had time to respond on that thread yet. -Barry From chuqui@plaidworks.com Sat Nov 16 18:41:13 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sat, 16 Nov 2002 10:41:13 -0800 Subject: [Mailman-Developers] 2.1b4+ language bug? Message-ID: Had a subscriber from sweden subscribe to one of my lists today. The=20 notice to the admin that was sent is a bit schizophrenic: note that the charset is us-ascii, but the actual content is swedish,=20 and it's not rendering right... From: mailman-bounces@plaidworks.com Date: Sat Nov 16, 2002 5:07:04 AM US/Pacific To: maple-leafs-owner@plaidworks.com Subject: maple-leafs subscription notification Return-Path: Received: from www.plaidworks.com (localhost [127.0.0.1]) by=20 plaidworks.com (8.12.2/8.12.2) with ESMTP id gAGD767k029950 for=20 ; Sat, 16 Nov 2002 05:07:06 -0800 (PST) Mime-Version: 1.0 Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: 8bit Message-Id: Precedence: bulk X-Beenthere: maple-leafs@plaidworks.com X-Mailman-Version: 2.1b4+ List-Id: A mailing list for fans of the Toronto Maple Leafs=20 X-List-Administrivia: yes Sender: mailman-bounces+listadmin=3Dplaidworks.com@plaidworks.com Errors-To: mailman-bounces+listadmin=3Dplaidworks.com@plaidworks.com christerlindberg@telia.com =89r nu anm=89lda till listan maple-leafs. --=20 Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Stress is when you wake up screaming and you realize you haven't fallen=20= asleep yet. From marilyn@deliberate.com Sat Nov 16 18:43:32 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Sat, 16 Nov 2002 10:43:32 -0800 (PST) Subject: [Mailman-Developers] mailman and voting In-Reply-To: <15830.24850.578032.290150@gargle.gargle.HOWL> Message-ID: On Sat, 16 Nov 2002, Barry A. Warsaw wrote: > > >>>>> "MD" == Marilyn Davis writes: > > MD> Thank you Barry. I'm so glad you find it interesting. > > MD> A copy of the article that they are (finally) going to publish > MD> (maybe) is at > MD> http://www.deliberate.com/eVote/papers/ljarticle.html. You > MD> can see that it talks about "majordomo" and I am to > MD> search-and-replace with "mailman" and make it work. > > Cool. I've only just skimmed the article, but it looks interesting. > I think MM2.1 might provide a very nice platform for eVote. For 2.1? I got 2.0.13 from gnu.org. It's already obsolete? What a business, this! > example, MM2.1 supports virtual lists, so you could do something like, > set up one or a small number of voting lists, and manipulate the > recipients via the Mailman/Post.py interface. > > MD> I do have a question. To milk mailman for password > MD> verification and the list of addresses, I fork and exec to > MD> withlist, attaching withlist's stdout to eVote's stdin to > MD> collect my answers. (eVote is written in C.) But withlist > MD> also writes to stderr - when there is no error. Might the > MD> mailman authors consider only writing to stderr when there's > MD> an error? > > I'm thinking that withlist might be a hammer when you need a > screwdriver. Remember that there really isn't anything special about > withlist -- it just imports a few Python modules and manipulates those > modules. So there's certainly nothing stopping you from writing a > script that is much more appropriate for your task. Yes. I could. And I'd like to. But I'm afraid of licensing issues. eVote/Clerk's license is not GPL but GPL-like. There is a clause in the license to try to protect the voter from a cheating administrator, so it's not as free as Richard Stallman would like. c) If the modified program supports non-public voting, i.e. voting in which the participants cannot see the votes of the other participants, when run, you must cause the program, to announce the following whenever it gives instructions for non-public voting, and whenever it generates receipts and reports pertaining to the non-public vote: Warnings: Although eVote will not reveal your vote to the other members of the voting community, the system administrator of the computer that stores your vote can quite easily see the voting records of individuals. Also, there is the possibility that your ballot can be seen by a "snooper", someone who intercepts your ballot in transit. The integrity of the poll, i.e., the accuracy of the count, is susceptible to being tampered with by the system administrator of the computer running the eVote(R)/Clerk software. Both the privacy of your vote and the integrity of the poll are susceptible to attack at your own computer. So, to stay beyond reproach, I'd better not glue the two softwares together too tightly just yet. I just learned how to redirect stderr into my program so there's no problem. Thank you again. Marilyn From barry@python.org Sun Nov 17 20:55:06 2002 From: barry@python.org (Barry A. Warsaw) Date: Sun, 17 Nov 2002 15:55:06 -0500 Subject: [Mailman-Developers] notification d'abonnement de Powerteam_fr References: <20021116062249.GF28796@merlins.org> <20021116123748.GA2795@ferrara.linux.it> Message-ID: <15832.554.509865.160919@gargle.gargle.HOWL> >>>>> "SP" == Simone Piunno writes: >> Is/was there a bug with expanding strings for foreign >> languages? (my mailman is probably cvs as of 5-6 weeks ago) SP> Yes, this is broken since at least 2.1b4, and AFAIK is still SP> broken in CVS. Please see bug report SF #631774 I think I've now fixed both bugs reported in this issue. -Barry From noreply@sourceforge.net Sun Nov 17 20:55:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 17 Nov 2002 12:55:30 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631774 ] i18n unicode string interpolation Message-ID: Bugs item #631774, was opened at 2002-10-31 16:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631774&group_id=103 Category: None Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: i18n unicode string interpolation Initial Comment: Hi, below you can find a report from one of the italian translators (thanks Enea Zaffanella). I believe somewhere between 2.1b3 and b4 a string has been converted into unicode and now string interpolation is not working anymore as expected. Here u'' appears in html output (generated by admin.py): ====================================== ********************************************************************** **********************************************************************
    Indirizzo/nome
    La tua decisione
    Motivo del rifiuto
    u'zaffanella@example.it
    Enea Zaffanella'
    Rimando la decisione Approvo Rigetta Scarta
    ================================ And here (adminsubscribeack.txt) interpolation doesn't happen: ================================ %(member)s è stato iscritto con successo a %(listname)s. ================================ They are 2 different cases: one is _(string) and the other is Utils.Maketext(a template, dictionary of strings), so this suggests even more that i18n.py has been screwed up by unicode. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-17 15:55 Message: Logged In: YES user_id=12800 Both of these should now be fixed for b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631774&group_id=103 From barry@python.org Sun Nov 17 21:11:12 2002 From: barry@python.org (Barry A. Warsaw) Date: Sun, 17 Nov 2002 16:11:12 -0500 Subject: [Mailman-Developers] notification d'abonnement de Powerteam_fr References: <20021116062249.GF28796@merlins.org> <20021116123748.GA2795@ferrara.linux.it> <15832.554.509865.160919@gargle.gargle.HOWL> Message-ID: <15832.1520.871753.649995@gargle.gargle.HOWL> >>>>> "BAW" == Barry A Warsaw writes: BAW> I think I've now fixed both bugs reported in this issue. Except of course I can't commit these because SF's cvs is down. :/ -Barry From links@momsview.com Fri Nov 15 05:31:47 2002 From: links@momsview.com (Links at Momsview) Date: Fri, 15 Nov 2002 00:31:47 -0500 Subject: [Mailman-Developers] Disabling confirm on unsubscription 2.1b4 Message-ID: <010c01c28c68$4ba09de0$6401a8c0@p3> I am running a list using 2.1b4 with open subscribe (ALLOW_OPEN_SUBSCRIBE=1 and DEFAULT_SUBSCRIBE_POLICY = 0) I would like to also allow the equivalent of "open" unsubscriptions by turning off confirmations. I already have DEFAULT_UNSUBSCRIBE_POLICY = 0 but realized I would have to hack the code to do what I wanted (turn off confirmations). >From what I have gathered, the code of interest is in the cmd_unsubscribe.py module in mailman/Mailman/Commands directory. Below is the relevent section of code from cmd_unsubscribe.py with my changes (commented out lines of code) clearly indicated: --------------------------------------------- # If we're doing admin-approved unsubs, don't worry about the password if mlist.unsubscribe_policy: try: mlist.DeleteMember(address, 'mailcmd') except Errors.MMNeedApproval: res.results.append(_("""\ Your unsubscription request has been forwarded to the list administrator for approval.""")) # elif password is None: # No password was given, so we need to do a mailback confirmation # instead of unsubscribing them here. # cpaddr = mlist.getMemberCPAddress(address) # mlist.ConfirmUnsubscription(cpaddr) # res.results.append(_('A removal confirmation message has been sent.')) # else: # No admin approval is necessary, so we can just delete them if the # passwords match. # oldpw = mlist.getMemberPassword(address) # if oldpw <> password: # res.results.append(_('You gave the wrong password')) # return STOP mlist.ApprovedDeleteMember(address, 'mailcmd') res.results.append(_('Unsubscription request succeeded.')) ---------------------------------------------------------- This was just a quick hack that I intended to replace with a formal mm_cfg controlled option once I verified that it worked. To my suprise IT DIDN'T DISABLE THE CONFIRM even though the code was commented out. I made these changes in the untarred source in /mailman-2.1b4/Mailman/Commands/ and did: make clean ./configure make install I verified that the new .py and .pyc files made it to /mailman/Mailman/Commands in the installation directory. Can anyone tell me what I'm doing wrong? Thank you in advance. From webperson@now.org Sun Nov 17 20:54:20 2002 From: webperson@now.org (NOW Website Coordinator) Date: Sun, 17 Nov 2002 12:54:20 -0800 Subject: [Mailman-Developers] Help! 2.1b4 bug prevents me from seeing membership list-- it crashes Message-ID: <4.3.2.7.2.20021117121125.00cda840@now.org> I'm trying to convert our lists from majordomo to mailman. It worked fine with a small test list, but when I tried to convert a larger one, all I've gotten is the bug listed below. I originally added them from the form (mass subscribe) and then tried sync_members, and then remove_members and add_members. I can get the names out with list_members. There are only 1100 names. I get this every time I click on membership management. Any time would be very wonderful. Thanks. Bug in Mailman version 2.1b4 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 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 192, in main show_results(mlist, doc, category, subcat, cgidata) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 496, in show_results form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 828, in membership_options qs = cgi.parse_qs(os.environ['QUERY_STRING']) File "/usr/local/lib/python2.2/UserDict.py", line 14, in __getitem__ def __getitem__(self, key): return self.data[key] KeyError: QUERY_STRING Python information: Variable Value sys.version 2.2.1 (#1, Sep 28 2002, 10:00:33) [GCC 3.0] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform sunos5 Environment variables: Variable Value HTTP_REFERER http://www.now.org/mailman/admin/dc-zaps/members/add PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Netscape-Enterprise/3.6 SP3 SCRIPT_NAME /mailman/admin REQUEST_METHOD GET HTTP_HOST www.now.org PATH_INFO /dc-zaps/members/list HTTPS OFF SERVER_PROTOCOL HTTP/1.1 TZ US/Eastern HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/msword, application/vnd.ms-powerpoint, application/vnd.ms-excel, */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows 98) HTTP_CONNECTION Keep-Alive HTTP_COOKIE now-test-list+admin=2802000000699a0fd73d732800000034333737373038616265383531623135333539353738313335343562663235666531663963343235; new-test+admin=2802000000696b28d73d732800000031386661633766356230663431633031313736323231303634316436623834376666356534366261; dc-zaps+admin=28020000006902f2d73d732800000062386465653339363261633163313761336331303435643231333430633638356634663237356462 SERVER_NAME www.now.org REMOTE_ADDR 64.160.53.109 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_LANGUAGE en-us SERVER_URL http://www.now.org PATH_TRANSLATED /usr/ns-home/docs/dc-zaps/members/list SERVER_PORT 80 REMOTE_HOST 64.160.53.109 HTTP_ACCEPT_ENCODING gzip, deflate Sarah Stapleton-Gray -------------------------------------------- Web Site Coordinator National Organization for Women http://www.now.org From barry@python.org Mon Nov 18 15:52:50 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 18 Nov 2002 10:52:50 -0500 Subject: [Mailman-Developers] Help! 2.1b4 bug prevents me from seeing membership list-- it crashes References: <4.3.2.7.2.20021117121125.00cda840@now.org> Message-ID: <15833.3282.508396.609121@gargle.gargle.HOWL> >>>>> "NWC" == NOW Website Coordinator writes: NWC> I get this every time I click on membership management. NWC> KeyError: QUERY_STRING NWC> SERVER_SOFTWARE Netscape-Enterprise/3.6 SP3 I'm going to put my money on the server not quite supporting the CGI standard. The work around should be fairly straightforward but I don't know if there will be reduced functionality because of it. I'll make the changes. If you can test with the cvs version, that'd be good, otherwise just wait for beta5 (today, crossing fingers). -Barry From noreply@sourceforge.net Mon Nov 18 18:20:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 10:20:52 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637748 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637748, was opened at 2002-11-13 08:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637748&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) >Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637748&group_id=103 From noreply@sourceforge.net Mon Nov 18 18:21:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 10:21:25 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637747 ] Mangled "Re:" in i18n subject header Message-ID: Bugs item #637747, was opened at 2002-11-13 08:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) >Summary: Mangled "Re:" in i18n subject header Initial Comment: Hello! Look, here is the subject from a mailman-managed mailing list: Subject: [Bug] =?koi8-r?B?UmU6IFtCdWddIFJlWzJdOiBbQnVnXSBSZTogW0J1Z10gUmU6IFtCdQ==?= =?koi8-r?B?Z10g8NLPxMHF1NPRINPMwdfRztPLycog28vBxg==?= Let me decode it: import sys, email.Header print email.Header.decode_header(sys.stdin.read()) [('Subject: [Bug]', None), ('Re: [Bug] Re[2]: [Bug] Re: [Bug] Re: [Bug] \xf0\xd2\xcf\xc4\xc1\xc5\xd4\xd3\xd1 \xd3\xcc\xc1\xd7\xd1\xce\xd3\xcb\xc9\xca \xdb\xcb\xc1\xc6', 'koi8-r')] Look how many "Re:"s re there! The problem arise when Mailman adds list tag (in this case [Bug]) to an *encoded* header. Mailman must decode the header and check for "Re:" and list tag in the decoded header. All mailing lists that I know are guilty with the bug. Let Mailman be the first that fixes it! Thank you. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 13:21 Message: Logged In: YES user_id=12800 I'm closing this because I believe it /is/ fixed in MM2.1 and it won't be fixed in MM2.0.x. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2002-11-13 09:29 Message: Logged In: YES user_id=4799 Mailman 2.1 is still in beta. I don't dare to recommend it to sysadmins - these are not my mailing lists, nor my hosts. But it's good to know there is a fix. I'll give it a try when you release 2.1-final. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2002-11-13 09:29 Message: Logged In: YES user_id=4799 Mailman 2.1 is still in beta. I don't dare to recommend it to sysadmins - these are not my mailing lists, nor my hosts. But it's good to know there is a fix. I'll give it a try when you release 2.1-final. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-13 09:18 Message: Logged In: YES user_id=12800 Oleg, have you tried this with MM2.1? I think there's code in there that tries to decode the header first before searching for the prefix. I'm not surprised MM2.0 doesn't do the right thing, but MM2.1 should. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637747&group_id=103 From Dan.Mick@sun.com Mon Nov 18 19:12:18 2002 From: Dan.Mick@sun.com (Dan Mick) Date: Mon, 18 Nov 2002 11:12:18 -0800 Subject: [Mailman-Developers] mailman and voting References: <15829.56422.922114.542043@gargle.gargle.HOWL> Message-ID: <3DD93B92.2040609@sun.com> > It sounds like a great cause, but I'm not sure how much direct help I > can provide. I'm pretty swamped right now. I don't know if there are > any others on this list that might be able to lend a hand. I can't tell what needs to be done, but feel free to contact me; I might be able to help. From noreply@sourceforge.net Mon Nov 18 20:46:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 12:46:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634303 ] Recode pipermail templates Message-ID: Patches item #634303, was opened at 2002-11-06 03:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Recode pipermail templates Initial Comment: This patch transparently recodes the pipermail templates and messages if the article and index files have a different encoding than the template language If necessary, HTML character references are generate. If recoding fails, it will proceed without exception, but produce garbage. For messages, this uses a method self._, which first invokes _, then does the recoding. This makes it necessary for _ to go back more than one frame, so the number of frames is now an optional parameter (defaulting to 1). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 15:46 Message: Logged In: YES user_id=12800 Feel free to shoot holes in this, but I think it might not be simpler to just get rid of the multiple _charsets stuff in HyperArch.HyperArchive. Say we always encode the indices pages with the character set of the list's preferred language, except that we also html-ify any bogus characters outside that charset. Seems to me we can chop a bunch of code and still get the results we want, even if at the expense of potentially bigger pages (which I don't care about). I'm going to commit some changes and test them out on the playground list. This seem to work well here for my test lists. Semi-related: would PEP 293 allow us to get rid of unicode_quote? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 From noreply@sourceforge.net Mon Nov 18 22:23:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 14:23:30 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640360 ] path relative URLs with /base vs /base/ Message-ID: Bugs item #640360, was opened at 2002-11-18 22:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640360&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: path relative URLs with /base vs /base/ Initial Comment: Our Apache server accepts path requests with or with a trailing slash, indifferently. (I understand there is no redirect.) This affects (cripples) relative paths, because http://host/mailman/private/name is the same page as http:// host/mailman/private/name/, but is different in reference to relative paths. The relative location of a month would be `href="name/2002-November/subject.html"' for the former, but `href="2002-November/subject.html"' for the latter. I suspect that the "private" URL is rarely entered by hand anyway, but FYI. /mailman/private/name/2002-November/ subject.html is OK, as far as I know. 2.1b4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640360&group_id=103 From noreply@sourceforge.net Mon Nov 18 22:57:45 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 14:57:45 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640374 ] 2.1b4 Mailman bug Message-ID: Bugs item #640374, was opened at 2002-11-18 16:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b4 Mailman bug Initial Comment: When I try to access some of my lists via the web interface to moderate them I receive this error message: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admindb.py", line 227, in main show_pending_unsubs(mlist, form) File "/var/mailman/Mailman/Cgi/admindb.py", line 332, in show_pending_unsubs fullname = Utils.uncanonstr(mlist.getMemberName (addr), lang) File "/var/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/var/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member NotAMemberError: capeterson28@hotmail.com This is only a problem for some of my lists. Some lists I can log into and moderate successfully from the Web. I am running Mailman 2.1b4 on RedHat Linux 7.3. Let me know if you need more information. Thanks for your help. Paul Marshall ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103 From noreply@sourceforge.net Mon Nov 18 23:25:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 15:25:18 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634303 ] Recode pipermail templates Message-ID: Patches item #634303, was opened at 2002-11-06 09:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Recode pipermail templates Initial Comment: This patch transparently recodes the pipermail templates and messages if the article and index files have a different encoding than the template language If necessary, HTML character references are generate. If recoding fails, it will proceed without exception, but produce garbage. For messages, this uses a method self._, which first invokes _, then does the recoding. This makes it necessary for _ to go back more than one frame, so the number of frames is now an optional parameter (defaulting to 1). ---------------------------------------------------------------------- >Comment By: Martin v. Löwis (loewis) Date: 2002-11-19 00:25 Message: Logged In: YES user_id=21627 My concern with this approach is that we might not have a codec for the encoding of the message. That means we cannot decode the message to unicode, which means we cannot htmlify unsupported characters. OTOH, we do have codecs for the preferred encodings of all supported languages. [Sorry I didn't think of this issue when we were talking about it recently] If we consider this case unlikely to occur in real life, and are prepared to produce some error message in the page if it does happen, then the approach is fine. As for PEP293: Yes, this is precisely the intention: it simplifies generating html-escaped strings, and it is more efficient than any other strategy (since the codec will call the error handling only when an encoding error occurs). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 21:46 Message: Logged In: YES user_id=12800 Feel free to shoot holes in this, but I think it might not be simpler to just get rid of the multiple _charsets stuff in HyperArch.HyperArchive. Say we always encode the indices pages with the character set of the list's preferred language, except that we also html-ify any bogus characters outside that charset. Seems to me we can chop a bunch of code and still get the results we want, even if at the expense of potentially bigger pages (which I don't care about). I'm going to commit some changes and test them out on the playground list. This seem to work well here for my test lists. Semi-related: would PEP 293 allow us to get rid of unicode_quote? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 From noreply@sourceforge.net Mon Nov 18 23:29:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 15:29:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-10 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None >Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 18:29 Message: Logged In: YES user_id=12800 This would be cool to add to cron/checkdbs. Here are some ideas - either have a MAX_REQUEST_AGE value in Defaults.py or a max_request_age attribute on lists if you want this to be different per-list (which might be a good idea since this is dependent on how often the list admins clear their pendings) - in the checkdbs message, keep a record of how many old ones you expire and mention it in the user notification. e.g. 17 old requests automatically expired. I'll mark this as for MM2.1 group, but it's really going to be pushed back until the following release. ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-10 20:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Mon Nov 18 23:29:47 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 15:29:47 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634303 ] Recode pipermail templates Message-ID: Patches item #634303, was opened at 2002-11-06 03:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 Category: Pipermail >Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Recode pipermail templates Initial Comment: This patch transparently recodes the pipermail templates and messages if the article and index files have a different encoding than the template language If necessary, HTML character references are generate. If recoding fails, it will proceed without exception, but produce garbage. For messages, this uses a method self._, which first invokes _, then does the recoding. This makes it necessary for _ to go back more than one frame, so the number of frames is now an optional parameter (defaulting to 1). ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-11-18 18:25 Message: Logged In: YES user_id=21627 My concern with this approach is that we might not have a codec for the encoding of the message. That means we cannot decode the message to unicode, which means we cannot htmlify unsupported characters. OTOH, we do have codecs for the preferred encodings of all supported languages. [Sorry I didn't think of this issue when we were talking about it recently] If we consider this case unlikely to occur in real life, and are prepared to produce some error message in the page if it does happen, then the approach is fine. As for PEP293: Yes, this is precisely the intention: it simplifies generating html-escaped strings, and it is more efficient than any other strategy (since the codec will call the error handling only when an encoding error occurs). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 15:46 Message: Logged In: YES user_id=12800 Feel free to shoot holes in this, but I think it might not be simpler to just get rid of the multiple _charsets stuff in HyperArch.HyperArchive. Say we always encode the indices pages with the character set of the list's preferred language, except that we also html-ify any bogus characters outside that charset. Seems to me we can chop a bunch of code and still get the results we want, even if at the expense of potentially bigger pages (which I don't care about). I'm going to commit some changes and test them out on the playground list. This seem to work well here for my test lists. Semi-related: would PEP 293 allow us to get rid of unicode_quote? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 From noreply@sourceforge.net Mon Nov 18 23:35:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 15:35:46 -0800 Subject: [Mailman-Developers] [ mailman-Patches-626550 ] Add "Date" field to admindb summary Message-ID: Patches item #626550, was opened at 2002-10-21 17:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=626550&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) >Summary: Add "Date" field to admindb summary Initial Comment: The attached patch adds the message's "Date" value to the summary fields (which already include Subject, Size, and Reason). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 18:35 Message: Logged In: YES user_id=12800 Sorry, I didn't see this one until after 2.1b4, which added a similar field, but called Received: ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2002-10-25 18:50 Message: Logged In: YES user_id=485579 Updated the patch to apply to the latest Mailman CVS code. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=626550&group_id=103 From noreply@sourceforge.net Mon Nov 18 23:59:40 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 15:59:40 -0800 Subject: [Mailman-Developers] [ mailman-Patches-625482 ] i18n List-Id Message-ID: Patches item #625482, was opened at 2002-10-18 21:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=625482&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: i18n List-Id Initial Comment: List description is a short phrase which describes list character and set by the list administrator. This is added in every list-related mail in the 'List-Id' header. With this patch, you can safely make this phrase i18n. (Otherwise, break RFC) This is a quick hack copying mostly from the code for 'Subject' header and may need optimization. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 18:59 Message: Logged In: YES user_id=12800 Thanks! I refactored the code a bit. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=625482&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:01:39 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:01:39 -0800 Subject: [Mailman-Developers] [ mailman-Patches-621257 ] MTA_ALIASES_STYLE = 'qmail-virtual' Message-ID: Patches item #621257, was opened at 2002-10-10 07:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=621257&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: John S. Denker (jsdenker) Assigned to: Nobody/Anonymous (nobody) Summary: MTA_ALIASES_STYLE = 'qmail-virtual' Initial Comment: I heartily endorse the recommendation in README.QMAIL to make a virtual mail server. The patch (attached) improves support for this, causing bin/newlist to generate the correct commands for creating the aliases. Included is the corresponding patch to the documentation. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:01 Message: Logged In: YES user_id=12800 John, there is no attachment to this patch issue. Did you forget to check the "upload and attach a file" checkbox? Please attach your patch and I'll commit it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=621257&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:04:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:04:50 -0800 Subject: [Mailman-Developers] [ mailman-Patches-605234 ] Stylesheet support for archives Message-ID: Patches item #605234, was opened at 2002-09-05 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Stylesheet support for archives Initial Comment: This patch adds a stylesheet reference to the pipermail archives, and copies in an empty stylesheet the first time the list is opened and the file doesn't already exist. The patch modifies two files in the Mailman.Archiver package, and the stylesheet should be copied into templates/en/. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:04 Message: Logged In: YES user_id=12800 Postponing this to post-MM2.1 :( ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-09-05 16:00 Message: Logged In: YES user_id=3066 Barry volunteered to integrate and test. Yay! ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:06:10 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:06:10 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-10 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 18:29 Message: Logged In: YES user_id=12800 This would be cool to add to cron/checkdbs. Here are some ideas - either have a MAX_REQUEST_AGE value in Defaults.py or a max_request_age attribute on lists if you want this to be different per-list (which might be a good idea since this is dependent on how often the list admins clear their pendings) - in the checkdbs message, keep a record of how many old ones you expire and mention it in the user notification. e.g. 17 old requests automatically expired. I'll mark this as for MM2.1 group, but it's really going to be pushed back until the following release. ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-10 20:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:06:22 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:06:22 -0800 Subject: [Mailman-Developers] [ mailman-Patches-630339 ] create list with multiple owners Message-ID: Patches item #630339, was opened at 2002-10-29 04:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: create list with multiple owners Initial Comment: Create list with multiple list owners, by 'create' CGI script and 'newlist' command line script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:06:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:06:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-605234 ] Stylesheet support for archives Message-ID: Patches item #605234, was opened at 2002-09-05 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 Category: Pipermail >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Stylesheet support for archives Initial Comment: This patch adds a stylesheet reference to the pipermail archives, and copies in an empty stylesheet the first time the list is opened and the file doesn't already exist. The patch modifies two files in the Mailman.Archiver package, and the stylesheet should be copied into templates/en/. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:04 Message: Logged In: YES user_id=12800 Postponing this to post-MM2.1 :( ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-09-05 16:00 Message: Logged In: YES user_id=3066 Barry volunteered to integrate and test. Yay! ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:08:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:08:53 -0800 Subject: [Mailman-Developers] [ mailman-Patches-605146 ] Expand "addrs" to "addresses" Message-ID: Patches item #605146, was opened at 2002-09-05 12:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605146&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Jon Parise (parise) Assigned to: Nobody/Anonymous (nobody) >Summary: Expand "addrs" to "addresses" Initial Comment: The attached patch expands the abbreviated "addrs" text to the full "addresses" word. I think this looks more professional. Because this changes the gettext string, however, localization updates will have to be made. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:08 Message: Logged In: YES user_id=12800 Accepted. I'll apply this as soon as SF cvs comes back. :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605146&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:11:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:11:34 -0800 Subject: [Mailman-Developers] [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 01:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 00:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 00:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From marilyn@deliberate.com Tue Nov 19 00:28:21 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Mon, 18 Nov 2002 16:28:21 -0800 (PST) Subject: [Mailman-Developers] mailman and voting In-Reply-To: <3DD93B92.2040609@sun.com> Message-ID: I've been waiting for this message to come to me through the list. Maybe the list is smart enough to not send a duplicate? On Mon, 18 Nov 2002, Dan Mick wrote: > > > It sounds like a great cause, but I'm not sure how much direct help I > > can provide. I'm pretty swamped right now. I don't know if there are > > any others on this list that might be able to lend a hand. > > I can't tell what needs to be done, but feel free to contact me; I might be > able to help. My immediate goal is to make an eVote/Clerk distribution that has instructions for placing eVote/Clerk on top of an already-running mailman installation. That will get me out of trouble with the Linux Journal article which, I'm told, is scheduled for the March issue. This first mailmaned-eVote will give (force-onto) all lists at the site the ability to poll themselves. If you have time and inclination, you could fix this in mailman. Even for my first release, I need to add a new argument to MailList.ApproveAddMember, MailList.ApproveAddMembers, and MailList.DeleteMember --> eVote_notif=None. If the argument is None (the default) then a mail message is generated to: eVoteAddress = 'eVote-notify@%s' % self.host_name If the argument is 0, which is how I call these functions from clone_member, eVote is not notified. eVote itself is calling clone_member and already has changed the address in the Clerk. Now then, it would be groovy indeed if the admin could set a flag on her web page to say yes or no to eVoting, if eVoting is available for the site. If the answer is no, then eVote_notif should be 0. Does that sound like a plan? I have a question. It's not real important but would eliminate some tackiness. When I generate these messages, right now I am doing this: subject = 'UNSUBSCRIBE %s' % self.real_name text = '%s has unsubscribed from %s' % (name, self.real_name) eVoteAddress = 'eVote-notify@%s' % self.host_name sender = 'mailman-owner@%s' % self.host_name msg = Message.UserNotification(eVoteAddress, sender, subject, text) HandlerAPI.DeliverToUser(self, msg) The resulting message has some instructions attached. How do I get it to stop sending the instructions? eVote doesn't read them anyway. Even when I skipped Message.UserNotification: eVoteAddress = ('eVote-notify@%s' % self.host_name) txt = ('%s has been added to %s.' % (name, self.real_name)) msg = Message.OutgoingMessage(txt) msg['Subject'] = 'SUBSCRIBE %s' % self.real_name msg['From'] = 'mailman-owner@%s' % self.host_name msg['To'] = eVoteAddress msg.recips = [eVoteAddress] HandlerAPI.DeliverToUser(self, msg) I still get that notification. How is that happening? Thank you for any help anyone can give. Marilyn From noreply@sourceforge.net Tue Nov 19 00:35:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:35:20 -0800 Subject: [Mailman-Developers] [ mailman-Patches-600368 ] i18n fix for HTMLFormatter.py Message-ID: Patches item #600368, was opened at 2002-08-26 14:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=600368&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: i18n fix for HTMLFormatter.py Initial Comment: In english the word "the" is gender-insensitive, but this is not the case in several other languages (at least italian and french). This patch tries to easy the translation process moving "the" from this string (The %(which)s is only available to the list to the %(which)s value. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:35 Message: Logged In: YES user_id=12800 Accepted ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=600368&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:41:35 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:41:35 -0800 Subject: [Mailman-Developers] [ mailman-Patches-593674 ] notify copy Message-ID: Patches item #593674, was opened at 2002-08-11 11:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=593674&group_id=103 Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: notify copy Initial Comment: in 2.1b3 when a message is held for moderation and admin_immed_notify is enabled, administrators receive a notice including a full copy of the original message. This can be annoying, especially when the message was held for being too big (and as you know this happens all the time because of Klez) This patch adds a new per-list config setting, allowing the list administrator to choose if the original message will be attached or not to the notice. Default is to attach the copy unless the message was held fort being too big. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:41 Message: Logged In: YES user_id=12800 Postponing ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=593674&group_id=103 From noreply@sourceforge.net Tue Nov 19 00:42:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 16:42:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-591258 ] Filter module and hooks Message-ID: Patches item #591258, was opened at 2002-08-05 15:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=591258&group_id=103 Category: None >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Laurence Berland (laurenceb) Assigned to: Nobody/Anonymous (nobody) Summary: Filter module and hooks Initial Comment: The Filter.py module allows one to filter messages using standard regular expression replacement. You are allowed as many or few replacements as needed, comments can be placed in the configuration, each list gets its own regular expressions, and there's a toggle to short circuit the whole process and turn it off on a per-list basis. The hooks included filter messages before they are archived. The module has been tested in this capacity and functions without any bugs. The Filter.py module is written in the standard mailman module style, and so can be cleanly placed in the pipeline if one desires, though this capacity has not been tested. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:42 Message: Logged In: YES user_id=12800 Postponing ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=591258&group_id=103 From noreply@sourceforge.net Tue Nov 19 01:05:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 17:05:42 -0800 Subject: [Mailman-Developers] [ mailman-Patches-567288 ] 'rejection-notice' breaks METAFMT_ASCII Message-ID: Patches item #567288, was opened at 2002-06-11 03:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=567288&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 7 Submitted By: Maximillian Dornseif (mdornseif) Assigned to: Nobody/Anonymous (nobody) Summary: 'rejection-notice' breaks METAFMT_ASCII Initial Comment: The variable 'rejection-notice' will not work well with METADATA_FORMAT = METAFMT_ASCII or HOLD_MESSAGES_AS_PICKLES = 0. Renaming to 'rejection_notice' helps. I guess this change breaks kompatibility with old queues. In case SF.net upload breaks: http://c0re.jp/c0de/misc/mailman-2.1b2-rejection-notice.patch Index: ./Mailman/Cgi/admindb.py - text = Utils.wrap(msgdata.get('rejection-notice', + text = Utils.wrap(msgdata.get('rejection_notice', Index: ./Mailman/Handlers/Hold.py - msgdata['rejection-notice'] = Utils.wrap(exc.rejection_notice(mlist)) + msgdata['rejection_notice'] = Utils.wrap(exc.rejection_notice(mlist)) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:05 Message: Logged In: YES user_id=12800 Note that while I don't think HOLD_MESSAGES_AS_PICKLES is affected, you're right about METADATA_FORMAT= METAFMT_ASCII. This is because that format uses execfile() and dashes aren't allowed in identifiers. Fixed, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=567288&group_id=103 From noreply@sourceforge.net Tue Nov 19 01:08:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 17:08:26 -0800 Subject: [Mailman-Developers] [ mailman-Patches-563686 ] Position cursor in login templates Message-ID: Patches item #563686, was opened at 2002-06-02 20:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id=103 Category: Web UI >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Position cursor in login templates Initial Comment: Some of my list owners wanted the cursor to be positioned in the password field for the admin & admindb pages. So I hacked a tiny bit of javascript to position the cursor in the first form field on the admlogin, options, and private templates. All languages. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:08 Message: Logged In: YES user_id=12800 Postponing to after MM2.1. No Javascript for MM2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id=103 From noreply@sourceforge.net Tue Nov 19 01:09:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 17:09:27 -0800 Subject: [Mailman-Developers] [ mailman-Patches-502668 ] new mlist option send_reminder_frequency Message-ID: Patches item #502668, was opened at 2002-01-12 08:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: new mlist option send_reminder_frequency Initial Comment: For announcement mailing lists, which get only one or two mails each year, a monthly password reminder is too much. The list administrator can toggle the send_reminder once each year, but that's error prone. The attached patch adds a list specific option send_reminder_frequency with the values monthly (default), yearly and quaterly. the mailpasswds script is changed to ask for this option. I didn't yet figure out, how to update existing lists ... ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:09 Message: Logged In: YES user_id=12800 Postponing until after MM2.1 ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-08-09 17:57 Message: Logged In: YES user_id=60903 Updated patch for the alternative (not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-05-28 02:11 Message: Logged In: YES user_id=60903 Here is the updated alternative patch not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-01-16 15:08 Message: Logged In: YES user_id=60903 Here is an alternative patch not introducing a new option, but extending the send_reminders option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 From noreply@sourceforge.net Tue Nov 19 01:10:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 17:10:04 -0800 Subject: [Mailman-Developers] [ mailman-Patches-457706 ] Union Mailing Lists membership adaptor Message-ID: Patches item #457706, was opened at 2001-09-02 05:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457706&group_id=103 Category: mail delivery >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Mark Tearle (mtearle) Assigned to: Nobody/Anonymous (nobody) Summary: Union Mailing Lists membership adaptor Initial Comment: Provides functionality/behaviour similar to how sendmail treats its aliases file. eg alias1: alias2, alias3 alias2: a, b alias3: b, c would only deliver one message to the union of alias2 and alias3 which is a, b, c Also, an example of the MemberAdaptor API ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:10 Message: Logged In: YES user_id=12800 Postponing until after MM2.1 ---------------------------------------------------------------------- Comment By: Mark Tearle (mtearle) Date: 2002-01-14 02:04 Message: Logged In: YES user_id=2554 Updated UnionMemberAdaptor for 2.1a4 (basically just extra methods) ---------------------------------------------------------------------- Comment By: Mark Tearle (mtearle) Date: 2001-09-02 05:07 Message: Logged In: YES user_id=2554 Against Mailman 2.1a3 (May need to bump version number in Version.py) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457706&group_id=103 From noreply@sourceforge.net Tue Nov 19 01:27:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 17:27:02 -0800 Subject: [Mailman-Developers] [ mailman-Patches-621257 ] MTA_ALIASES_STYLE = 'qmail-virtual' Message-ID: Patches item #621257, was opened at 2002-10-10 11:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=621257&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: John S. Denker (jsdenker) Assigned to: Nobody/Anonymous (nobody) Summary: MTA_ALIASES_STYLE = 'qmail-virtual' Initial Comment: I heartily endorse the recommendation in README.QMAIL to make a virtual mail server. The patch (attached) improves support for this, causing bin/newlist to generate the correct commands for creating the aliases. Included is the corresponding patch to the documentation. ---------------------------------------------------------------------- >Comment By: John S. Denker (jsdenker) Date: 2002-11-19 01:27 Message: Logged In: YES user_id=626701 I dunno what's going on with uploads. I thought I uploaded it months ago. I tried again just now and sourceforge refused to accept it, saying "upload cancelled". Please grab the patch from http://www.av8n.net/~jsd/virtual.patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-19 00:01 Message: Logged In: YES user_id=12800 John, there is no attachment to this patch issue. Did you forget to check the "upload and attach a file" checkbox? Please attach your patch and I'll commit it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=621257&group_id=103 From noreply@sourceforge.net Tue Nov 19 02:50:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 18:50:24 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-637403 ] remove from multilists. Message-ID: Feature Requests item #637403, was opened at 2002-11-12 13:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637403&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Victor Nolton (ven-x) Assigned to: Nobody/Anonymous (nobody) Summary: remove from multilists. Initial Comment: You guys were fantastic with my last request.. here is another one.. I run 7 mailing lists which all revolve around the same topic, just each one is a little different. it is not uncommon for people to sign up on each list. so generally when they have their email bounces or want to be removed it has to be done on every list.. is there a way to or is there a script out there that can basically do like /usr/local/mailman/bin/remove_members * someone@somewhere.com the * meaning all lists. and have it remove that from every list on the system? Just checking, I didn't see it in the help. ---------------------------------------------------------------------- Comment By: Aleksey Nogin (nogin) Date: 2002-11-18 18:50 Message: Logged In: YES user_id=28564 Dup of request 459227? ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-11-12 16:52 Message: Logged In: YES user_id=10725 --fromall already exists, at least in 2.1b4; that seems like just what you want. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637403&group_id=103 From noreply@sourceforge.net Tue Nov 19 02:53:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 18:53:34 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-640455 ] Ability to change subscribed address Message-ID: Feature Requests item #640455, was opened at 2002-11-18 18:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=640455&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Aleksey Nogin (nogin) Assigned to: Nobody/Anonymous (nobody) Summary: Ability to change subscribed address Initial Comment: It would be really great if a user could change the subscribed address (with appropriate confirmations, of course) without having to manually subscribe and unsubscribe. It would be especially nice if this could be done universally for all the lists user is subscribed to. When you address changes and you are subscribe to many lists, the current situation is *really* painful... See also request 456071. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=640455&group_id=103 From noreply@sourceforge.net Tue Nov 19 02:54:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 18:54:57 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-456071 ] Unified User Access Message-ID: Feature Requests item #456071, was opened at 2001-08-28 02:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=456071&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Unified User Access Initial Comment: Allow a user to be subscribed to X number of lists, but only need one password to access all subscription information. This would greatly improve user experience. (BTW: Great product, and the install was painless as well.) ---------------------------------------------------------------------- Comment By: Aleksey Nogin (nogin) Date: 2002-11-18 18:54 Message: Logged In: YES user_id=28564 Yes, I would like to second this. Among other things this would make requests 459227 and 640455 easier. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=456071&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:30:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:30:34 -0800 Subject: [Mailman-Developers] [ mailman-Patches-621257 ] MTA_ALIASES_STYLE = 'qmail-virtual' Message-ID: Patches item #621257, was opened at 2002-10-10 07:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=621257&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: John S. Denker (jsdenker) Assigned to: Nobody/Anonymous (nobody) Summary: MTA_ALIASES_STYLE = 'qmail-virtual' Initial Comment: I heartily endorse the recommendation in README.QMAIL to make a virtual mail server. The patch (attached) improves support for this, causing bin/newlist to generate the correct commands for creating the aliases. Included is the corresponding patch to the documentation. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 22:30 Message: Logged In: YES user_id=12800 SF has been acting wacky all day. It looks like your upload worked, even though you got that error message. Thanks. ---------------------------------------------------------------------- Comment By: John S. Denker (jsdenker) Date: 2002-11-18 20:27 Message: Logged In: YES user_id=626701 I dunno what's going on with uploads. I thought I uploaded it months ago. I tried again just now and sourceforge refused to accept it, saying "upload cancelled". Please grab the patch from http://www.av8n.net/~jsd/virtual.patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:01 Message: Logged In: YES user_id=12800 John, there is no attachment to this patch issue. Did you forget to check the "upload and attach a file" checkbox? Please attach your patch and I'll commit it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=621257&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:38:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:38:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-582567 ] No Archive Message Message-ID: Patches item #582567, was opened at 2002-07-16 20:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=582567&group_id=103 Category: Web UI >Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Susan Dridi (sdridi) Assigned to: Nobody/Anonymous (nobody) Summary: No Archive Message Initial Comment: If there are no messages in a private archive (a new list, for example), and if a user visits the archives, they are given a message with more path information than they need. For example, if I have a Mailman list called yippee and my user name is smith, the message displayed is: No file /yippee/ (/evenhigherdirectory/higherdirectory/smith/archives/private/yippee/) The path is generated by the "safetruefilename" variable which comes from: line 102 of Mailman/Cgi/private.py: path = os.environ.get('PATH_INFO') true_filename = os.path.join( mm_cfg.PRIVATE_ARCHIVE_FILE_DIR, true_path(path)) and line 194 of Mailman/Cgi/private.py except IOError: # Avoid cross-site scripting attacks safetruefilename = cgi.escape(true_filename) safepath = cgi.escape(path) print 'Content-type: text/html\n' print "

    Archive File Not Found

    " print "No file", safepath, '(%s)' % safetruefilename This is more information than a user can deduce from the URL. Users of a private list have the right to view info posted to the list. Unauthorized users shouldn't be able to learn directory structure of the host. This is not even information that the admin needs to debug anything - the admin ought to know where the archives are stored! By commenting out the variables after print "No file", safepath, the user is given a better info message, in this example, No file /yippee/ This may not be the best solution, but it works for my project:) -Susan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=582567&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:39:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:39:19 -0800 Subject: [Mailman-Developers] [ mailman-Patches-574976 ] Reply-To option, Author Name & Archives Message-ID: Patches item #574976, was opened at 2002-06-28 02:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=574976&group_id=103 Category: Pipermail >Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Susan Dridi (sdridi) Assigned to: Nobody/Anonymous (nobody) Summary: Reply-To option, Author Name & Archives Initial Comment: If the option to Reply-To the list is set, and if the "From:" field in the list.mbox file is in the format of "Poster Name" or else Poster Name then Poster Name is displayed as the Author. If the "From:" field is in the format of someone@example.com (AOL does this) then the Author is the list e-mail address. The e-mail address in the archived post is always the list e-mail address. So, it's often difficult to tell who actually posted something. Here is the patch, which just rearranges lines that were already in the code: *** pipermail.py.dist Fri Jun 1 15:30:16 2001 --- pipermail.py Mon Jun 24 12:22:46 2002 *************** *** 176,189 **** # 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 # Save the In-Reply-To:, References:, and Message-ID: lines # --- 176,188 ---- # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') ! if self.author == "": ! self.author = self.email ! 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) # Save the In-Reply-To:, References:, and Message-ID: lines # ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=574976&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:41:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:41:08 -0800 Subject: [Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements Message-ID: Patches item #573505, was opened at 2002-06-25 01:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 Category: None >Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: usenet threading improvements Initial Comment: Basically message-id munging for all messages. Might be better as an option? This helps with threading in usenet gating, as what happens is this: someone sends a mail with message- id foo@bar.com gating replaces the message-id with mailman.123.456.list@list.com list member replies via mail, "in-reply-to" header is set to the foo@bar.com now when the message is gated it can't thread because in-reply-to: (which is translated into references:) is wrong. Solution is to munge all message-ids. Doesn't really do any harm AFAICT. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:41:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:41:25 -0800 Subject: [Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements Message-ID: Patches item #573505, was opened at 2002-06-25 01:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 >Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: usenet threading improvements Initial Comment: Basically message-id munging for all messages. Might be better as an option? This helps with threading in usenet gating, as what happens is this: someone sends a mail with message- id foo@bar.com gating replaces the message-id with mailman.123.456.list@list.com list member replies via mail, "in-reply-to" header is set to the foo@bar.com now when the message is gated it can't thread because in-reply-to: (which is translated into references:) is wrong. Solution is to munge all message-ids. Doesn't really do any harm AFAICT. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:45:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:45:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-551327 ] Makefile fix so that errors propagate Message-ID: Patches item #551327, was opened at 2002-05-02 05:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id=103 >Category: configure/install >Group: Mailman 2.1 >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Daniel Resare (noa) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile fix so that errors propagate Initial Comment: While I was trying to build mailman-2.1b1 as an rpm i encountered problems with my python installation that made the build in misc fail. Unfortunately, the error didn't propagate to the toplevel make process so it took some time to track down. The attached patch simply propagates any errors from make subprocesses to the topelevel make in an automake like fashion. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 22:45 Message: Logged In: YES user_id=12800 I'm inclined to close this one. On further reflection, while it can be a pain sometimes if a build fails, at other times I want the build to continue and do as much as possible. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-03 09:38 Message: Logged In: YES user_id=12800 No problem. No the patch was easy to understand, I just don't think it goes far enough. See the simple mistake I introduced that didn't stop the build process. By comprehensive I mean that more Makefile.in's probably need to be patched so that any error in any of them will stop the build process. ---------------------------------------------------------------------- Comment By: Daniel Resare (noa) Date: 2002-05-03 04:48 Message: Logged In: YES user_id=24013 Since english is not my first language I don't understand what you mean with 'comprehensive'. Does it indicate that my patch is hard to understand? (Sounds unlikely to me) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-02 21:54 Message: Logged In: YES user_id=12800 I think a more comprehensive solution might be necessary. I introduced a delivery mistake (calling it email-2.0.3 in misc/Makefile.in) and the build process didn't stop. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:47:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:47:20 -0800 Subject: [Mailman-Developers] [ mailman-Patches-534298 ] forward unhandled bounces to admin Message-ID: Patches item #534298, was opened at 2002-03-24 08:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 Category: list administration >Group: Mailman 2.0.x Status: Open Resolution: None Priority: 7 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: forward unhandled bounces to admin Initial Comment: samba.org handles a lot of mail messages, and therefore suffers a lot of bounced messages. Mailman's automatic bounce handling is great, but the problem is that people keep dreaming up new and wierd bounce messages. With Mailman 2.0.8, if I turn on automatic bounce handling then some bouncing addresses are not correctly detected and therefore keep generating large amounts of traffic indefinitely. If I turn it off, we get about 3000 bounces per day. Some of these are just not handled yet by the BouncerAPI and need patches. In some cases there is in fact no deterministic way to work out the bouncing address (at least until we have VERP), and human intervention is required. For example, Novell's brilliant mail software includes no information in the Received lines or bounce message to indicate what the bouncing address is! Anyhow, this patch changes the behaviour of the bounce handler so that bounce messages which do not cause any positive action are forwarded to the list administrator. "Positive action" can mean noticing that the address is already disabled, or marking it as bouncing, or similar things. It doesn't include addresses which don't seem to be on the list, which probably means that we have not interpreted the message properly and more help is required. So in summary bounces which can be automatically handled will be, and others will go to the admin. I'm not sure this is the perfect behaviour, but it certainly seems like an improvement. Perhaps you want to make it more configurable. Please merge this, or something like it. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-02 21:18 Message: Logged In: YES user_id=521 Tim, that's not quite so much of a problem as you might think. When excessive bounces are detected Mailman only *disables* addresses rather than removing them. With or without this patch, bouncing addresses which are already disabled are noted in the log file and not further action is taken. Problems can occur if the address is actually removed. This can arise in two ways. One way is that the mail administrator might explicitly remove the user from the list because of manual bounce processing. In that case, any later bounces will also go through to the admin. That's the reason for my patch to add --disable to remove_members. Secondly, users might unsubscribe themselves and then have their address start bouncing. You can imagine Mailman remembering previously-subscribed members so that it could handle these cases, but that's a much bigger project, and probably best done in conjunction with VERP. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 20:03 Message: Logged In: YES user_id=521 This patch modifies the behaviour when handling bounce messages with multiple addresses, such as from Postfix. Now messages in which any of the bouncing addresses cannot be automatically handled are forwarded to the administrator. Eventually it might be nice to put a notice in the message explaining the problem -- e.g. user not found, is not a member, etc. This update also makes "digester lucked out" be considered successful processing. ---------------------------------------------------------------------- Comment By: Tim Potter (tpot) Date: 2002-03-24 18:18 Message: Logged In: YES user_id=9949 The scenario where addresses which don't seem to be on the list can be caused by bounces received after the user has been disabled due to the size of the mail queue. It may cause confusion forwarding them to the admin as there is nothing they can do about it except puzzle over why it was received. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-623783 ] Option to discard non-member postings Message-ID: Patches item #623783, was opened at 2002-10-15 17:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=623783&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Alan Batie (abatie) Assigned to: Nobody/Anonymous (nobody) Summary: Option to discard non-member postings Initial Comment: Spam has become such an epidemic that any even semi-public list must restrict postings to members only, but then it's up to the administrator to go in and manually delete it all, which is a real pain through the web interface in mailman. This patch adds an option to just throw all non-member postings away. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=623783&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-624112 ] mail password reminder bug Message-ID: Patches item #624112, was opened at 2002-10-16 10:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=624112&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Marcin Deranek (marcin_deranek) Assigned to: Nobody/Anonymous (nobody) Summary: mail password reminder bug Initial Comment: cron/mailpasswds script sends improper headers (Sender, Errors-To, X-BeenThere, Return-Path). It uses headers of first publicly available mailing list. My patch uses MAILMAN_OWNER variable from config file as sender of password reminder. Patch was created for version 2.0.13. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=624112&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-637686 ] Simple members-in-LDAP support. Message-ID: Patches item #637686, was opened at 2002-11-13 05:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=637686&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Simple members-in-LDAP support. Initial Comment: In an organization where all users are in a LDAP directory, fetching data about members of a mailing list from the directory is sometimes a good idea. For example, in my directory, I can find out all members of a certain organizational unit using a LDAP search. I still want all the other features of Mailman - archives, restrict posting to members, etc.. This patch makes it possible to define a LDAP search URI (RFC2255) in the configuration. When posting to the list, the search is executed and the resulting mail addresses are added to the normal list members. It's configurable on a per-installation-level if the ldap search configuration should be displayed. The python-ldap module is needed in order for this to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=637686&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636504 ] Configurable absolute URLs for scripts Message-ID: Patches item #636504, was opened at 2002-11-11 03:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636504&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable absolute URLs for scripts Initial Comment: In my Mailman setup I want to use http for some URLs (most of them, including the archives) for less CPU usage on the server, and https on some URLs (login with password, list administration) for better (if not good, since the passwords go in cleartext over mail anyway) security. One way of accomplishing this is to make script URLs absolute, and set DEFAULT_URL to a https hostname. This patch makes it possible to configure if GetScriptURL should by default return an absolute URL using a variable in Default.py/mm_cfg.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636504&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-615388 ] Patch to enhance Sendmail.py Message-ID: Patches item #615388, was opened at 2002-09-27 02:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615388&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Patch to enhance Sendmail.py Initial Comment: This patches changes Sendmail.py so it actually works and stops some of the problems with the old Sendmail.py like duplicate messages and other unknown conditions of sendmail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615388&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-558898 ] allow multiple values for invoking group Message-ID: Patches item #558898, was opened at 2002-05-21 18:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=558898&group_id=103 Category: command line scripts Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Nalin Dahyabhai (nsdahya1) Assigned to: Nobody/Anonymous (nobody) Summary: allow multiple values for invoking group Initial Comment: Per bug #558896, a patch which converts the allowed gid into an array of allowed gids which can be set at compile-time. Might not be complete enough, but it seems to work for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=558898&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-565346 ] suggested wording change Message-ID: Patches item #565346, was opened at 2002-06-06 11:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=565346&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Glen Foster (gafoster) Assigned to: Nobody/Anonymous (nobody) Summary: suggested wording change Initial Comment: The message: rejection = 'Non-members are not allowed to post messages to this list.' in ${PREFIX}/Mailman/Handlers/Hold.py line 60 is confusing when lists are run by membership-based organizations. It is unclear to non-subscribed posters that the word "members" refers to list members and not members of the organization itself. A suggested rewording is: rejection = 'You must subscribe to this list before you may post.' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=565346&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements Message-ID: Patches item #573505, was opened at 2002-06-25 01:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: usenet threading improvements Initial Comment: Basically message-id munging for all messages. Might be better as an option? This helps with threading in usenet gating, as what happens is this: someone sends a mail with message- id foo@bar.com gating replaces the message-id with mailman.123.456.list@list.com list member replies via mail, "in-reply-to" header is set to the foo@bar.com now when the message is gated it can't thread because in-reply-to: (which is translated into references:) is wrong. Solution is to munge all message-ids. Doesn't really do any harm AFAICT. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-590655 ] listinfo page shows lists not on server Message-ID: Patches item #590655, was opened at 2002-08-03 21:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=590655&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Joshua Eichen (jeichen) Assigned to: Nobody/Anonymous (nobody) Summary: listinfo page shows lists not on server Initial Comment: This patch allows for lists that are not on the server to be read from an xml file and displayed on the list of lists page. It supports virtual hosts and the categories patch by andy_cat You need a python xml package with a sax2 reader for this to work. There are three varibles you need to add: XML_LIBRARY: where the xml library is installed up to '_xmlplus/' OSL_FILE: where the list of off site lists are stored. USE_OFF_SITE_LISTS: set to 1 to turn on. The xml file look like this: http://testl Test description localhost http://nope.info Examplek exmaple1.com example1 Changed files: listinfo.py Defaults.py OffSiteList.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=590655&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-562061 ] Poor grammar: templates/subscribeack.txt Message-ID: Patches item #562061, was opened at 2002-05-29 16:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=562061&group_id=103 Category: None Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Dominic Hargreaves (therealdom) Assigned to: Nobody/Anonymous (nobody) Summary: Poor grammar: templates/subscribeack.txt Initial Comment: This file contains the phrase: "You may also have your password mailed to you automatically off of the Web page noted above." This is incorrect, and should read: "You may also have your password mailed to you automatically from the Web page noted above." The attached trivial patch fixes this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=562061&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:31 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:31 -0800 Subject: [Mailman-Developers] [ mailman-Patches-532315 ] More options for remove_user Message-ID: Patches item #532315, was opened at 2002-03-19 22:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=532315&group_id=103 Category: command line scripts Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: More options for remove_user Initial Comment: Sometimes the bouncer needs a little bit of manual intervention from the sysadmin. This patch adds a --disable option to remove_members, so that you can turn off delivery to people who are having trouble. It doesn't send them a notification in the way the bouncer does, and it doesn't export all of the user options. Giving the admin a way to do both of those things from the command line would be quite nice. For the moment this is useful. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-03 23:00 Message: Logged In: YES user_id=521 Here's another update: this one has --verbose, --disable, and --every-list, which are just right for getting an annoying address out of your hair. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=532315&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:28 -0800 Subject: [Mailman-Developers] [ mailman-Patches-615387 ] Umbrella list member exploder. Message-ID: Patches item #615387, was opened at 2002-09-27 02:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615387&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Umbrella list member exploder. Initial Comment: If you subscribe a list to another list with the format +somelist@mailman.domain then that line is removed and all of the members of 'somelist' are put in it's place. This allows you to have heiracial lists that apear to come from the master list, but are totaly generated on the fly by the members of other lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615387&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-594831 ] Incomplete DSN bounce tracking Message-ID: Patches item #594831, was opened at 2002-08-13 20:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=594831&group_id=103 Category: bounce processing Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Jesús Cea Avión (jcea) Assigned to: Nobody/Anonymous (nobody) Summary: Incomplete DSN bounce tracking Initial Comment: Mailman 2.0.13 here. I didn´t check Mailman 2.1.*. I'm very surprised nobody found & correct the problem before. Problem: Some valid DSN bounce notifications are not correctly parsed. A DSN message with several "packets", last packet is ignored. Reproduce: not neccesary. Code inspection should show this patch as trivially correct. Patch: In file Mailman/Bouncers/DSN.py, simply add two lines: --- DSN.py Tue Aug 13 13:22:39 2002 +++ DSN2.py Wed Aug 14 01:57:09 2002 @@ -105,6 +105,10 @@ headers[string.lower(hdr)] = string.strip(val) # now go through all the blocks, finding the recip address that is being # reported. + + if len(headers) : + blocks.append(headers) + addrs = [] for headers in blocks: if string.lower(headers.get('action', '')) <> 'failed': ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=594831&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-522080 ] Respond sensibly to blank -request email Message-ID: Patches item #522080, was opened at 2002-02-24 10:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=522080&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Seb Wills (sebwills) Assigned to: Nobody/Anonymous (nobody) Summary: Respond sensibly to blank -request email Initial Comment: In Mailman 2.0.8, if you send an emtpy message containing no commands to the -request address, the reply is also entirely blank. This extremely simple patch to MailCommandHandler.py changes this behaviour so that a blank message to a - request address returns an error telling the user that their message contained no commands, and reminding them how to get the help message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=522080&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:31 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:31 -0800 Subject: [Mailman-Developers] [ mailman-Patches-534298 ] forward unhandled bounces to admin Message-ID: Patches item #534298, was opened at 2002-03-24 08:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: forward unhandled bounces to admin Initial Comment: samba.org handles a lot of mail messages, and therefore suffers a lot of bounced messages. Mailman's automatic bounce handling is great, but the problem is that people keep dreaming up new and wierd bounce messages. With Mailman 2.0.8, if I turn on automatic bounce handling then some bouncing addresses are not correctly detected and therefore keep generating large amounts of traffic indefinitely. If I turn it off, we get about 3000 bounces per day. Some of these are just not handled yet by the BouncerAPI and need patches. In some cases there is in fact no deterministic way to work out the bouncing address (at least until we have VERP), and human intervention is required. For example, Novell's brilliant mail software includes no information in the Received lines or bounce message to indicate what the bouncing address is! Anyhow, this patch changes the behaviour of the bounce handler so that bounce messages which do not cause any positive action are forwarded to the list administrator. "Positive action" can mean noticing that the address is already disabled, or marking it as bouncing, or similar things. It doesn't include addresses which don't seem to be on the list, which probably means that we have not interpreted the message properly and more help is required. So in summary bounces which can be automatically handled will be, and others will go to the admin. I'm not sure this is the perfect behaviour, but it certainly seems like an improvement. Perhaps you want to make it more configurable. Please merge this, or something like it. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-02 21:18 Message: Logged In: YES user_id=521 Tim, that's not quite so much of a problem as you might think. When excessive bounces are detected Mailman only *disables* addresses rather than removing them. With or without this patch, bouncing addresses which are already disabled are noted in the log file and not further action is taken. Problems can occur if the address is actually removed. This can arise in two ways. One way is that the mail administrator might explicitly remove the user from the list because of manual bounce processing. In that case, any later bounces will also go through to the admin. That's the reason for my patch to add --disable to remove_members. Secondly, users might unsubscribe themselves and then have their address start bouncing. You can imagine Mailman remembering previously-subscribed members so that it could handle these cases, but that's a much bigger project, and probably best done in conjunction with VERP. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 20:03 Message: Logged In: YES user_id=521 This patch modifies the behaviour when handling bounce messages with multiple addresses, such as from Postfix. Now messages in which any of the bouncing addresses cannot be automatically handled are forwarded to the administrator. Eventually it might be nice to put a notice in the message explaining the problem -- e.g. user not found, is not a member, etc. This update also makes "digester lucked out" be considered successful processing. ---------------------------------------------------------------------- Comment By: Tim Potter (tpot) Date: 2002-03-24 18:18 Message: Logged In: YES user_id=9949 The scenario where addresses which don't seem to be on the list can be caused by bounces received after the user has been disabled due to the size of the mail queue. It may cause confusion forwarding them to the admin as there is nothing they can do about it except puzzle over why it was received. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-574976 ] Reply-To option, Author Name & Archives Message-ID: Patches item #574976, was opened at 2002-06-28 02:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=574976&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Susan Dridi (sdridi) Assigned to: Nobody/Anonymous (nobody) >Summary: Reply-To option, Author Name & Archives Initial Comment: If the option to Reply-To the list is set, and if the "From:" field in the list.mbox file is in the format of "Poster Name" or else Poster Name then Poster Name is displayed as the Author. If the "From:" field is in the format of someone@example.com (AOL does this) then the Author is the list e-mail address. The e-mail address in the archived post is always the list e-mail address. So, it's often difficult to tell who actually posted something. Here is the patch, which just rearranges lines that were already in the code: *** pipermail.py.dist Fri Jun 1 15:30:16 2001 --- pipermail.py Mon Jun 24 12:22:46 2002 *************** *** 176,189 **** # 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 # Save the In-Reply-To:, References:, and Message-ID: lines # --- 176,188 ---- # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') ! if self.author == "": ! self.author = self.email ! 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) # Save the In-Reply-To:, References:, and Message-ID: lines # ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=574976&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-526483 ] Alternative to SMART_ADDRESS_MATCH Message-ID: Patches item #526483, was opened at 2002-03-06 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=526483&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Seb Wills (sebwills) Assigned to: Nobody/Anonymous (nobody) Summary: Alternative to SMART_ADDRESS_MATCH Initial Comment: This patch adds an extra configuration parameter, COLLAPSIBLE_DOMAINS, containing a list of domains within which all subdomains are considered equivalent, for the purposes of verifying whether a post comes from a list member (for lists where only members can post). For example, if COLLAPSIBLE_DOMAINS=['cam.ac.uk', 'ox.ac.uk'] and xxx@mrao.cam.ac.uk is subscribed to a members-posting-only list, then messages from xxx@hermes.cam.ac.uk or xxx@cam.ac.uk would not be held. This is intended to be an alternative to using SMART_ADDRESS_MATCH. Advantages over using SMART_ADDRESS_MATCH are: - COLLAPSIBLE_DOMAINS only applies to domains you know use common usernames across all sub-systems (because you've explicitly listed them in mm_cfg.py - SMART_ADDRESS_MATCH only works if the more general form of the address is subscribed to the list and a more specific one is posted from, not the other way round (e.g. if xxx@cam.ac.uk is subscribed, then posts from xxx@hermes.cam.ac.uk *will* be held if you are just using SMART_ADDRESS_MATCH. COLLAPSIBLE_DOMAINS works both ways round. Note that COLLAPSIBLE_DOMAINS only applies to verifying whether a potential posting comes from a list member; it doesn't attempt to match up email addresses when people try to edit their subscription options on the web or by email. The uploaded file is a patch against 2.0.8 source. Actually it's a patch against (2.0.8 with a few other patches), but I've checked and the patch does correctly apply against virgin 2.0.8 source. If you apply this patch to the installation rather than the source, you'll need to add the COLLAPSIBLE_DOMAINS entry to your mm_cfg.py -- see comments in the patched Defaults.py.in ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=526483&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-549176 ] Per-list Templates in archive [2] Message-ID: Patches item #549176, was opened at 2002-04-26 12:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=549176&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Alessandro Forghieri (alien_life_form) Assigned to: Nobody/Anonymous (nobody) Summary: Per-list Templates in archive [2] Initial Comment: Greetings. An archive exemplifying how to use the templates for my templates-in-archive proposals - see my previous post. Cheers, alf ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=549176&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-558515 ] sendmail.py patch for security Message-ID: Patches item #558515, was opened at 2002-05-20 22:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=558515&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Peter D. Gray (pdg999) Assigned to: Nobody/Anonymous (nobody) Summary: sendmail.py patch for security Initial Comment: This is an updated Sendmail.py which avoids popen etc and is therefore (hopefully) secure. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=558515&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-582567 ] No Archive Message Message-ID: Patches item #582567, was opened at 2002-07-16 20:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=582567&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Susan Dridi (sdridi) Assigned to: Nobody/Anonymous (nobody) Summary: No Archive Message Initial Comment: If there are no messages in a private archive (a new list, for example), and if a user visits the archives, they are given a message with more path information than they need. For example, if I have a Mailman list called yippee and my user name is smith, the message displayed is: No file /yippee/ (/evenhigherdirectory/higherdirectory/smith/archives/private/yippee/) The path is generated by the "safetruefilename" variable which comes from: line 102 of Mailman/Cgi/private.py: path = os.environ.get('PATH_INFO') true_filename = os.path.join( mm_cfg.PRIVATE_ARCHIVE_FILE_DIR, true_path(path)) and line 194 of Mailman/Cgi/private.py except IOError: # Avoid cross-site scripting attacks safetruefilename = cgi.escape(true_filename) safepath = cgi.escape(path) print 'Content-type: text/html\n' print "

    Archive File Not Found

    " print "No file", safepath, '(%s)' % safetruefilename This is more information than a user can deduce from the URL. Users of a private list have the right to view info posted to the list. Unauthorized users shouldn't be able to learn directory structure of the host. This is not even information that the admin needs to debug anything - the admin ought to know where the archives are stored! By commenting out the variables after print "No file", safepath, the user is given a better info message, in this example, No file /yippee/ This may not be the best solution, but it works for my project:) -Susan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=582567&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-433767 ] Subscriber Profiler Message-ID: Patches item #433767, was opened at 2001-06-16 12:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_id=103 Category: None Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Swee Heng (sweeheng) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber Profiler Initial Comment: This is a patch to mailman-2.0.5 to implement a "subscriber profiler" feature. See my 2 postings on the mailing list for more details: o http://mail.python.org/pipermail/mailman-developers/2001-May/004270.html o http://mail.python.org/pipermail/mailman-developers/2001-June/004279.html Feel free to email me comments and queries at . (I finally figured out how to use SourceForge! :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 17:53 Message: Logged In: YES user_id=12800 Do you have any interest in porting this to MM2.1? I tried to look at the screen shots but got 404 errors, are they still available? Would you like me to add links to this patch for the MM2.0 unsupported patches page? See http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/UnofficialMailman20xPatches ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 21:40 Message: Logged In: YES user_id=17693 Hello... I install mailman from a RPM file... and install the patch manually... I need to know how COMPILE profile CGI-BIN file manually... do you know how? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-549174 ] Per-list Templates in archive Message-ID: Patches item #549174, was opened at 2002-04-26 12:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=549174&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Alessandro Forghieri (alien_life_form) Assigned to: Nobody/Anonymous (nobody) Summary: Per-list Templates in archive Initial Comment: Grettings. The included Hyperarch.py provides a drop-in replacement of the original, which also offers per-list templates in archived lists. It will look for templates in the directory [prefix]/templates/list-name (small caps version). Possible temnplates must be named as follows: arch_listing_end.tmpl arch_listing_start.tmpl article_template.tmpl index_entry_template.tmpl index_footer_template.tmpl index_header_template.tmpl TOC_entry_template.tmpl TOC_template.tmpl each has the function of the like named variable in Hyperarch - please refer to the included example for details. Format is almost html - true % characters must be escaped by doubling them (e.g. 100% => 100%%). A default is provided as a fallback for missing templates (identical to the previous default). I did not make any attempt to integrate this in the general template editing facility of mailman. It should n't be difficult though. Also missing is a way to regenerate the archives when a template changes. Installation: replace [prefix]/Mailman/Archiver/Hyperarch.py with the attachment to this message. The second attachment (see part 2) is an archive exemplifying how to use the templates. Cheers, alf ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=549174&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-510407 ] Mail sizes on Admin request page Message-ID: Patches item #510407, was opened at 2002-01-29 17:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510407&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: Mail sizes on Admin request page Initial Comment: I've been having problems with mailman in moderated list mode, where posts over the max allowed size gets thru. This patch adds the size (below subject) to the "Pending Administrative Requests" page, and also adds a warning if that size exceeds the list maximum. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510407&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:32 -0800 Subject: [Mailman-Developers] [ mailman-Patches-422468 ] Avoid multiple prefixes in Subject Message-ID: 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_id=103 Category: None Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 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_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:34 -0800 Subject: [Mailman-Developers] [ mailman-Patches-413752 ] Coerce posts to plain text. Message-ID: Patches item #413752, was opened at 2001-04-04 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 13:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103 I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 13:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 12:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 11:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 00:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-27 23:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-27 20:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 15:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 11:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 11:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 11:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 13:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 16:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 15:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 14:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-19 19:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 15:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-07 23:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 12:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 11:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:48:31 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:48:31 -0800 Subject: [Mailman-Developers] [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 03:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 02:32 Message: Logged In: YES user_id=81797 That last one had a missing quote. Try this patch: *** SpamAssassin.py.orig Fri Aug 23 00:28:59 2002 --- SpamAssassin.py Fri Aug 23 00:31:00 2002 *************** *** 30,45 **** from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_PORT = 0 ! try: ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! i = string.find(SPAMD_HOST, ':') ! if i >= 0: ! SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] ! try: SPAMD_PORT = int(SPAMD_PORT) ! except: SPAMD_PORT = None ! except: ! SPAMD_HOST = 'localhost' if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE --- 30,44 ---- from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_HOST = 'localhost' ! SPAMD_PORT = None ! if hasattr(mm_cfg, 'SPAMASSASSIN_HOST'): ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! try: ! SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) ! SPAMD_PORT = int(SPAMD_PORT) ! except ValueError: ! SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 02:19 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 02:18 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: dann frazier (dannf) Date: 2002-08-17 14:11 Message: Logged In: YES user_id=146718 hey James, found a typo. also wanted to point out: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139942&repeatmerged=yes --- SpamAssassin.py.orig Sat Aug 17 12:05:41 2002 +++ SpamAssassin.py Sat Aug 17 12:06:13 2002 @@ -35,7 +35,7 @@ SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST i = string.find(SPAMD_HOST, ':') if i >= 0: - SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] + SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], SPAMD_HOST[i+1:] try: SPAMD_PORT = int(SPAMD_PORT) except: SPAMD_PORT = None except: ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 05:00 Message: Logged In: YES user_id=146903 remembering to check the "upload file" checkbox this time ... ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 04:59 Message: Logged In: YES user_id=146903 Yet another new version that fixes a small typo. With previous messages, you couldn't approve messages that had been identified as spam once (they would get identified again when the queue got processed, instead of passing the message through). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-09 20:19 Message: Logged In: YES user_id=146903 The Mailman installation on mail.gnome.org also uses this filter. I don't think there are any stability problems with the filter. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-07-09 17:16 Message: Logged In: YES user_id=81797 FYI, I ran the previous version since installation and it seemed to work fine. I didn't run into any problems, with probably 500 messages handled. I've updated to the new version and it seems ok so far, but I've only sent about 10 messages through. Sean ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-03 00:02 Message: Logged In: YES user_id=146903 Yet another version. There were some bugs in handling of certain error conditions when talking to spamd. These would result in exceptions and the messages staying in the delivery queue :( With the new version, the message will be passed through unchecked under these conditions, and a message will be added to the error log. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-12 17:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 02:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 02:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-25 20:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:49:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:49:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-534297 ] demon.co.uk and another bounce handler Message-ID: Patches item #534297, was opened at 2002-03-24 08:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 Category: mail delivery >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: demon.co.uk and another bounce handler Initial Comment: This patch handles the format currently observed for demo.co.uk addresses as of 2002-02-24. Please merge it. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 20:10 Message: Logged In: YES user_id=521 The machine in the second format says "PP 5.0" in its SMTP banner. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 19:51 Message: Logged In: YES user_id=521 Here's an updated patch which handles another format. I can't see any identification of what software it is. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 08:08 Message: Logged In: YES user_id=521 oops, here it is ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:50:06 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:50:06 -0800 Subject: [Mailman-Developers] [ mailman-Patches-534297 ] demon.co.uk and another bounce handler Message-ID: Patches item #534297, was opened at 2002-03-24 08:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 >Category: bounce processing Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: demon.co.uk and another bounce handler Initial Comment: This patch handles the format currently observed for demo.co.uk addresses as of 2002-02-24. Please merge it. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 20:10 Message: Logged In: YES user_id=521 The machine in the second format says "PP 5.0" in its SMTP banner. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 19:51 Message: Logged In: YES user_id=521 Here's an updated patch which handles another format. I can't see any identification of what software it is. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 08:08 Message: Logged In: YES user_id=521 oops, here it is ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:50:44 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:50:44 -0800 Subject: [Mailman-Developers] [ mailman-Patches-521129 ] Bouncer for ATTMail Message-ID: Patches item #521129, was opened at 2002-02-21 14:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 >Category: bounce processing >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for ATTMail Initial Comment: Seems to use UUCP-style addresses; metadata is in the headers. You also need to insert this into the list of bouncers in BouncerAPI.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:53:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:53:19 -0800 Subject: [Mailman-Developers] [ mailman-Patches-521124 ] Bouncer for SMTP_Gateway Message-ID: Patches item #521124, was opened at 2002-02-21 14:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521124&group_id=103 >Category: bounce processing >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for SMTP_Gateway Initial Comment: Another whacko mail bounce format. We see a few of these. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521124&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:53:38 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:53:38 -0800 Subject: [Mailman-Developers] [ mailman-Patches-521110 ] patch to handle new MAIL32 bounce format Message-ID: Patches item #521110, was opened at 2002-02-21 13:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521110&group_id=103 >Category: bounce processing >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: patch to handle new MAIL32 bounce format Initial Comment: We've observed many bounce messages apparently from the MAIL32 mailer, but with slightly different text. This patch lets Mailman detect them automatically. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521110&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:54:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:54:08 -0800 Subject: [Mailman-Developers] [ mailman-Patches-520621 ] patch to handle new Yahoo! bounce format Message-ID: Patches item #520621, was opened at 2002-02-20 15:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 >Category: bounce processing >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: patch to handle new Yahoo! bounce format Initial Comment: Yahoo seem to have changed the format of their bounce messages. This patch makes 2.0.8 detect them again. >From looking at CVSweb it seems like it would work fine with 2.2 as well. Python Rocks! ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-02-21 13:42 Message: Logged In: YES user_id=521 (Silly sourceforge attachments!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:54:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:54:53 -0800 Subject: [Mailman-Developers] [ mailman-Patches-509269 ] Fix to fallback of thread by subject Message-ID: Patches item #509269, was opened at 2002-01-27 14:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=509269&group_id=103 Category: Pipermail >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Stuart Donaldson (stuartd) Assigned to: Nobody/Anonymous (nobody) Summary: Fix to fallback of thread by subject Initial Comment: The existing code in HyperDatabase.py looks like it was intending to fallback to threading by subject if the In-Reply-To and References headers were missing. However the implementation it is broken, apparently an incomplete port of some other module. This patch fixes the set_location() method, and getOldestArticle methods to allow subject threading to once again work. Note: pipermail.py has an unused database class which also implements broken versions of these methods. This patch does not fix those because they were unused. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=509269&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-605234 ] Stylesheet support for archives Message-ID: Patches item #605234, was opened at 2002-09-05 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Stylesheet support for archives Initial Comment: This patch adds a stylesheet reference to the pipermail archives, and copies in an empty stylesheet the first time the list is opened and the file doesn't already exist. The patch modifies two files in the Mailman.Archiver package, and the stylesheet should be copied into templates/en/. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:04 Message: Logged In: YES user_id=12800 Postponing this to post-MM2.1 :( ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-09-05 16:00 Message: Logged In: YES user_id=3066 Barry volunteered to integrate and test. Yay! ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-591258 ] Filter module and hooks Message-ID: Patches item #591258, was opened at 2002-08-05 15:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=591258&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Laurence Berland (laurenceb) Assigned to: Nobody/Anonymous (nobody) Summary: Filter module and hooks Initial Comment: The Filter.py module allows one to filter messages using standard regular expression replacement. You are allowed as many or few replacements as needed, comments can be placed in the configuration, each list gets its own regular expressions, and there's a toggle to short circuit the whole process and turn it off on a per-list basis. The hooks included filter messages before they are archived. The module has been tested in this capacity and functions without any bugs. The Filter.py module is written in the standard mailman module style, and so can be cleanly placed in the pipeline if one desires, though this capacity has not been tested. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:42 Message: Logged In: YES user_id=12800 Postponing ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=591258&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-630339 ] create list with multiple owners Message-ID: Patches item #630339, was opened at 2002-10-29 04:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: create list with multiple owners Initial Comment: Create list with multiple list owners, by 'create' CGI script and 'newlist' command line script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-563686 ] Position cursor in login templates Message-ID: Patches item #563686, was opened at 2002-06-02 20:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id=103 Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Position cursor in login templates Initial Comment: Some of my list owners wanted the cursor to be positioned in the password field for the admin & admindb pages. So I hacked a tiny bit of javascript to position the cursor in the first form field on the admlogin, options, and private templates. All languages. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:08 Message: Logged In: YES user_id=12800 Postponing to after MM2.1. No Javascript for MM2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-502668 ] new mlist option send_reminder_frequency Message-ID: Patches item #502668, was opened at 2002-01-12 08:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: new mlist option send_reminder_frequency Initial Comment: For announcement mailing lists, which get only one or two mails each year, a monthly password reminder is too much. The list administrator can toggle the send_reminder once each year, but that's error prone. The attached patch adds a list specific option send_reminder_frequency with the values monthly (default), yearly and quaterly. the mailpasswds script is changed to ask for this option. I didn't yet figure out, how to update existing lists ... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:09 Message: Logged In: YES user_id=12800 Postponing until after MM2.1 ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-08-09 17:57 Message: Logged In: YES user_id=60903 Updated patch for the alternative (not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-05-28 02:11 Message: Logged In: YES user_id=60903 Here is the updated alternative patch not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-01-16 15:08 Message: Logged In: YES user_id=60903 Here is an alternative patch not introducing a new option, but extending the send_reminders option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-593674 ] notify copy Message-ID: Patches item #593674, was opened at 2002-08-11 11:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=593674&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: notify copy Initial Comment: in 2.1b3 when a message is held for moderation and admin_immed_notify is enabled, administrators receive a notice including a full copy of the original message. This can be annoying, especially when the message was held for being too big (and as you know this happens all the time because of Klez) This patch adds a new per-list config setting, allowing the list administrator to choose if the original message will be attached or not to the notice. Default is to attach the copy unless the message was held fort being too big. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:41 Message: Logged In: YES user_id=12800 Postponing ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=593674&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 01:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 00:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 00:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-457706 ] Union Mailing Lists membership adaptor Message-ID: Patches item #457706, was opened at 2001-09-02 05:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457706&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Mark Tearle (mtearle) Assigned to: Nobody/Anonymous (nobody) Summary: Union Mailing Lists membership adaptor Initial Comment: Provides functionality/behaviour similar to how sendmail treats its aliases file. eg alias1: alias2, alias3 alias2: a, b alias3: b, c would only deliver one message to the union of alias2 and alias3 which is a, b, c Also, an example of the MemberAdaptor API ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 20:10 Message: Logged In: YES user_id=12800 Postponing until after MM2.1 ---------------------------------------------------------------------- Comment By: Mark Tearle (mtearle) Date: 2002-01-14 02:04 Message: Logged In: YES user_id=2554 Updated UnionMemberAdaptor for 2.1a4 (basically just extra methods) ---------------------------------------------------------------------- Comment By: Mark Tearle (mtearle) Date: 2001-09-02 05:07 Message: Logged In: YES user_id=2554 Against Mailman 2.1a3 (May need to bump version number in Version.py) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457706&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:55:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:55:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-10 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 18:29 Message: Logged In: YES user_id=12800 This would be cool to add to cron/checkdbs. Here are some ideas - either have a MAX_REQUEST_AGE value in Defaults.py or a max_request_age attribute on lists if you want this to be different per-list (which might be a good idea since this is dependent on how often the list admins clear their pendings) - in the checkdbs message, keep a record of how many old ones you expire and mention it in the user notification. e.g. 17 old requests automatically expired. I'll mark this as for MM2.1 group, but it's really going to be pushed back until the following release. ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-10 20:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:56:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:56:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 14:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 >Category: Pipermail >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd patch -p1 < ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 06:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 07:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 12:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 10:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 07:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 12:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 12:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 06:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 12:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 07:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 11:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 10:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 05:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 06:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 13:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 11:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 11:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 11:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 12:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 06:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 07:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 06:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:56:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:56:52 -0800 Subject: [Mailman-Developers] [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 14:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 >Category: Pipermail >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 06:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 06:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 12:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 13:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 13:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 10:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 10:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 06:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 12:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 07:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 10:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 05:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 06:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 13:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 11:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 16:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 11:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 11:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 06:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 07:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:58:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:58:19 -0800 Subject: [Mailman-Developers] [ mailman-Patches-457702 ] SMTP32.py raises exception on None Message-ID: Patches item #457702, was opened at 2001-09-02 04:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457702&group_id=103 >Category: bounce processing >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Mark Tearle (mtearle) Assigned to: Nobody/Anonymous (nobody) Summary: SMTP32.py raises exception on None Initial Comment: SMTP32.py was dying trying to preforms startswith on None ---------------------------------------------------------------------- Comment By: Mark Tearle (mtearle) Date: 2001-09-02 04:55 Message: Logged In: YES user_id=2554 (against Mailman 2.1a3) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457702&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:59:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:59:11 -0800 Subject: [Mailman-Developers] [ mailman-Patches-412398 ] no mailto links within archived text Message-ID: Patches item #412398, was opened at 2001-03-30 01:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=412398&group_id=103 Category: Pipermail >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: no mailto links within archived text Initial Comment: One of my list subscriber wants this because he get too many personal questions. It would be better if we can obscure all the mail addresses within text though. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=412398&group_id=103 From noreply@sourceforge.net Tue Nov 19 03:59:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 19:59:57 -0800 Subject: [Mailman-Developers] [ mailman-Patches-425589 ] Quote HTML in index pages Message-ID: Patches item #425589, was opened at 2001-05-20 03:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=425589&group_id=103 Category: Pipermail >Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Quote HTML in index pages Initial Comment: This is with reference to BUG #412893. Subject lines and Author lines with HTML are not being quoted properly. A patch to HyperArch.py solves the problem. Apparently. :) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 22:59 Message: Logged In: YES user_id=12800 We'll believe the follow up and close this patch. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-20 04:10 Message: Logged In: NO Apparently the latest version of Mailman 2.0.5 no longer has this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=425589&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:00:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:00:14 -0800 Subject: [Mailman-Developers] [ mailman-Patches-403310 ] Have a maximum member count limit on lists. Message-ID: Patches item #403310, was opened at 2001-01-18 06:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=403310&group_id=103 Category: list administration >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Peter Liljenberg (petli) Assigned to: Nobody/Anonymous (nobody) Summary: Have a maximum member count limit on lists. Initial Comment: This patch to Mailman 2.0.1 makes it possible to control how large lists can be, in terms of members. Different lists can have different limits. Warnings will be sent to the list owner when the list is getting full, at configurable percent levels. When the list becoms full, the owner will be notified and new subscription requests will be queued. When there is room in the list, either because someone else unsubscribes or the limit is increased, queued requests will be subscribed. The limit can only be controlled by a command line script, list owners can't change the limit by themselves unless they have access to the mailman installation. See README.MAXNOMEMBERS for details, which is included in the patch. ---------------------------------------------------------------------- Comment By: Peter Liljenberg (petli) Date: 2001-01-18 06:06 Message: Oh well, the patch was to large to upload here. It can be downloaded from http://www.cendio.se/~petli/mailman/ instead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=403310&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:00:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:00:50 -0800 Subject: [Mailman-Developers] [ mailman-Patches-403066 ] Auto Approval of subscriptions for certain domains Message-ID: Patches item #403066, was opened at 2001-01-01 09:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=403066&group_id=103 >Category: list administration >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Mark Tearle (mtearle) Assigned to: Nobody/Anonymous (nobody) Summary: Auto Approval of subscriptions for certain domains Initial Comment: A patch to enable automatic approval for certain domains, eg people in the example.com are automatically approved all others have to wait for the moderator ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=403066&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:02:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:02:02 -0800 Subject: [Mailman-Developers] [ mailman-Patches-402077 ] get the subscriber's email address insubscribeack.txt Message-ID: Patches item #402077, was opened at 2000-10-23 03:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402077&group_id=103 >Category: list administration >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: get the subscriber's email address insubscribeack.txt Initial Comment: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402077&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:02:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:02:43 -0800 Subject: [Mailman-Developers] [ mailman-Patches-402455 ] Generate .htaccess files containing username/passwd for list Message-ID: Patches item #402455, was opened at 2000-11-20 13:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402455&group_id=103 Category: command line scripts >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Generate .htaccess files containing username/passwd for list Initial Comment: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402455&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:03:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:03:14 -0800 Subject: [Mailman-Developers] [ mailman-Patches-401719 ] insert correct mail signature delimiter Message-ID: Patches item #401719, was opened at 2000-09-30 01:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401719&group_id=103 >Category: mail delivery >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Godisch (godisch) Assigned to: Nobody/Anonymous (nobody) Summary: insert correct mail signature delimiter Initial Comment: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401719&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:05:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:05:54 -0800 Subject: [Mailman-Developers] [ mailman-Patches-402100 ] have a nicer admin-address Message-ID: Patches item #402100, was opened at 2000-10-24 05:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402100&group_id=103 Category: mail delivery >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Fil (fill) Assigned to: Nobody/Anonymous (nobody) Summary: have a nicer admin-address Initial Comment: ---------------------------------------------------------------------- Comment By: Fil (fill) Date: 2000-10-24 05:25 Message: Instead of receiving mail from list-request@.... receive it from (listname) list-request@.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402100&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:05:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:05:56 -0800 Subject: [Mailman-Developers] [ mailman-Patches-401672 ] make 'Starting:' and 'Ending:' date localtime instead of GMT Message-ID: Patches item #401672, was opened at 2000-09-26 23:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401672&group_id=103 Category: Pipermail >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: make 'Starting:' and 'Ending:' date localtime instead of GMT Initial Comment: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401672&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:05:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:05:55 -0800 Subject: [Mailman-Developers] [ mailman-Patches-401693 ] centers the footer logos Message-ID: Patches item #401693, was opened at 2000-09-28 12:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401693&group_id=103 Category: Web UI >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Martin Godisch (godisch) Assigned to: Nobody/Anonymous (nobody) Summary: centers the footer logos Initial Comment: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401693&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:05:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:05:57 -0800 Subject: [Mailman-Developers] [ mailman-Patches-401598 ] Add command and args to LockFile's logging Message-ID: Patches item #401598, was opened at 2000-09-21 16:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 Category: list administration >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Dan Mick (dmick) Assigned to: Nobody/Anonymous (nobody) Summary: Add command and args to LockFile's logging Initial Comment: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:05:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:05:58 -0800 Subject: [Mailman-Developers] [ mailman-Patches-401383 ] Defines HTML to head and foot all Mailman documents Message-ID: Patches item #401383, was opened at 2000-08-31 21:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401383&group_id=103 Category: Web UI >Group: Mailman 2.0.x Status: Open Resolution: Postponed >Priority: 1 Submitted By: dgc (dgc) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Defines HTML to head and foot all Mailman documents Initial Comment: ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2001-06-07 17:42 Message: Logged In: YES user_id=12800 I'm reopening this one because it might be a good idea, and isn't implemented yet. Apache's mod_layout may be a better long term approach (see Chuq's mailman-developers post on the subject). ---------------------------------------------------------------------- Comment By: dgc (dgc) Date: 2000-12-15 00:10 Message: Revised for 2.0 final. This revision presumes prior application of 101379 and 101372, which are currently postponed. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-19 16:51 Message: This patch is a good idea, however I'm defering this until after 2.0 final. I'm hoping that we'll have a much more uniform way of modifying the look of a Mailman site in the future. ---------------------------------------------------------------------- Comment By: dgc (dgc) Date: 2000-08-31 21:16 Message: This adds GLOBAL_HEADER and GLOBAL_FOOTER variables in Defaults.py, then alters document presentation so that all Mailman documents show whatever they're set to at the head/foot of each page. This is for site look-n-feel stuff. By default it looks identical to what Mailman does already. Patch against 2.0beta5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401383&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:06:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:06:20 -0800 Subject: [Mailman-Developers] [ mailman-Patches-407876 ] Bug Report 407871; Bounce notifications Message-ID: Patches item #407876, was opened at 2001-03-12 05:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=407876&group_id=103 Category: list administration Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Carel Braam (carelbraam) Assigned to: Nobody/Anonymous (nobody) Summary: Bug Report 407871; Bounce notifications Initial Comment: Bounce notifications disappear ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=407876&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:07:39 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:07:39 -0800 Subject: [Mailman-Developers] [ mailman-Patches-410286 ] Change the behavior of Cgi/admin.py Message-ID: Patches item #410286, was opened at 2001-03-21 10:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=410286&group_id=103 Category: None >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Chris Ryan (cryan) Assigned to: Nobody/Anonymous (nobody) Summary: Change the behavior of Cgi/admin.py Initial Comment: This patch changes the behavior of Mailman/Cgi/admin.py to use new methods of Mailman/MailList.py (also in this patch) instead of getattr() and setattr(). This will allow for the integration of the datasource driver code that is being developed to work properly without having to overhaul admin.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=410286&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:08:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:08:04 -0800 Subject: [Mailman-Developers] [ mailman-Patches-415448 ] Recognize bounces from swbell.net. Message-ID: Patches item #415448, was opened at 2001-04-11 12:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=415448&group_id=103 >Category: bounce processing >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Recognize bounces from swbell.net. Initial Comment: This is a simple patch which causes Mailman/Bouncers/SimpleMatch.py to recognize bounce messages from swbell.net. (Might be "Sun Internet Mail Server".) This is a patch on Mailman-2.0.3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=415448&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:08:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:08:33 -0800 Subject: [Mailman-Developers] [ mailman-Patches-423983 ] Virtual hosts support fixes Message-ID: Patches item #423983, was opened at 2001-05-14 13:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=423983&group_id=103 >Category: Web UI >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: pbm (pbm) Assigned to: Nobody/Anonymous (nobody) Summary: Virtual hosts support fixes Initial Comment: Even if the VIRTUAL_HOST_OVERVIEW variable is set, all the lists are show in the administrative interface and not just that belongiing to the called virtual host. In addition, the default host name is shown in the text. This is bad, because if you decide to hide the lists belonging to different virtual hosts in the listview interface, users can show them by just clicking on the "admin interface" link. (Of course, they could just change the hostname portion of the URL, but they must knowother vhosts' hostnames). This very simple patch should fix the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=423983&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:09:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:09:12 -0800 Subject: [Mailman-Developers] [ mailman-Patches-432819 ] listinfo and virtual hosts Message-ID: Patches item #432819, was opened at 2001-06-13 12:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=432819&group_id=103 Category: Web UI >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: listinfo and virtual hosts Initial Comment: If you have virtual hosts the actual hostname from the http-server gets compared with the hostname in the URL of the list from the general configuration page. That comparison is done casesensitive and the output of my listinfo was empty. The patch makes the comparison caseinsensitive. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=432819&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:09:35 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:09:35 -0800 Subject: [Mailman-Developers] [ mailman-Patches-449681 ] Bug #449677: HyperArch.py charsets Message-ID: Patches item #449681, was opened at 2001-08-09 21:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=449681&group_id=103 Category: Pipermail >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Ben Gertzfield (che_fox) Assigned to: Nobody/Anonymous (nobody) Summary: Bug #449677: HyperArch.py charsets Initial Comment: Here's the patch for Bug #449677 (I didn't realize there was a separate Patches section til just now, whoops!). In short, HyperArch.py line 158 assumes charsets are in the form \w+ when in fact they can have characters outside of \w like - : ( ) etc. This patch makes Subject: lines with MIME encodings that use charsets like ISO-2022-JP get decoded properly in the archives. Patch is against Mailman 2.0.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=449681&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:11:39 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:11:39 -0800 Subject: [Mailman-Developers] [ mailman-Patches-483696 ] Categorisation of lists in ListInfo View Message-ID: Patches item #483696, was opened at 2001-11-20 01:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=483696&group_id=103 Category: Web UI >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: andy (andy_cat) Assigned to: Nobody/Anonymous (nobody) Summary: Categorisation of lists in ListInfo View Initial Comment: This patch allows categorisation of lists when displaying the "list of lists" in listinfo.py and admin.py It does this by adding a new property to the MailList object called "categories", a new MailList member function called GetListCategories, and a dictionary making function in Utils.py Changed files are: listinfo.py admin.py Defaults.py MailList.py Utils.py Version.py htmlformat.py Preexisting lists will show up as "Unclassified" once you apply the patch and set LISTINFO_USE_CATEGORIES = 1 in Defaults.py To set the categories, either use the Mailman list admin GUI for the list and set the "categories affilations" value (a list can be in multiple categories) in the General Options page ( Configuration Categories ) or if you have many lists to categorise it will be easier to use command line python. $python -i bin/withlist Loading list: (unlocked) >>> m.Lock() >>> m.categories='testing' >>> m.Save() >>> Unlocking (but not saving) list: Finalizing substitute your lists name for , and if you have lots you may want to script this. Python code done by Patch and these docs by ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 15:54 Message: Logged In: YES user_id=17693 Hello, I install your patch but the listinfo don't show the list names... admin is working ok... the problem is listinfo... if possible, see: http://lists.homelinux.com/mailman/listinfo,admin, etc Thanks, ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=483696&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:30:13 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:30:13 -0800 Subject: [Mailman-Developers] [ mailman-Patches-482934 ] bare format for list_lists command Message-ID: Patches item #482934, was opened at 2001-11-17 18:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=482934&group_id=103 Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: bare format for list_lists command Initial Comment: Added -b|--bare switch to list_lists script to output just the listname instead of listname and description. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 23:30 Message: Logged In: YES user_id=12800 I'm accepting this patch, but with one difference. -b prints the list's internal names, not their real names. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=482934&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:30:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:30:46 -0800 Subject: [Mailman-Developers] [ mailman-Patches-482934 ] bare format for list_lists command Message-ID: Patches item #482934, was opened at 2001-11-17 18:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=482934&group_id=103 Category: command line scripts Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: bare format for list_lists command Initial Comment: Added -b|--bare switch to list_lists script to output just the listname instead of listname and description. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 23:30 Message: Logged In: YES user_id=12800 I'm accepting this patch, but with one difference. -b prints the list's internal names, not their real names. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=482934&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:31:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:31:36 -0800 Subject: [Mailman-Developers] [ mailman-Patches-470968 ] Mailman 2.0.6 Archiving in Japanese Message-ID: Patches item #470968, was opened at 2001-10-13 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=470968&group_id=103 Category: Pipermail Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Hideaki Suzuki (h1suzuki) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman 2.0.6 Archiving in Japanese Initial Comment: Mailman 2.0.6's Pipermail does't handle rfc2237 Japanese escaping sequences. This patch handle them so that an archive containing Japanese mail can be seen figurably. I haven't seen any part of either 2.1.x or i18n version code. So, the newer mailman may not need this kind of patch.... i hope so. anyway, 2.0.6 is the newest stable version. so i believe it's worth to submit it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 23:31 Message: Logged In: YES user_id=12800 I'll go ahead and close this one since MM2.1 should not need it. ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 02:46 Message: Logged In: YES user_id=21627 As this patch is specific to one encoding (iso-2022-jp), I recommend not to incorporate it into mailman - it may break other encodings. ---------------------------------------------------------------------- Comment By: Hideaki Suzuki (h1suzuki) Date: 2001-10-30 08:11 Message: Logged In: YES user_id=254086 rfc2237.patch should have more. 1. some MTA splits a long Japanese subject into two lines, and ends the first line w/ ESC(J r.t. ESC(B. the previous patch does not handle ESC(J. replacing J w/ B in EncWord.py may be a solution. 2. when mailman needs admin's approval, it sends conferm'n w/o decoding the subject/author line. i'll submit the patches for them here later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=470968&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:35:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:35:00 -0800 Subject: [Mailman-Developers] [ mailman-Patches-478491 ] Minor edit to INSTALL file Message-ID: Patches item #478491, was opened at 2001-11-05 18:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=478491&group_id=103 Category: documentation Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Federico Grau (donfede) Assigned to: Nobody/Anonymous (nobody) Summary: Minor edit to INSTALL file Initial Comment: Minor edit to INSTALL file clarifying login used to install software. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=478491&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:35:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:35:34 -0800 Subject: [Mailman-Developers] [ mailman-Patches-470372 ] ToUsenet.py and NNTP 441 errors Message-ID: Patches item #470372, was opened at 2001-10-11 16:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=470372&group_id=103 >Category: mail delivery >Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: ToUsenet.py and NNTP 441 errors Initial Comment: When ToUsenet.py gets an NNTP 441 error, it loses the message. This patch helps strip some usually rejected headers and preserves the message if the posting fails. See http://mail.python.org/pipermail/mailman-developers/2001-October/009692.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=470372&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:36:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:36:08 -0800 Subject: [Mailman-Developers] [ mailman-Patches-490029 ] more DIRSETGID for BSD Message-ID: Patches item #490029, was opened at 2001-12-06 16:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=490029&group_id=103 Category: cross platform >Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Nobody/Anonymous (nobody) Summary: more DIRSETGID for BSD Initial Comment: As described in README.BSD, 'chmod g+s' is troublesome, so on BSD systems we % make DIRSETGID=: install That only works if all 'chmod g+s' in all Makefiles are replaced with $(DIRSETGID). Two in src/Makefile.in have been overlooked. Here's the simple patch fixing that. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2002-04-20 19:53 Message: Logged In: YES user_id=80530 I just upgraded to 2.0.10 and this patch still is not in place. What's the holdup? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=490029&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:38:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:38:24 -0800 Subject: [Mailman-Developers] [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 06:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) Assigned to: Nobody/Anonymous (nobody) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply@sourceforge.net Tue Nov 19 04:38:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 20:38:53 -0800 Subject: [Mailman-Developers] [ mailman-Patches-498747 ] Decoration fixes for MIME encodings Message-ID: Patches item #498747, was opened at 2002-01-02 17:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=498747&group_id=103 >Category: mail delivery >Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Mikhail Zabaluev (mzabaluev) Assigned to: Nobody/Anonymous (nobody) Summary: Decoration fixes for MIME encodings Initial Comment: Plugs the case when the sole body of a message is encoded in base64 or quoted-printable. In the former case, the body is left unchanged (I follow the principle of least meddling here); in the latter case, the header and footer are encoded to quoted-printable prior to being appended to the body. Also, some optimizations are made, such as the changed order of conditions. This is rather a short-term fix. For the long-time i18n solutions, I'll post a feature request later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=498747&group_id=103 From noreply@sourceforge.net Tue Nov 19 05:26:16 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 21:26:16 -0800 Subject: [Mailman-Developers] [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 00:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 From jon@csh.rit.edu Tue Nov 19 05:28:17 2002 From: jon@csh.rit.edu (Jon Parise) Date: Tue, 19 Nov 2002 00:28:17 -0500 Subject: [Mailman-Developers] SpamAssassin handler for Mailman 2.1 In-Reply-To: <20021021225908.GC27873@csh.rit.edu> References: <20021021225908.GC27873@csh.rit.edu> Message-ID: <20021119052817.GA16082@csh.rit.edu> On Mon, Oct 21, 2002 at 06:59:08PM -0400, Jon Parise wrote: > I've taken James Henstridge's SpamAssassin handler[1] and updated it > for Mailman 2.1. It's been running on the lists.horde.org mailing > lists since last night with no ill effects. I'm going to keep it > running for a few more days before I'm confident in its performance, > but I'll be submitting it (or adding it to the open patch request) > soon. > > [1] http://sourceforge.net/tracker/index.php?func=detail&aid=534577&group_id=103&atid=300103 I've just created a new patch[1] for the updated SpamAssassin handler. Comments are welcome. [1] http://sourceforge.net/tracker/index.php?func=detail&aid=640518&group_id=103&atid=300103 -- Jon Parise (jon@csh.rit.edu) :: http://www.csh.rit.edu/~jon/ From barry@python.org Tue Nov 19 06:21:46 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 01:21:46 -0500 Subject: [Mailman-Developers] SF patches Message-ID: <15833.55418.733344.569553@gargle.gargle.HOWL> I did a massive triage on the outstanding Mailman patches. I made sure every patch fell into one of three groups, depending on the version it is targeted for. The groups are: Mailman 2.0.x Mailman 2.1 Mailman 2.2 / 3.0 Each patch was also assigned a priority. Any patch falling into the Mailman 2.0.x group was given a priority of 1. Any patch falling into the 2.2/3.0 group was given a priority of 3. I plan to address the MM2.1 group patches before the final release. Anything in MM2.2/3.0 I won't consider for MM2.1 final. Same goes for MM2.0.x patches, but those I will likely also close once MM2.1 is released. If anybody has a patch in the 2.0.x or 2.2/3.0 group that they really think ought to go into MM2.1, please make a comment, and if possible, reassign it to the 2.1 group (if you don't have permission, just add a comment and I'll decide). Note that 2.0.x patches must be updated for current cvs or there's no hope of getting it in. I plan on doing a triage on the outstanding bug reports too, when possible. I want to start whittling things down to the bear necessities (sic :). -Barry From noreply@sourceforge.net Tue Nov 19 07:03:06 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 23:03:06 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-640455 ] Ability to change subscribed address Message-ID: Feature Requests item #640455, was opened at 2002-11-18 21:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=640455&group_id=103 Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Aleksey Nogin (nogin) Assigned to: Nobody/Anonymous (nobody) Summary: Ability to change subscribed address Initial Comment: It would be really great if a user could change the subscribed address (with appropriate confirmations, of course) without having to manually subscribe and unsubscribe. It would be especially nice if this could be done universally for all the lists user is subscribed to. When you address changes and you are subscribe to many lists, the current situation is *really* painful... See also request 456071. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-19 02:03 Message: Logged In: YES user_id=12800 Mailman 2.1 already supports this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=640455&group_id=103 From noreply@sourceforge.net Tue Nov 19 07:10:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 18 Nov 2002 23:10:17 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-637531 ] Request: populate Real Name from mail Message-ID: Feature Requests item #637531, was opened at 2002-11-12 21:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637531&group_id=103 >Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Request: populate Real Name from mail Initial Comment: It would be nice to have the option of letting Mailman automatically populate the Real Name field of a list's subscribers db from mail headers passing through the system. For example, if no Real Name exists for an email address and a post is received from that address, Mailman can just yank the Real Name (or whatever is supplied) from the mail header (ie From: field, etc). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=637531&group_id=103 From chuqui@plaidworks.com Tue Nov 19 07:12:34 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Mon, 18 Nov 2002 23:12:34 -0800 Subject: [Mailman-Developers] one more personalization thought. Message-ID: <46B3EEF3-FB8E-11D6-BF85-0003934516A8@plaidworks.com> I had this thought tonight. Almost hate to suggest new features, barry, but... Since not everyone is going to personalize every message, but may well turn on verping/personalization for ever "N" messages (that feature is in there, right? I remember seeing it, I think, and I know we talked about it.... Sigh, I really ought to look atht ehsource, but it's in my other computer right now...) -- I was thinking it might be nice to be able to create headers and footers that take advantage of personalization but don't leave stuff around when it's not turned on. my current footer is: _______________________________________________ Do not post admin requests to the list. They will be ignored. %(real_name)s mailing list (%(real_name)s@%(host_name)s) Help/Unsubscribe/Update your Subscription: %(user_optionsurl)s This email sent to %(user_address)s if I turn off personalization, a number of those things don't work. That really seems to limit the ability ot personalize part-time, which I expect a lot of users are going to want to do as a tradeoff on overhaead issues. So how about: %(if_personalized) _______________________________________________ Do not post admin requests to the list. They will be ignored. %(real_name)s mailing list (%(real_name)s@%(host_name)s) Help/Unsubscribe/Update your Subscription: %(user_optionsurl)s This email sent to %(user_address)s %(endif) %(if_not_personalized) generic footer %(endif) As I remember, some of your HTML also has something similar -- the listinfo pages do some kind of "if digests are turned on, show this", don't they? this is, I think, an extension of that... anyway, just putting it forward to chew on.... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek From noreply@sourceforge.net Tue Nov 19 12:49:06 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 19 Nov 2002 04:49:06 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640664 ] autowrap lines over 1000 chars Message-ID: Bugs item #640664, was opened at 2002-11-19 12:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103 Category: nntp/news Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Chris Dudley (dudleyc) Assigned to: Nobody/Anonymous (nobody) Summary: autowrap lines over 1000 chars Initial Comment: NNTP has a maximum line length of 1000 chars. emails do not have the same restriction. Would it be possible for the script which posts emails to the mailing list to autowrap all the emails at 1000 characters so that they would still be valid nntp posts? Currently i'm getting a fair few error 441 returns from NNTP because some emails exceed the line length limit. It could wrap at the last space or hyphon before the 1000th character, or something similar. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103 From sb.list@sb.org Tue Nov 19 13:43:59 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Tue, 19 Nov 2002 08:43:59 -0500 Subject: [Mailman-Developers] Why are fields initialized with "archive" Message-ID: I just cvsupped because I discovered that my current installation (about a week old) was initializing some fields in the web forms with the word "archive". I've seen this as the initial name of a list when creating one, and as the password when clicking on a subscriber's email address in Membership List mode. Unfortunately, the current CVS also does this. Is this worth filing a bug report on? Am I really "one brave soul" to update my Mailman installation from CVS? - Stoney -- Stonewall Ballard stoney@sb.org http://stoney.sb.org/ From barry@python.org Tue Nov 19 14:28:37 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 09:28:37 -0500 Subject: [Mailman-Developers] Why are fields initialized with "archive" References: Message-ID: <15834.19093.244500.590664@gargle.gargle.HOWL> >>>>> "SB" == Stonewall Ballard writes: SB> I just cvsupped because I discovered that my current SB> installation (about a week old) was initializing some fields SB> in the web forms with the word "archive". SB> I've seen this as the initial name of a list when creating SB> one, and as the password when clicking on a subscriber's email SB> address in Membership List mode. SB> Unfortunately, the current CVS also does this. SB> Is this worth filing a bug report on? It's definitely worth investigating further . I just checked my personal domains and mail.python.org and neither has this problem. Take a look at the page source, maybe these default values are coming from your browser? SB> Am I really "one brave soul" to update my Mailman installation SB> from CVS? Nope. I always try to leave the cvs trunk stable, and I usually run mail.python.org on very nearly up-to-date. BTW, I'm just going to update the NEWS file and I'll be releasing b5 today. -Barry From sb.list@sb.org Tue Nov 19 16:00:56 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Tue, 19 Nov 2002 11:00:56 -0500 Subject: [Mailman-Developers] Why are fields initialized with "archive" In-Reply-To: <15834.19093.244500.590664@gargle.gargle.HOWL> Message-ID: This turned out to be a very confused password-auto-enter function on Chimera (the OS X browser). I've got Apache protecting my archives with a basic auth, and somehow, Chimera thinks that belongs in the first field on any page in that path. Sorry for the bother. - Stoney On 11/19/02 9:28 AM, "Barry A. Warsaw" wrote: > >>>>>> "SB" == Stonewall Ballard writes: > > SB> I just cvsupped because I discovered that my current > SB> installation (about a week old) was initializing some fields > SB> in the web forms with the word "archive". > > SB> I've seen this as the initial name of a list when creating > SB> one, and as the password when clicking on a subscriber's email > SB> address in Membership List mode. > > SB> Unfortunately, the current CVS also does this. > > SB> Is this worth filing a bug report on? > > It's definitely worth investigating further . I just checked my > personal domains and mail.python.org and neither has this problem. > Take a look at the page source, maybe these default values are coming > from your browser? > > SB> Am I really "one brave soul" to update my Mailman installation > SB> from CVS? > > Nope. I always try to leave the cvs trunk stable, and I usually run > mail.python.org on very nearly up-to-date. > > BTW, I'm just going to update the NEWS file and I'll be releasing b5 > today. > > -Barry From noreply@sourceforge.net Tue Nov 19 16:28:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 19 Nov 2002 08:28:32 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore Message-ID: Bugs item #640775, was opened at 2002-11-19 16:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: David Weisgerber (davidweisgerber) Assigned to: Nobody/Anonymous (nobody) Summary: Qrunner suddenly doesn't work anymore Initial Comment: Since I checked my e-mail-account today I had over 1000 new mails where my cron daemon worries about those errors with your qrunner and listinfo.py: (1) "Traceback (most recent call last): File "/home/mailman/cron/qrunner", line 84, in ? from Mailman import Utils EOFError: EOF read where object expected" (2) "Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 40, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 36, in ? from Mailman import Utils EOFError: EOF read where object expected" Don't know why, I didn't changed something on the machine and there is noone who could change something. Hard disk space is also okay. So I couldn't figure out where the problem was but I hope you can fix it, the web page shows your 'A bug in mailman' page and this is a cat from /logs/error: "Oct 01 10:10:46 2002 (12542) listinfo: no such list "csi172": Oct 01 10:11:05 2002 (12546) Someone tried to access the admin interface for a non-existent list: csi172 Nov 19 18:10:17 2002 admin(9683): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9683): [----- Mailman Version: 2.0.11 -----] admin(9683): [----- Traceback ------] admin(9683): Traceback (most recent call last): admin(9683): File "/home/mailman/scripts/driver", line 90, in run_main admin(9683): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9683): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9683): from Mailman import Utils admin(9683): EOFError: EOF read where object expected admin(9683): [----- Python Information -----] admin(9683): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9683): sys.executable = /usr/bin/python admin(9683): sys.prefix = /usr admin(9683): sys.exec_prefix= /usr admin(9683): sys.path = /usr admin(9683): sys.platform = linux-i386 admin(9683): [----- Environment Variables -----] admin(9683): PATH_INFO: /kutro admin(9683): PYTHONPATH: /home/mailman admin(9683): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9683): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9683): SERVER_ADMIN: root@localhost admin(9683): SCRIPT_NAME: /mailman/listinfo admin(9683): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9683): REQUEST_METHOD: GET admin(9683): HTTP_HOST: md.2y.net admin(9683): HTTP_KEEP_ALIVE: 300 admin(9683): SERVER_PROTOCOL: HTTP/1.1 admin(9683): QUERY_STRING: admin(9683): REQUEST_URI: /mailman/listinfo/kutro admin(9683): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9683): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9683): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9683): HTTP_CONNECTION: keep-alive admin(9683): SERVER_NAME: md.2y.net admin(9683): REMOTE_ADDR: 192.168.0.2 admin(9683): REMOTE_PORT: 32951 admin(9683): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9683): PATH_TRANSLATED: /home/kutro-homepage admin(9683): SERVER_PORT: 80 admin(9683): GATEWAY_INTERFACE: CGI/1.1 admin(9683): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9683): SERVER_ADDR: 192.168.0.1 admin(9683): DOCUMENT_ROOT: /var/www/html Nov 19 18:10:32 2002 admin(9684): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9684): [----- Mailman Version: 2.0.11 -----] admin(9684): [----- Traceback ------] admin(9684): Traceback (most recent call last): admin(9684): File "/home/mailman/scripts/driver", line 90, in run_main admin(9684): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9684): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9684): from Mailman import Utils admin(9684): EOFError: EOF read where object expected admin(9684): [----- Python Information -----] admin(9684): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9684): sys.executable = /usr/bin/python admin(9684): sys.prefix = /usr admin(9684): sys.exec_prefix= /usr admin(9684): sys.path = /usr admin(9684): sys.platform = linux-i386 admin(9684): [----- Environment Variables -----] admin(9684): PYTHONPATH: /home/mailman admin(9684): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9684): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9684): SERVER_ADMIN: root@localhost admin(9684): SCRIPT_NAME: /mailman/listinfo admin(9684): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9684): REQUEST_METHOD: GET admin(9684): HTTP_HOST: md.2y.net admin(9684): HTTP_KEEP_ALIVE: 300 admin(9684): SERVER_PROTOCOL: HTTP/1.1 admin(9684): QUERY_STRING: admin(9684): REQUEST_URI: /mailman/listinfo admin(9684): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9684): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9684): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9684): HTTP_CONNECTION: keep-alive admin(9684): SERVER_NAME: md.2y.net admin(9684): REMOTE_ADDR: 192.168.0.2 admin(9684): REMOTE_PORT: 32951 admin(9684): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9684): SERVER_PORT: 80 admin(9684): GATEWAY_INTERFACE: CGI/1.1 admin(9684): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9684): SERVER_ADDR: 192.168.0.1 admin(9684): DOCUMENT_ROOT: /var/www/html" PS: The logs say that there were no recent activities on any list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 From barry@python.org Tue Nov 19 16:49:34 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 11:49:34 -0500 Subject: [Mailman-Developers] MM2.1b5 today? Message-ID: <15834.27550.707359.141052@gargle.gargle.HOWL> Well, if the SF project pages come up before midnight EST. :/ -Barry From barry@python.org Tue Nov 19 17:07:25 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 12:07:25 -0500 Subject: [Mailman-Developers] MM2.1b5 today? References: <15834.27550.707359.141052@gargle.gargle.HOWL> Message-ID: <15834.28621.964249.347308@gargle.gargle.HOWL> >>>>> "BAW" == Barry A Warsaw writes: BAW> Well, if the SF project pages come up before midnight EST. :/ Looks like it was just a bogus cache entry. SF is fine. -Barry From mss@mawhrin.net Tue Nov 19 17:18:28 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Tue, 19 Nov 2002 17:18:28 +0000 Subject: [Mailman-Developers] MM2.1b5 today? In-Reply-To: <15834.27550.707359.141052@gargle.gargle.HOWL> References: <15834.27550.707359.141052@gargle.gargle.HOWL> Message-ID: <20021119171828.GA2036@mawhrin.net> On Tue, Nov 19, 2002 at 11:49:34AM -0500, Barry A. Warsaw wrote: > Well, if the SF project pages come up before midnight EST. :/ Small note. You said that all files for 2.1 should have revision 2.x, there are some files (in templates/en) that are not. :) -- Misha -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021119/7d2e8fca/attachment.bin From barry@python.org Tue Nov 19 17:35:58 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 12:35:58 -0500 Subject: [Mailman-Developers] MM2.1b5 today? References: <15834.27550.707359.141052@gargle.gargle.HOWL> <20021119171828.GA2036@mawhrin.net> Message-ID: <15834.30334.982041.852714@gargle.gargle.HOWL> >>>>> "MS" == Mikhail Sobolev writes: MS> Small note. You said that all files for 2.1 should have MS> revision 2.x, there are some files (in templates/en) that are MS> not. :) True, but the templates don't bother me as much, mostly because others have checkin privs for the non-English ones. It's still a good rule to follow though and I may bump the CVS revs on the templates sometime before the 2.1 final release. -Barry From barry@python.org Tue Nov 19 18:44:35 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 13:44:35 -0500 Subject: [Mailman-Developers] RELEASED Mailman 2.1 beta 5 Message-ID: <15834.34451.968216.159620@gargle.gargle.HOWL> I've released Mailman 2.1 beta 5, and upgraded the python.org server to run this version, so with this announcement you are seeing its effects. :) Everything seems to be cruising along smoothly, so hopefully we'll have better luck with this version than with 2.1b4. See below for a list of changes since 2.1b4. Lots of bug fixes, u/i tweaks, and added support for Estonian. Be sure to read the IMPORTANT note in the change file below. If you're seeing horrible performance with Pipermail archives under 2.1b4, there is a fix available but you will have to take some manual steps. Enjoy, -Barry -------------------- snip snip -------------------- 2.1 beta 5 (19-Nov-2002) As is typical for a late beta release, this one includes the usual bug fixes, tweaks, and massive new features (just kidding). IMPORTANT: If you are using Pipermail, and you have any archives that were created or added to in 2.1b4, you will need to run bin/b4b5-archfix, followed by bin/check_perms to fix some serious performance problems. From you install directory, run "bin/b4b5-archfix --help" for details. - The personalization options have been tweaked to provide more control over mail header and decoration personalizations. In 2.1b4, when personalization was enabled, the To and Cc headers were always overwritten. But that's usually not appropriate for anything but announce lists, so now these headers aren't changed unless "Full personalization" is enabled. - You now need to go to the General category to enable emergency moderation. - The order of the hold modules in the GLOBAL_PIPELINE has changed, again. Now Moderate comes before Hold. - Estonian language support has been added. - All posted messages should now get decorated with headers and footers in a MIME-safe way. Previously, some MIME type messages didn't get decorated at all. - bin/arch grew a -q/--quiet option - bin/list_lists grew a -b/--bare option From noreply@sourceforge.net Tue Nov 19 19:27:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 19 Nov 2002 11:27:21 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640374 ] 2.1b4 Mailman bug Message-ID: Bugs item #640374, was opened at 2002-11-18 16:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b4 Mailman bug Initial Comment: When I try to access some of my lists via the web interface to moderate them I receive this error message: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admindb.py", line 227, in main show_pending_unsubs(mlist, form) File "/var/mailman/Mailman/Cgi/admindb.py", line 332, in show_pending_unsubs fullname = Utils.uncanonstr(mlist.getMemberName (addr), lang) File "/var/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/var/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member NotAMemberError: capeterson28@hotmail.com This is only a problem for some of my lists. Some lists I can log into and moderate successfully from the Web. I am running Mailman 2.1b4 on RedHat Linux 7.3. Let me know if you need more information. Thanks for your help. Paul Marshall ---------------------------------------------------------------------- >Comment By: Paul Marshall (paulmarshll) Date: 2002-11-19 13:27 Message: Logged In: YES user_id=582441 I recently upgraded to Mailman 2.1b5, however I still receive this error when I try to log into some of the lists. Thanks. Paul. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103 From andrew.clark@ucsb.edu Tue Nov 19 21:45:41 2002 From: andrew.clark@ucsb.edu (Andrew D. Clark) Date: Tue, 19 Nov 2002 13:45:41 -0800 Subject: [Mailman-Developers] bin/arch sometimes dies in 2.1b5 Message-ID: <71560000.1037742341@modulus.oit.ucsb.edu> I've had bin/arch croak on a few different list archives (though for one of the lists, it worked the 2nd time I ran it, so that's good!) with the following error: Updating HTML for article 2 Traceback (most recent call last): File "./arch", line 173, in ? main() File "./arch", line 163, in main archiver.close() File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/services/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/services/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/services/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark@ucsb.edu (805) 893-5311 From andrew.clark@ucsb.edu Tue Nov 19 22:03:19 2002 From: andrew.clark@ucsb.edu (Andrew D. Clark) Date: Tue, 19 Nov 2002 14:03:19 -0800 Subject: [Mailman-Developers] more arch problems in 2.1b5 Message-ID: <72610000.1037743399@modulus.oit.ucsb.edu> A few more lists, a few different errors: Traceback (most recent call last): File "./arch", line 173, in ? main() File "./arch", line 163, in main archiver.close() File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/services/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/services/mailman/Mailman/Archiver/HyperArch.py", line 1214, in update_article self.message(_("article file %s is missing!") TypeError: format requires a mapping At least it's working for most of the lists. Anyone have any suggestions? -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark@ucsb.edu (805) 893-5311 From andrew.clark@ucsb.edu Tue Nov 19 22:13:56 2002 From: andrew.clark@ucsb.edu (Andrew D. Clark) Date: Tue, 19 Nov 2002 14:13:56 -0800 Subject: [Mailman-Developers] fix for some arch problems Message-ID: <72890000.1037744036@modulus.oit.ucsb.edu> I love answering my own questions. Either that, or I'm far too hasty posting problems to the list before I try to fix them. In anycase, hopefully this will help anyone else who is having problems regenerating their archives. Try renaming the html archive directory for a given list to listname.backup. Then run arch again and let it recreate the whole html archive from scratch. Worked for me on a few archives that arch was barfing on. -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark@ucsb.edu (805) 893-5311 From gward@python.net Tue Nov 19 22:22:15 2002 From: gward@python.net (Greg Ward) Date: Tue, 19 Nov 2002 17:22:15 -0500 Subject: [Mailman-Developers] fix for some arch problems In-Reply-To: <72890000.1037744036@modulus.oit.ucsb.edu> References: <72890000.1037744036@modulus.oit.ucsb.edu> Message-ID: <20021119222215.GA3938@cthulhu.gerg.ca> On 19 November 2002, Andrew D. Clark said: > Try renaming the html archive directory for a given list to listname.backup. > Then run arch again and let it recreate the whole html archive from > scratch. Worked for me on a few archives that arch was barfing on. Did you remember to run bin/b4b5-archfix? Greg -- Greg Ward http://www.gerg.ca/ This message transmitted with 100% recycled electrons. From marilyn@deliberate.com Tue Nov 19 22:33:26 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Tue, 19 Nov 2002 14:33:26 -0800 (PST) Subject: [Mailman-Developers] Mail Message-ID: Mailman Developers, If a non-member of a list sends a mail message to the request address to "set nomail on passwd", the non-member gets a traceback and the admin gets an "unexpected mailman error" message. Instead, the MailCommandHandler probably wants to catch the exception and suggest to the non-user that she joins the list before she turns off her mail stream. I did this accidentally, first with an unknown password and the second time with the admin's password. Each traceback is a little different. I hope this is helpful. Thank you, Marilyn Davis The MailCommandHandler.py >From t2-request@localhost.localdomain Tue Nov 19 14:24:13 2002 Date: Tue, 19 Nov 2002 13:31:01 -0800 From: t2-request@localhost.localdomain To: marilyn@localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. >>>>> Subject line ignored: >>>>> Re: Mailman results for T2 ***** set nomail on XXXXXXXX >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at . The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 376, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/home/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError >From t2-request@localhost.localdomain Tue Nov 19 14:24:19 2002 Date: Tue, 19 Nov 2002 13:32:01 -0800 From: t2-request@localhost.localdomain To: marilyn@localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. ***** set nomail on (the admin password) >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at . The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 412, in ProcessSetCmd self.SetUserOption(sender, option_info[args[0]], value) File "/home/mailman/Mailman/MailList.py", line 206, in SetUserOption user = self.GetUserCanonicalAddress(user) File "/home/mailman/Mailman/MailList.py", line 174, in GetUserCanonicalAddress cpuser = self.GetUserSubscribedAddress(member) File "/home/mailman/Mailman/MailList.py", line 159, in GetUserSubscribedAddress member = string.lower(member) File "/usr/local/lib/python2.2/string.py", line 54, in lower return s.lower() AttributeError: 'NoneType' object has no attribute 'lower' From alaric@babcom.com Wed Nov 20 00:37:10 2002 From: alaric@babcom.com (Phil Stracchino) Date: Tue, 19 Nov 2002 19:37:10 -0500 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta 5 In-Reply-To: <15834.34451.968216.159620@gargle.gargle.HOWL> References: <15834.34451.968216.159620@gargle.gargle.HOWL> Message-ID: <20021120003710.GA25573@babylon5.babcom.com> Hey, I just had an idea for a Mailman (not necessarily 2.1) feature enhancement. Smack me if this isn't reasonable. See, I just had to get myself off an opt-out spam list that Walgreens put me on, which process involved their system mailing me a randomly computer-generated username and password in cleartext. And it occurred to me that it's bugged me for some time that Mailman sends its monthly password reminders in cleartext. Someone who can sniff your mail or peek at your mail spool can unsubscribe you from mailing lists, or change your subscription options, without your consent. So, my idea: GPG support for mailman, which the server operator has a configuration option to disable, and allow registered listmembers to upload a GPG public key. This key could be used in either or both of two ways: 1. Provide an "Encrypt password reminders using GPG" option on the user options configuration page. Mailman should not allow a user who has not uploaded a key to set this option, and if a user does try to set it without first uploading a key, it should display a message explaining that a GPG public key is required in order to enable this option, and explaining to the user how to upload a key. This will prevent persons able to spy on the user's email from obtaining the user's password by that method. 2. Provide an "Accept signed posts only" option, again on the per-user options page. If this option is set by a user, Mailman will accept posts from that user only if signed with the previously-uploaded GPG key. This will enable the user to prevent malicious individuals from forging posts to the list in their name. Once again, Mailman should not allow the option to be set if no key has been uploaded. Both of these options could optionally be made global across all lists on that server to which that user is subscribed at that address. I'd offer sample implementations for both of these, except I just maybe if I'm lucky know just about enough Python to be dangerous (i.e, not enough to write code in Python, but enough to break existing code and not understand why what I did broke it). What do you think? Thoughts, questions, LARTage? -- .********* Fight Back! It may not be just YOUR life at risk. *********. : phil stracchino : unix ronin : renaissance man : mystic zen biker geek : : alaric@babcom.com : alaric-ruthven@earthlink.net : phil@latt.net : : 2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold) : : Linux Now! ...Because friends don't let friends use Microsoft. : From danny@terweij.nl Wed Nov 20 00:45:42 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 20 Nov 2002 01:45:42 +0100 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 References: <15834.34451.968216.159620@gargle.gargle.HOWL> <20021120003710.GA25573@babylon5.babcom.com> Message-ID: <015701c2902e$27ddae10$1e00a8c0@onsnet.org> From: "Phil Stracchino" > So, my idea: GPG support for mailman, which the server operator has a > configuration option to disable, and allow registered listmembers to > upload a GPG public key. This key could be used in either or both of > two ways: I have only windows users on the lists. And this users are not familar with such things. Most of the members here are housewifes (woman who are not working and some do babysitting and take care of the husbands :) ) Danny. From alaric@babcom.com Wed Nov 20 01:34:17 2002 From: alaric@babcom.com (Phil Stracchino) Date: Tue, 19 Nov 2002 20:34:17 -0500 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: <015701c2902e$27ddae10$1e00a8c0@onsnet.org> References: <15834.34451.968216.159620@gargle.gargle.HOWL> <20021120003710.GA25573@babylon5.babcom.com> <015701c2902e$27ddae10$1e00a8c0@onsnet.org> Message-ID: <20021120013417.GA26195@babylon5.babcom.com> On Wed, Nov 20, 2002 at 01:45:42AM +0100, Danny Terweij wrote: > From: "Phil Stracchino" > > > So, my idea: GPG support for mailman, which the server operator has a > > configuration option to disable, and allow registered listmembers to > > upload a GPG public key. This key could be used in either or both of > > two ways: > > I have only windows users on the lists. And this users are not familar with > such things. > Most of the members here are housewifes (woman who are not working and some > do babysitting and take care of the husbands :) ) So the people who aren't familiar with it don't have to use it ... and it should be up to their server administrator whether to enable (and hence expose) the feature in any case. Admins running a large number of lists with many subscribers on a heavily-loaded machine may not wish to accept the additional CPU load. (This is *why* I said the server operator/admin should have the option to disable it server-wide.) As for Windows ... GPG is, as far as I know, still interoperable with PGP, which is still available for Windows. Further, a Windows program called WinPT exists which integrates GnuPG into the Windows desktop, and GPG plugins exist for both Eudora, Outlook Express, and Mozilla. Then there's GPGrelay which can be used to enable *any* Windows MUA to send and receive GPG-signed and encrypted mail. In short, being a Windows user does not mean that you cannot use GPG. I would also note that being a Windows user does not of itself mean that you are inherently too ignorant to use GPG either. Many people who might use this feature if it was available have to use Windows because that's all that their work provides, or because the software they want to use most only runs on Windows. To some extent, the Windows users are possibly among those who need such capabilities most, because of Windows' (particularly consumer Win9x's) crappy security. -- .********* Fight Back! It may not be just YOUR life at risk. *********. : phil stracchino : unix ronin : renaissance man : mystic zen biker geek : : alaric@babcom.com : alaric-ruthven@earthlink.net : phil@latt.net : : 2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold) : : Linux Now! ...Because friends don't let friends use Microsoft. : From philb@philb.us Wed Nov 20 04:44:13 2002 From: philb@philb.us (Phil Barnett) Date: Tue, 19 Nov 2002 23:44:13 -0500 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: <015701c2902e$27ddae10$1e00a8c0@onsnet.org> References: <15834.34451.968216.159620@gargle.gargle.HOWL> <20021120003710.GA25573@babylon5.babcom.com> <015701c2902e$27ddae10$1e00a8c0@onsnet.org> Message-ID: <200211192344.13146.philb@philb.us> On Tuesday 19 November 2002 07:45 pm, Danny Terweij wrote: > > So, my idea: GPG support for mailman, which the server operator has a > > configuration option to disable, and allow registered listmembers to > > upload a GPG public key. This key could be used in either or both of > > two ways: > I have only windows users on the lists. And this users are not familar = with > such things. > Most of the members here are housewifes (woman who are not working and = some > do babysitting and take care of the husbands :) ) =2E..and so we should dumb down all their software so it doesn't offend t= hem... I thinkit's a great idea. --=20 Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo From chuqui@plaidworks.com Wed Nov 20 04:51:01 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 19 Nov 2002 20:51:01 -0800 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: <200211192344.13146.philb@philb.us> Message-ID: On Tuesday, November 19, 2002, at 08:44 PM, Phil Barnett wrote: > ...and so we should dumb down all their software so it doesn't offend > them... > No, the proper question is whether it's appropriate for the list server software to take the lead in pushing this technology out to the users. In the case of List-ID and List-*, it's clear that the list server has to go first, because otherwise the mail client authors have no motivation to implement support for the headers. Asking the mail clients to add support first here is wrong. But encryption? Since no mainstream client supports encryption, and building in encryption is hard to use (even for geeks) and non-trivial, tell me why it's the list server's responsibility to blaze this trail? IMHO, it's not. Themail clients need to get their encryption act together. Until they do, builting encryption into the server tools is stupid, because it won't be compatible with stuff when they DO build it into clients (and until they do, it'll be there, but only the five geeks out there will use it). so putting it into the server when there's no acknowledged standard and no client support -- why? Explain why it's the server's responsibility to go first here? -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ From philb@philb.us Wed Nov 20 06:02:55 2002 From: philb@philb.us (Phil Barnett) Date: Wed, 20 Nov 2002 01:02:55 -0500 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: References: Message-ID: <200211200102.55148.philb@philb.us> On Tuesday 19 November 2002 11:51 pm, Chuq Von Rospach wrote: > On Tuesday, November 19, 2002, at 08:44 PM, Phil Barnett wrote: > > ...and so we should dumb down all their software so it doesn't offend > > them... > No, the proper question is whether it's appropriate for the list server > software to take the lead in pushing this technology out to the users. > In the case of List-ID and List-*, it's clear that the list server has > to go first, because otherwise the mail client authors have no > motivation to implement support for the headers. Asking the mail > clients to add support first here is wrong. > But encryption? Since no mainstream client supports encryption, and > building in encryption is hard to use (even for geeks) and non-trivial, > tell me why it's the list server's responsibility to blaze this trail? As far as I can see, there's only one reason. The server is locking the c= lient=20 into passing plaintext passwords around the planet without an alternative= =2E If=20 this alternative is not offered at the server, no client can implement it= =2E=20 The server is the only appropriate location to offer this capability.=20 Modifying the client will never make this capability available. > IMHO, it's not. Themail clients need to get their encryption act > together. Until they do, builting encryption into the server tools is > stupid, because it won't be compatible with stuff when they DO build it > into clients (and until they do, it'll be there, but only the five > geeks out there will use it). > > so putting it into the server when there's no acknowledged standard and > no client support -- why? Standards are ALWAYS out of date. That's what makes them standards. What = comes=20 before standards? Implementation by people who didn't wait for standards = to=20 exist. What happens then? Standards emerge. Do we wait for standards or go for capability? > Explain why it's the server's responsibility to go first here? I'm not sure that I agree that there are no mail clients that went first. Every mail client that I've used on both Linux and Windows supports GPG o= r PGP=20 for several years. (when I've had a choice of which mail client to use) Now, with that said, it's not the point. Why should this be implemented? Because we're sending passwords in plaintext. That alone is enough reason= =2E Ideally, these capabilities would be developed in tandem, but that would=20 require a controlled environment, such as a business controlling it's=20 deployed software. As open source advocates, we don't have that luxury. I= n=20 open source, it's always been features first, adoption and implementation= =20 second. Every open source 'standard' that we use today grew out of this=20 method. Let the strong survive and the weak die. Darwin in high speed. Sending passwords as plaintext in 2002 is downright negligent considering= the=20 current state of sniffing, monitoring and penetration. I admit that the=20 developers might need to rip out PGP/GPG and use whatever becomes the=20 standard in the future, but that is no reason to continue to treat the=20 internet like it's 1988. At least by the time this feature needs an overh= aul,=20 a working framework will exist and it will be easy to move forward with=20 whichever standard eventually evolves. It's not like our planet is flat and we'll fall off the edge if we sail t= oo=20 far... Now, with all that said, it's likely to increase support requirements (wh= ich=20 can be mitigated to some extent with proper documentation). That, IMO, an= d=20 developer time and effort would be the only good reasons to not persue op= t-in=20 sending of encrypted passwords. And, I'm not married to PGP/GPG, but I do= n't=20 think there's a more ubiquitous encryptor out there. I'm not a developer on this project and won't be in the foreseeable futur= e, so=20 from my end, it's just another wishlist item. In open source, it's the=20 developer who is king and gets to decide these things. If this problem bu= gs=20 an active project developer enough, I would expect him/her to scratch the= =20 itch. I'm content to wait for that time to arrive or not. Such is the lif= e of=20 an open source advocate. --=20 Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo From chuqui@plaidworks.com Wed Nov 20 06:18:02 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 19 Nov 2002 22:18:02 -0800 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: <200211200102.55148.philb@philb.us> Message-ID: On Tuesday, November 19, 2002, at 10:02 PM, Phil Barnett wrote: > As far as I can see, there's only one reason. The server is locking > the client > into passing plaintext passwords around the planet without an > alternative. give me a nice, usable encryption system that doesn't require a masters degree to use, and we'll use it. But don't ask a mailing list server to invent it and the infrastructure to make it work. > The server is the only appropriate location to offer this capability. > Modifying the client will never make this capability available. no, but without client support and an infrastructure to make it usable, it makes no sense to put it in the server. And it's not the server's job to lead that development. IMHO, of course. >> Explain why it's the server's responsibility to go first here? > > I'm not sure that I agree that there are no mail clients that went > first. > > Every mail client that I've used on both Linux and Windows supports > GPG or PGP > for several years. (when I've had a choice of which mail client to use) you and the other 50 geeks out there. What about normal people, like the 93% of the universe on windows or macs? > Because we're sending passwords in plaintext. That alone is enough > reason. not IMHO. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Very funny, Scotty. Now beam my clothes down here, will you? From claw@kanga.nu Wed Nov 20 08:37:26 2002 From: claw@kanga.nu (J C Lawrence) Date: Wed, 20 Nov 2002 00:37:26 -0800 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: Message from Chuq Von Rospach References: Message-ID: <28565.1037781446@kanga.nu> On Tue, 19 Nov 2002 20:51:01 -0800 Chuq Von Rospach wrote: > Explain why it's the server's responsibility to go first here? Loosely: Because it need not hurt either side. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From noreply@sourceforge.net Wed Nov 20 11:08:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 20 Nov 2002 03:08:27 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore Message-ID: Bugs item #640775, was opened at 2002-11-19 16:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 7 Submitted By: David Weisgerber (davidweisgerber) Assigned to: Nobody/Anonymous (nobody) Summary: Qrunner suddenly doesn't work anymore Initial Comment: Since I checked my e-mail-account today I had over 1000 new mails where my cron daemon worries about those errors with your qrunner and listinfo.py: (1) "Traceback (most recent call last): File "/home/mailman/cron/qrunner", line 84, in ? from Mailman import Utils EOFError: EOF read where object expected" (2) "Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 40, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 36, in ? from Mailman import Utils EOFError: EOF read where object expected" Don't know why, I didn't changed something on the machine and there is noone who could change something. Hard disk space is also okay. So I couldn't figure out where the problem was but I hope you can fix it, the web page shows your 'A bug in mailman' page and this is a cat from /logs/error: "Oct 01 10:10:46 2002 (12542) listinfo: no such list "csi172": Oct 01 10:11:05 2002 (12546) Someone tried to access the admin interface for a non-existent list: csi172 Nov 19 18:10:17 2002 admin(9683): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9683): [----- Mailman Version: 2.0.11 -----] admin(9683): [----- Traceback ------] admin(9683): Traceback (most recent call last): admin(9683): File "/home/mailman/scripts/driver", line 90, in run_main admin(9683): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9683): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9683): from Mailman import Utils admin(9683): EOFError: EOF read where object expected admin(9683): [----- Python Information -----] admin(9683): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9683): sys.executable = /usr/bin/python admin(9683): sys.prefix = /usr admin(9683): sys.exec_prefix= /usr admin(9683): sys.path = /usr admin(9683): sys.platform = linux-i386 admin(9683): [----- Environment Variables -----] admin(9683): PATH_INFO: /kutro admin(9683): PYTHONPATH: /home/mailman admin(9683): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9683): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9683): SERVER_ADMIN: root@localhost admin(9683): SCRIPT_NAME: /mailman/listinfo admin(9683): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9683): REQUEST_METHOD: GET admin(9683): HTTP_HOST: md.2y.net admin(9683): HTTP_KEEP_ALIVE: 300 admin(9683): SERVER_PROTOCOL: HTTP/1.1 admin(9683): QUERY_STRING: admin(9683): REQUEST_URI: /mailman/listinfo/kutro admin(9683): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9683): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9683): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9683): HTTP_CONNECTION: keep-alive admin(9683): SERVER_NAME: md.2y.net admin(9683): REMOTE_ADDR: 192.168.0.2 admin(9683): REMOTE_PORT: 32951 admin(9683): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9683): PATH_TRANSLATED: /home/kutro-homepage admin(9683): SERVER_PORT: 80 admin(9683): GATEWAY_INTERFACE: CGI/1.1 admin(9683): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9683): SERVER_ADDR: 192.168.0.1 admin(9683): DOCUMENT_ROOT: /var/www/html Nov 19 18:10:32 2002 admin(9684): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9684): [----- Mailman Version: 2.0.11 -----] admin(9684): [----- Traceback ------] admin(9684): Traceback (most recent call last): admin(9684): File "/home/mailman/scripts/driver", line 90, in run_main admin(9684): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9684): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9684): from Mailman import Utils admin(9684): EOFError: EOF read where object expected admin(9684): [----- Python Information -----] admin(9684): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9684): sys.executable = /usr/bin/python admin(9684): sys.prefix = /usr admin(9684): sys.exec_prefix= /usr admin(9684): sys.path = /usr admin(9684): sys.platform = linux-i386 admin(9684): [----- Environment Variables -----] admin(9684): PYTHONPATH: /home/mailman admin(9684): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9684): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9684): SERVER_ADMIN: root@localhost admin(9684): SCRIPT_NAME: /mailman/listinfo admin(9684): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9684): REQUEST_METHOD: GET admin(9684): HTTP_HOST: md.2y.net admin(9684): HTTP_KEEP_ALIVE: 300 admin(9684): SERVER_PROTOCOL: HTTP/1.1 admin(9684): QUERY_STRING: admin(9684): REQUEST_URI: /mailman/listinfo admin(9684): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9684): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9684): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9684): HTTP_CONNECTION: keep-alive admin(9684): SERVER_NAME: md.2y.net admin(9684): REMOTE_ADDR: 192.168.0.2 admin(9684): REMOTE_PORT: 32951 admin(9684): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9684): SERVER_PORT: 80 admin(9684): GATEWAY_INTERFACE: CGI/1.1 admin(9684): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9684): SERVER_ADDR: 192.168.0.1 admin(9684): DOCUMENT_ROOT: /var/www/html" PS: The logs say that there were no recent activities on any list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 From martin.whinnery@blueyonder.co.uk Wed Nov 20 12:23:31 2002 From: martin.whinnery@blueyonder.co.uk (Martin Whinnery) Date: Wed, 20 Nov 2002 12:23:31 -0000 Subject: [Mailman-Developers] Contributing extensions --- how best to structure it? Message-ID: <00bc01c2908f$a37b6010$e6faa8c0@MARTLAPIBM> Folks, I'm quietly beavering away at LDAP support using the extend.py / MemberAdaptor route. It's going ok, but I'm unsure as to where I ought to be putting things. As Greg has pointed out, It's not a good idea to mess with the distribution code. So where ought stuff to go? I illustrate: I have 4 files: LDAPMemberships.py - replaces OldStyleMemberships.py for LDAP-enabled lists. LDAPnewlist - Used instead of newlist to create an LDAP-enabled list. ldap_cfg.py - Holds (currently) global LDAP settings (server etc) extend.py - extends the mlist object to use LDAPMemberships instead of OldStyleMemberships LDAPMemberships.py I have put in /usr/local/mailman/Mailman. That's fine. LDAPnewlist goes in /usr/local/mailman/bin/. Also fine. Extend.py (and to a lesser extent ldap_cfg.py) are the problem. It's conceivable that a site might wish to have some 'normal' lists, some LDAP-based lists, some lists controlled from RapidFile, etc. How to handle this? I suppose I'm proposing a structure rooted at /usr/local/mailman/ext/ . For example, I'd have /usr/local/mailman/ext/LDAP/ldap_cfg.py and /usr/local/mailman/ext/LDAP/extend.py. An SQL extension would use /usr/local/mailman/ext/SQL/ etc. Is this the right way to go about things? Mart 'Just the assistant' network manager South Birmingham College From gward@python.net Wed Nov 20 14:25:04 2002 From: gward@python.net (Greg Ward) Date: Wed, 20 Nov 2002 09:25:04 -0500 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta 5 In-Reply-To: <20021120003710.GA25573@babylon5.babcom.com> References: <15834.34451.968216.159620@gargle.gargle.HOWL> <20021120003710.GA25573@babylon5.babcom.com> Message-ID: <20021120142504.GA4959@cthulhu.gerg.ca> On 19 November 2002, Phil Stracchino said: > Hey, I just had an idea for a Mailman (not necessarily 2.1) feature > enhancement. Smack me if this isn't reasonable. [...] > So, my idea: GPG support for mailman, which the server operator has a > configuration option to disable, and allow registered listmembers to > upload a GPG public key. This key could be used in either or both of > two ways: Sounds like a good idea to me. If I may channel Barry, you'd best wait till after 2.1. > 1. Provide an "Encrypt password reminders using GPG" option on the user Suggestion #1: say "PGP" everywhere, not "GPG". PGP is the name of the protocol/file format (err, which is it anyways?), as well as the name of an implementation that's been around for over a decade. GPG (or GnuPG) is the name of another implementation that only us geeks know about. > without first uploading a key, it should display a message explaining > that a GPG public key is required in order to enable this option, and > explaining to the user how to upload a key. Suggestion #2: give the option of supplying a key server from which to fetch my key periodically. If I'm going to use this feature, I'm going to use it on half a dozen Mailman servers throughout the world, and I don't want to have to upload my key everywhere -- or redo it when my current key expires. (I suppose you should also request a key fingerprint to go along with the key server, in which case I still have to redo some work when my key expires. Sigh. This, presumably, is what Chuq meant by needing a master's degree to use the bloody thing.) Greg -- Greg Ward http://www.gerg.ca/ I'd rather have a bottle in front of me than have to have a frontal lobotomy. From gward@python.net Wed Nov 20 14:43:15 2002 From: gward@python.net (Greg Ward) Date: Wed, 20 Nov 2002 09:43:15 -0500 Subject: [Mailman-Developers] Shutting down mailmanctl for upgrade Message-ID: <20021120144315.GA5048@cthulhu.gerg.ca> I just noticed that UPGRADING doesn't say anything about shutting down mailmanctl around an upgrade. Should it? Greg -- Greg Ward http://www.gerg.ca/ I hope something GOOD came in the mail today so I have a REASON to live!! From andrew.clark@ucsb.edu Wed Nov 20 18:35:29 2002 From: andrew.clark@ucsb.edu (Andrew D. Clark) Date: Wed, 20 Nov 2002 10:35:29 -0800 Subject: [Mailman-Developers] bin/arch problems with unknown encodings Message-ID: <61800000.1037817329@modulus.oit.ucsb.edu> Under Mailman 2.1b5, when I run bin/arch on one of my lists for which I turned off pipermail archiving during the 2.1b3-pipermail-archiving-performance-sucks-badly period it dies complaining: "unknown encoding: big5_tw". The mbox for this list is huge, and I'm having trouble locating exactly which message is killing arch. Is there a way to either ignore non us-ascii messages when archiving (all the members of this private list only speak/read English, I'm not simply another arrogant American :) ), or a better way to scrub or locate such messages? I'm having similar problems with some other lists: "TypeError: unicode() argument 2 must be string, not None" BTW, I skipped Mailman 2.1b4 completely, so would running b4b5-archfix still be necessary/beneficial? BTW2, kudos to the cabal on 2.1b5! An older list archive created under mailman 2.0.x reported 20 messages in the archive, when I regenerated that list archive, the new archive reported 16. A manual peek at the mbox file showed 16 messages :) -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark@ucsb.edu (805) 893-5311 From sb.list@sb.org Wed Nov 20 20:10:29 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Wed, 20 Nov 2002 15:10:29 -0500 Subject: [Mailman-Developers] Alternate authentication mechanism (was ... RELEASED Mailman 2.1 beta 5) In-Reply-To: <20021120003710.GA25573@babylon5.babcom.com> Message-ID: On 11/19/02 7:37 PM, "Phil Stracchino" wrote: > Hey, I just had an idea for a Mailman (not necessarily 2.1) feature > enhancement. Smack me if this isn't reasonable. > > (GPG scheme elided) > > What do you think? Thoughts, questions, LARTage? > Nobody on any of the lists I run would have a clue on how to use this. I'd like to see a different mechanism - when you want to change your account info, Mailman would email you a URL containing a short-lived session key that you could use to get to your account page. No passwords. - Stoney From noreply@sourceforge.net Wed Nov 20 20:11:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 20 Nov 2002 12:11:23 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-641436 ] traceback for set nomail for non-member Message-ID: Bugs item #641436, was opened at 2002-11-20 20:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641436&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Marilyn Davis (marilyndavis) Assigned to: Nobody/Anonymous (nobody) Summary: traceback for set nomail for non-member Initial Comment: If a non-member of a list sends a mail message to the request address to "set nomail on passwd", the non-member gets a traceback and the admin gets an "unexpected mailman error" message. Instead, the MailCommandHandler probably wants to catch the exception and suggest to the non-user that she joins the list before she turns off her mail stream. I did this accidentally, first with an unknown password and the second time with the admin's password. Each traceback is a little different. I hope this is helpful. Thank you, Marilyn Davis The MailCommandHandler.py >From t2-request@localhost.localdomain Tue Nov 19 14:24:13 2002 Date: Tue, 19 Nov 2002 13:31:01 -0800 From: t2-request@localhost.localdomain To: marilyn@localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. >>>>> Subject line ignored: >>>>> Re: Mailman results for T2 ***** set nomail on XXXXXXXX >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at . The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 376, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/home/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError >From t2-request@localhost.localdomain Tue Nov 19 14:24:19 2002 Date: Tue, 19 Nov 2002 13:32:01 -0800 From: t2-request@localhost.localdomain To: marilyn@localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. ***** set nomail on (the admin password) >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at . The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 412, in ProcessSetCmd self.SetUserOption(sender, option_info[args[0]], value) File "/home/mailman/Mailman/MailList.py", line 206, in SetUserOption user = self.GetUserCanonicalAddress(user) File "/home/mailman/Mailman/MailList.py", line 174, in GetUserCanonicalAddress cpuser = self.GetUserSubscribedAddress(member) File "/home/mailman/Mailman/MailList.py", line 159, in GetUserSubscribedAddress member = string.lower(member) File "/usr/local/lib/python2.2/string.py", line 54, in lower return s.lower() AttributeError: 'NoneType' object has no attribute 'lower' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641436&group_id=103 From carson@taltos.org Wed Nov 20 21:22:43 2002 From: carson@taltos.org (Carson Gaspar) Date: Wed, 20 Nov 2002 16:22:43 -0500 Subject: [Mailman-Developers] Suppressing mailman non-error responses Message-ID: <380213203.1037809363@[192.168.20.2]> Currently, when you subscribe to a mailing list, the following occurs: -> -request "subscribe" <- received subscribe (optional cookie send, respond) <- subscribe results <- list welcome I'd _really_ like to not send the "I parsed your request and got no errors" e-mail, as it is entirely redundant. Obviously, if there were errors in the request, it's a different story. -- Carson From sb.list@sb.org Wed Nov 20 22:59:43 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Wed, 20 Nov 2002 17:59:43 -0500 Subject: [Mailman-Developers] Suppressing mailman non-error responses In-Reply-To: <380213203.1037809363@[192.168.20.2]> Message-ID: On 11/20/02 4:22 PM, "Carson Gaspar" wrote: > Currently, when you subscribe to a mailing list, the following occurs: > > -> -request "subscribe" > <- received subscribe > (optional cookie send, respond) > <- subscribe results > <- list welcome > > I'd _really_ like to not send the "I parsed your request and got no errors" > e-mail, as it is entirely redundant. Obviously, if there were errors in the > request, it's a different story. My users are frequently confused by that message, especially since it typically complains about the irrelevant text in the confirmation message. I would gladly avoid sending this unless there was a confirmation failure. - Stoney From noreply@sourceforge.net Wed Nov 20 23:38:22 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 20 Nov 2002 15:38:22 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-641564 ] quoted-printable in pipermail Message-ID: Bugs item #641564, was opened at 2002-11-20 18:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641564&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Thomas Krichel (thomaskrichel) Assigned to: Nobody/Anonymous (nobody) Summary: quoted-printable in pipermail Initial Comment: I am using version on debian 2.0.13-2. Some of my mail list owners send email with quoted- printable encoding. Such emails are distributed with the encoding stripped. In the ???.mbox/???.mbox file, a header that say that the message has quoted-printable encoding is present. After pipermail is run, in the .txt file, the encoding information header is no longer present, but the encoding is not decoded. This is annoying as some of many of our mails have urls. The urls fail to resolve because of the encoding. Best wishes, Thomas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641564&group_id=103 From marilyn@deliberate.com Thu Nov 21 00:58:26 2002 From: marilyn@deliberate.com (Marilyn Davis) Date: Wed, 20 Nov 2002 16:58:26 -0800 (PST) Subject: [Mailman-Developers] Alternate authentication mechanism (was ... RELEASED Mailman 2.1 beta 5) In-Reply-To: Message-ID: On Wed, 20 Nov 2002, Stonewall Ballard wrote: > On 11/19/02 7:37 PM, "Phil Stracchino" wrote: > > > Hey, I just had an idea for a Mailman (not necessarily 2.1) feature > > enhancement. Smack me if this isn't reasonable. > > > > (GPG scheme elided) > > > > What do you think? Thoughts, questions, LARTage? > > > > Nobody on any of the lists I run would have a clue on how to use this. > > I'd like to see a different mechanism - when you want to change your account > info, Mailman would email you a URL containing a short-lived session key > that you could use to get to your account page. No passwords. > > - Stoney Or, mailman can require a confirmation message, like it does for subscriptions. It would be good if a group could turn on encryption to encrypt the messages and keep them off the web. I suppose that's a big project. Marilyn > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > From edlau@ucf.ics.uci.edu Thu Nov 21 02:33:35 2002 From: edlau@ucf.ics.uci.edu (Edmund Lau) Date: Wed, 20 Nov 2002 18:33:35 -0800 (PST) Subject: [Mailman-Developers] Emer moderation Message-ID: So I've actually needed to use this feature. This might be a bug in 2.1b5 from CVS 11/19 and I need someone else to confirm this. Setting anyone's moderation bit on or off while under emergency moderation clears the emergency moderation bit. -Ed From edlau@ucf.ics.uci.edu Thu Nov 21 02:56:18 2002 From: edlau@ucf.ics.uci.edu (Edmund Lau) Date: Wed, 20 Nov 2002 18:56:18 -0800 (PST) Subject: [Mailman-Developers] Re: Emer moderation In-Reply-To: Message-ID: I think I see why now. At the bottom of the web UI for the membership management area, there is a "set everyone's moderation bit" thing. That seems to always select off, regardless of the general emergency moderation. This would also explain why some people I selected to be moderated came off. -Ed On Wed, 20 Nov 2002, Edmund Lau wrote: > So I've actually needed to use this feature. This might be a bug in > 2.1b5 from CVS 11/19 and I need someone else to confirm this. > > Setting anyone's moderation bit on or off while under emergency moderation > clears the emergency moderation bit. > > -Ed > > From edlau@ucf.ics.uci.edu Thu Nov 21 03:05:55 2002 From: edlau@ucf.ics.uci.edu (Edmund Lau) Date: Wed, 20 Nov 2002 19:05:55 -0800 (PST) Subject: [Mailman-Developers] Re: Emer moderation In-Reply-To: Message-ID: Sorry, I take that back. It seems to be affected after clicking on "submit your changes" regardless changes. (I didn't see the small "set" button on the right.) Sorry also for flooding everyone's inbox. -Ed On Wed, 20 Nov 2002, Edmund Lau wrote: > I think I see why now. > > At the bottom of the web UI for the membership management area, there is a > "set everyone's moderation bit" thing. That seems to always select off, > regardless of the general emergency moderation. This would also explain > why some people I selected to be moderated came off. > > -Ed > > > On Wed, 20 Nov 2002, Edmund Lau wrote: > > > So I've actually needed to use this feature. This might be a bug in > > 2.1b5 from CVS 11/19 and I need someone else to confirm this. > > > > Setting anyone's moderation bit on or off while under emergency moderation > > clears the emergency moderation bit. > > > > -Ed From barry@python.org Thu Nov 21 04:58:48 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 20 Nov 2002 23:58:48 -0500 Subject: [Mailman-Developers] Re: Emer moderation References: Message-ID: <15836.26632.780896.880789@gargle.gargle.HOWL> >>>>> "EL" == Edmund Lau writes: EL> Sorry, I take that back. It seems to be affected after EL> clicking on "submit your changes" regardless changes. (I EL> didn't see the small "set" button on the right.) Sorry also EL> for flooding everyone's inbox. Nope, thanks for reporting it! Fixed in cvs now. -Barry From barry@python.org Thu Nov 21 05:26:25 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 00:26:25 -0500 Subject: [Mailman-Developers] Suppressing mailman non-error responses References: <380213203.1037809363@[192.168.20.2]> Message-ID: <15836.28289.364792.817430@gargle.gargle.HOWL> >>>>> "CG" == Carson Gaspar writes: CG> I'd _really_ like to not send the "I parsed your request and CG> got no errors" e-mail, as it is entirely redundant. Obviously, CG> if there were errors in the request, it's a different story. I believe I have a fix for this. The confirmation is suppressed if - it confirmed a subscription and send_welcome_msg is true - it confirmed an unsub and send_goodbye_msg is true Otherwise, it sends the confirmation results. -Barry From terri@zone12.com Thu Nov 21 06:01:16 2002 From: terri@zone12.com (Terri Oda) Date: Thu, 21 Nov 2002 01:01:16 -0500 Subject: [Mailman-Developers] Alternate authentication mechanism (was ... RELEASED Mailman 2.1 beta 5) In-Reply-To: References: <20021120003710.GA25573@babylon5.babcom.com> Message-ID: <20021121060116.GB461@ostraya.zone12.com> On Wed, Nov 20, 2002 at 03:10:29PM -0500, Stonewall Ballard wrote: > On 11/19/02 7:37 PM, "Phil Stracchino" wrote: > > > Hey, I just had an idea for a Mailman (not necessarily 2.1) feature > > enhancement. Smack me if this isn't reasonable. > > > > (GPG scheme elided) > > > > What do you think? Thoughts, questions, LARTage? > > > > Nobody on any of the lists I run would have a clue on how to use this. > And to contrast, I've not only had people request this sort of thing, or express surprise that there is no secure way to do passwords, but I've also gotten mail from one user had some, um, choice words for the list administrators when she discovered that her password was sent in plaintext. (It's hard to feel sorry for someone who claims to be concerned about security and yet couldn't be bothered to read the warnings or say, notice that she was sending her password over http in order to subscribe in the first place. I wonder if I kept that message for posterity. She gave us quite the lecture, then unsubscribed in disgust, and hopefully changed that password anywhere else she was using it.) Anyhow, I think giving a PGP option is a great idea. As long as we're not forcing everyone to use it, it'd be a nice alternative for those people who do care. Although if it's not combined with a secure web interface, I'm not too sure it'd have much point. Terri From lrosa@mail.hypertrek.info Thu Nov 21 09:36:19 2002 From: lrosa@mail.hypertrek.info (Luigi Rosa) Date: Thu, 21 Nov 2002 10:36:19 +0100 Subject: [Mailman-Developers] [B5] MIME remapping Message-ID: <4499171.20021121103619@mail.hypertrek.info> Hello, since I installaed B5 my messages are reconverted in multipart/mixed with two part, both text/plain: the first part is my message, the second is the footer added by Mailman. I suspected that this was caused by filtering options, but the problem is still there even after disabling the msg filetring. Any suggestion? Note that I write the msgs using TheBat!, that cannot send msgs othar than pure text and puts this header: Content-Type: text/plain; charset=us-ascii -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info From R.Barrett@ftel.co.uk Thu Nov 21 10:45:11 2002 From: R.Barrett@ftel.co.uk (Richard Barrett) Date: Thu, 21 Nov 2002 10:45:11 +0000 Subject: [Mailman-Developers] exit status from Python mail scripts Message-ID: <5.1.1.6.0.20021120203726.03e54788@pop.ftel.co.uk> Question relates to various Mailman scripts run by the MTA for delivering to MM. Is there a particular reason why, on abnormal exit, the exit status returned by these scripts is not drawn from the values with defined meanings in /usr/include/sysexits.h ? From barry@python.org Thu Nov 21 13:22:03 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 08:22:03 -0500 Subject: [Mailman-Developers] [B5] MIME remapping References: <4499171.20021121103619@mail.hypertrek.info> Message-ID: <15836.56827.271764.908455@gargle.gargle.HOWL> >>>>> "LR" == Luigi Rosa writes: LR> since I installaed B5 my messages are reconverted in LR> multipart/mixed with two part, both text/plain: the first part LR> is my message, the second is the footer added by Mailman. LR> I suspected that this was caused by filtering options, but the LR> problem is still there even after disabling the msg filetring. LR> Any suggestion? LR> Note that I write the msgs using TheBat!, that cannot send LR> msgs othar than pure text and puts this header: LR> Content-Type: text/plain; charset=us-ascii Does the problem go away if you set your non-digest options msg_header and msg_footer to empty strings? If so, then either you're not actually sending text/plain messages, or your list is configured to use a language other than English. b5 adds headers and footers to messages with incompatible MIME types by wrapping them in multipart/mixed. -Barry From barry@python.org Thu Nov 21 13:25:25 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 08:25:25 -0500 Subject: [Mailman-Developers] exit status from Python mail scripts References: <5.1.1.6.0.20021120203726.03e54788@pop.ftel.co.uk> Message-ID: <15836.57029.576848.201918@gargle.gargle.HOWL> >>>>> "RB" == Richard Barrett writes: RB> Is there a particular reason why, on abnormal exit, the exit RB> status returned by these scripts is not drawn from the values RB> with defined meanings in /usr/include/sysexits.h ? Probably no good one. IOW, its historical. Care to provide a patch? -Barry From lrosa@mail.hypertrek.info Thu Nov 21 15:49:37 2002 From: lrosa@mail.hypertrek.info (Luigi Rosa) Date: Thu, 21 Nov 2002 16:49:37 +0100 Subject: [Mailman-Developers] [B5] MIME remapping In-Reply-To: <20021121133556.GA4698@pioppo.wired> References: <4499171.20021121103619@mail.hypertrek.info> <15836.56827.271764.908455@gargle.gargle.HOWL> <20021121133556.GA4698@pioppo.wired> Message-ID: <16822897468.20021121164937@mail.hypertrek.info> Hello Simone, Thursday, November 21, 2002, 2:35:56 PM, you wrote: >> then either you're not actually sending text/plain messages, or >> your list is configured to use a language other than English. b5 adds >> headers and footers to messages with incompatible MIME types by >> wrapping them in multipart/mixed. SP> That's right. SP> I believe that Luigi has the list configured with lang=it and because SP> of this headers/footers are marked iso-8859-1... therefore Mailman is SP> using multipart/mixed to solve the mixed-encoding problem. That is correct: the list with the problem has italian as a default setting. Now that we have found the problem, is there a solution? :-) -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info From R.Barrett@ftel.co.uk Thu Nov 21 15:53:46 2002 From: R.Barrett@ftel.co.uk (Richard Barrett) Date: Thu, 21 Nov 2002 15:53:46 +0000 Subject: [Mailman-Developers] exit status from Python mail scripts In-Reply-To: <15836.57029.576848.201918@gargle.gargle.HOWL> References: <5.1.1.6.0.20021120203726.03e54788@pop.ftel.co.uk> Message-ID: <5.1.1.6.0.20021121153440.041cb668@pop.ftel.co.uk> At 13:25 21/11/2002, Barry A. Warsaw wrote: > >>>>> "RB" == Richard Barrett writes: > > RB> Is there a particular reason why, on abnormal exit, the exit > RB> status returned by these scripts is not drawn from the values > RB> with defined meanings in /usr/include/sysexits.h ? > >Probably no good one. IOW, its historical. > >Care to provide a patch? >-Barry It happens that I have one I just built, tested and installed on our production MM 2.0.13 installation. I'm just testing the 2.1b5 version of it on my test system so it'll probably be tomorrow before I've finished. The reason I raised it is that, with Sendmail at least, an attempt to deliver to a list alias for a deleted list, where the mail aliases have not been updated, leads to the uninformative message 'unknown mailer error 1' rather than the more accurate/useful 'Unknown user'. There are also some other issues about how one would want the MTA to deal with uncaught exceptions in a MM script causing a delivery failure. In my case I would prefer the MTA to see these as EX_TEMPFAIL (75) so that I have an opportunity to fix the code and then have re-delivery by the local MTA succeed, rather than immediately hard failing the delivery so that it is rejected back to the sender as it is now. Anyway, I'll post the patches tomorrow and you can decide if you want to use them. From che@debian.org Thu Nov 21 17:25:12 2002 From: che@debian.org (Ben Gertzfield) Date: Thu, 21 Nov 2002 09:25:12 -0800 Subject: [Mailman-Developers] 2.1b5 pipermail archives assume all posts are in list language charset? Message-ID: <3DDD16F8.8080201@debian.org> Barry, i18n folks, I installed 2.1b5 to see how the status of pipermail archives and multilanguage posts was coming along. It's starting to look good on the main index page. Here's a test I made with Japanese, Chinese, and German all on the same page (note: I don't know Chinese or German so I just made up something that looked good for the test ;) The list is configured to allow all languages, but is set to us-ascii. http://foxden.org/pipermail/mailman/2002-November/thread.html (Ignore the duplicate Chinese test). The multilingual Subject lines are all converted to Unicode entities perfectly. But if you click on the second post (posted in iso-2022-jp), you can see that the HTML specifies us-ascii as the character set: http://foxden.org/pipermail/mailman/2002-November/000001.html resulting in major mojibake (FYI, Barry, "mojibake" is the Japanese word for "messed up characters", perfectly applicable here since there's no word for that in English). Where is pipermail getting the us-ascii from? I assume it's from the list config being set to English as the default list. But shouldn't it get the charset of the post from the post itself? Interestingly, the Subject on the above url is Unicode escaped, but the title of the page is: [Mailman] =?iso-2022-jp?b?GyRCRnxLXDhsJUYlOSVIGyhC?= Literally, in base64! Barry, you want I should work on this some this week, or do you have time to look at it? Ben From noreply@sourceforge.net Thu Nov 21 17:39:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 21 Nov 2002 09:39:11 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore Message-ID: Bugs item #640775, was opened at 2002-11-19 16:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 Category: command line scripts Group: 2.0.x Status: Open >Resolution: Works For Me Priority: 7 Submitted By: David Weisgerber (davidweisgerber) Assigned to: Nobody/Anonymous (nobody) Summary: Qrunner suddenly doesn't work anymore Initial Comment: Since I checked my e-mail-account today I had over 1000 new mails where my cron daemon worries about those errors with your qrunner and listinfo.py: (1) "Traceback (most recent call last): File "/home/mailman/cron/qrunner", line 84, in ? from Mailman import Utils EOFError: EOF read where object expected" (2) "Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 40, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 36, in ? from Mailman import Utils EOFError: EOF read where object expected" Don't know why, I didn't changed something on the machine and there is noone who could change something. Hard disk space is also okay. So I couldn't figure out where the problem was but I hope you can fix it, the web page shows your 'A bug in mailman' page and this is a cat from /logs/error: "Oct 01 10:10:46 2002 (12542) listinfo: no such list "csi172": Oct 01 10:11:05 2002 (12546) Someone tried to access the admin interface for a non-existent list: csi172 Nov 19 18:10:17 2002 admin(9683): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9683): [----- Mailman Version: 2.0.11 -----] admin(9683): [----- Traceback ------] admin(9683): Traceback (most recent call last): admin(9683): File "/home/mailman/scripts/driver", line 90, in run_main admin(9683): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9683): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9683): from Mailman import Utils admin(9683): EOFError: EOF read where object expected admin(9683): [----- Python Information -----] admin(9683): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9683): sys.executable = /usr/bin/python admin(9683): sys.prefix = /usr admin(9683): sys.exec_prefix= /usr admin(9683): sys.path = /usr admin(9683): sys.platform = linux-i386 admin(9683): [----- Environment Variables -----] admin(9683): PATH_INFO: /kutro admin(9683): PYTHONPATH: /home/mailman admin(9683): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9683): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9683): SERVER_ADMIN: root@localhost admin(9683): SCRIPT_NAME: /mailman/listinfo admin(9683): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9683): REQUEST_METHOD: GET admin(9683): HTTP_HOST: md.2y.net admin(9683): HTTP_KEEP_ALIVE: 300 admin(9683): SERVER_PROTOCOL: HTTP/1.1 admin(9683): QUERY_STRING: admin(9683): REQUEST_URI: /mailman/listinfo/kutro admin(9683): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9683): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9683): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9683): HTTP_CONNECTION: keep-alive admin(9683): SERVER_NAME: md.2y.net admin(9683): REMOTE_ADDR: 192.168.0.2 admin(9683): REMOTE_PORT: 32951 admin(9683): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9683): PATH_TRANSLATED: /home/kutro-homepage admin(9683): SERVER_PORT: 80 admin(9683): GATEWAY_INTERFACE: CGI/1.1 admin(9683): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9683): SERVER_ADDR: 192.168.0.1 admin(9683): DOCUMENT_ROOT: /var/www/html Nov 19 18:10:32 2002 admin(9684): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9684): [----- Mailman Version: 2.0.11 -----] admin(9684): [----- Traceback ------] admin(9684): Traceback (most recent call last): admin(9684): File "/home/mailman/scripts/driver", line 90, in run_main admin(9684): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9684): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9684): from Mailman import Utils admin(9684): EOFError: EOF read where object expected admin(9684): [----- Python Information -----] admin(9684): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9684): sys.executable = /usr/bin/python admin(9684): sys.prefix = /usr admin(9684): sys.exec_prefix= /usr admin(9684): sys.path = /usr admin(9684): sys.platform = linux-i386 admin(9684): [----- Environment Variables -----] admin(9684): PYTHONPATH: /home/mailman admin(9684): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9684): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9684): SERVER_ADMIN: root@localhost admin(9684): SCRIPT_NAME: /mailman/listinfo admin(9684): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9684): REQUEST_METHOD: GET admin(9684): HTTP_HOST: md.2y.net admin(9684): HTTP_KEEP_ALIVE: 300 admin(9684): SERVER_PROTOCOL: HTTP/1.1 admin(9684): QUERY_STRING: admin(9684): REQUEST_URI: /mailman/listinfo admin(9684): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9684): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9684): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9684): HTTP_CONNECTION: keep-alive admin(9684): SERVER_NAME: md.2y.net admin(9684): REMOTE_ADDR: 192.168.0.2 admin(9684): REMOTE_PORT: 32951 admin(9684): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9684): SERVER_PORT: 80 admin(9684): GATEWAY_INTERFACE: CGI/1.1 admin(9684): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9684): SERVER_ADDR: 192.168.0.1 admin(9684): DOCUMENT_ROOT: /var/www/html" PS: The logs say that there were no recent activities on any list. ---------------------------------------------------------------------- >Comment By: David Weisgerber (davidweisgerber) Date: 2002-11-21 17:39 Message: Logged In: YES user_id=477011 This fixed it for me: Delete /Mailman/Utils.pyc ==> Maybe it's just a python error ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 From donn@u.washington.edu Thu Nov 21 17:41:12 2002 From: donn@u.washington.edu (Donn Cave) Date: Thu, 21 Nov 2002 09:41:12 -0800 Subject: [Mailman-Developers] Alternate authentication mechanism (was ... RELEASED Mailman 2.1 beta 5) References: <20021120003710.GA25573@babylon5.babcom.com> <20021121060116.GB461@ostraya.zone12.com> Message-ID: <200211211741.gALHfCVv022812@mailhost1.u.washington.edu> Quoth Terri Oda : | On Wed, Nov 20, 2002 at 03:10:29PM -0500, Stonewall Ballard wrote: ... |> Nobody on any of the lists I run would have a clue on how to use this. | And to contrast, I've not only had people request this sort of thing, or | express surprise that there is no secure way to do passwords, but I've also | gotten mail from one user had some, um, choice words for the list | administrators when she discovered that her password was sent in plaintext. I think at our site, most fall into both categories. They're generally not interested in computing technology of this kind and you can't make them understand something they won't think about. But we've worked hard enough to make them conscious of a password security issue here - I mean, they will sense an incongruity. As do we. Mailman is one of the few, if not the only, application at our site that uses passwords, and we had to make a case for it. Part of the deal is that we avoid password authentication for our own site local users, so they (we hope) will not be tempted to set their Mailman password the same as their site (Kerberos) password. Instead they use their Kerberos password to authenticate to the site web authentication service, whereupon they're authenticated automatically to Mailman (as their Kerberos principal, which I map to mailman ID.) That's our fig leaf. Donn Cave, donn@u.washington.edu From Donal.Hunt2@mail.dcu.ie Thu Nov 21 18:10:13 2002 From: Donal.Hunt2@mail.dcu.ie (Donal Hunt) Date: Thu, 21 Nov 2002 18:10:13 +0000 Subject: [Mailman-Developers] Alternate authentication mechanism (was ... RELEASED Mailman 2.1 beta 5) Message-ID: <3DDD2185.6CE82805@mail.dcu.ie> On Thu, 21 Nov 2002, Marilyn Davis wrote: > > I'd like to see a different mechanism - when you want to change your account > > info, Mailman would email you a URL containing a short-lived session key > > that you could use to get to your account page. No passwords. > > Or, mailman can require a confirmation message, like it does for > subscriptions. > > It would be good if a group could turn on encryption to encrypt the > messages and keep them off the web. I suppose that's a big project. It's actually very easy to do. I created a proof-of-concept earlier this year by encrypting all traffic to/from my mailman lists with IBE (Identity Based Encryption). Worked out pretty well. I think the suggestion about a URL being mailed is far better (again a sniffer could get the url and reset the password before the user), but at least the password isn't readable... Donal DCU From R.Barrett@ftel.co.uk Thu Nov 21 18:23:34 2002 From: R.Barrett@ftel.co.uk (Richard Barrett) Date: Thu, 21 Nov 2002 18:23:34 +0000 Subject: Fwd: [Mailman-Developers] [ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore Message-ID: <5.1.1.6.0.20021121181147.04295ac0@pop.ftel.co.uk> Barry I posted on the subject '[Mailman-Users] Spurious ImportError stopping the qrunner' and you responded on 19 Nov If you recollect I said that the problem was cured by removing a file $prefix /Mailman/Utils.pyc which had automagically appeared out of place. Looks like someone else has found the same cure is necessary, albeit for a different spurious exception Python or Mailman problem or a conspiracy ?? Richard >X-Sieve: cmu-sieve 1.3 >To: noreply@sourceforge.net >From: noreply@sourceforge.net >Date: Thu, 21 Nov 2002 09:39:11 -0800 >Bugs item #640775, was opened at 2002-11-19 16:28 >You can respond by visiting: >https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 > >Category: command line scripts >Group: 2.0.x >Status: Open > >Resolution: Works For Me >Priority: 7 >Submitted By: David Weisgerber (davidweisgerber) >Assigned to: Nobody/Anonymous (nobody) >Summary: Qrunner suddenly doesn't work anymore > >Initial Comment: >Since I checked my e-mail-account today I had over 1000 >new mails where my cron daemon worries about those >errors with your qrunner and listinfo.py: > >(1) "Traceback (most recent call last): > File "/home/mailman/cron/qrunner", line 84, in ? > from Mailman import Utils >EOFError: EOF read where object expected" > >(2) "Traceback (most recent call last): > File "/home/mailman/cron/gate_news", line 40, in ? > from Mailman import MailList > File "/home/mailman/Mailman/MailList.py", line 36, in ? > from Mailman import Utils >EOFError: EOF read where object expected" >---------------------------------------------------------------------- > > >Comment By: David Weisgerber (davidweisgerber) >Date: 2002-11-21 17:39 > >Message: >Logged In: YES >user_id=477011 > >This fixed it for me: >Delete /Mailman/Utils.pyc >==> Maybe it's just a python error From bob@nleaudio.com Thu Nov 21 19:04:35 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Thu, 21 Nov 2002 14:04:35 -0500 Subject: [Mailman-Developers] Alternate authentication mechanism (was ... RELEASED Mailman 2.1 beta 5) References: <3DDD2185.6CE82805@mail.dcu.ie> Message-ID: <3DDD2E43.65DC3370@nleaudio.com> Yes, that's a much better idea.. I've seen mailman trashed in some security circles because of its mailing of passwords monthly, and in plain text. Bob From edlau@ucf.ics.uci.edu Thu Nov 21 20:24:41 2002 From: edlau@ucf.ics.uci.edu (Edmund Lau) Date: Thu, 21 Nov 2002 12:24:41 -0800 (PST) Subject: [Mailman-Developers] Missing Moderation Message Message-ID: Now that "martial law" (aka emergency moderation), is in effect on my lists (thanks Barry for the quick patch last night!), I've noticed a bug or feature. A post to the list in question doesn't seem to go through the routines to notify the sender their post is being held and doesn't notify the moderator that there is a new post pending for approval. So I can understand if this is a bug, but I can easily see why this could be a "feature" -- to prevent the poor moderator from getting overwhelmed. -Ed PS from CVS 11/20 From tkikuchi@is.kochi-u.ac.jp Fri Nov 22 00:35:49 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 22 Nov 2002 09:35:49 +0900 Subject: [Mailman-Developers] 2.1b5 pipermail archives assume all posts are in list language charset? References: <3DDD16F8.8080201@debian.org> Message-ID: <3DDD7BE5.604@is.kochi-u.ac.jp> Ben, > But if you click on the second post (posted in iso-2022-jp), you can see > that the HTML specifies us-ascii as the character set: > > Where is pipermail getting the us-ascii from? I assume it's from the > list config being set to English as the default list. But shouldn't it > get the charset of the post from the post itself? 'Iso-2022-jp' is designated as VERBATIM_ENCODING in Defaults.py, and vervatims are treated differently I suppose. You will need considerable work to display iso-2022 characters in web page which need html escaping. That's why I prefer euc-jp as the standard charcterset for Japanese. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From che@debian.org Fri Nov 22 00:38:02 2002 From: che@debian.org (Ben Gertzfield) Date: Thu, 21 Nov 2002 16:38:02 -0800 Subject: [Mailman-Developers] 2.1b5 pipermail archives assume all posts are in list language charset? In-Reply-To: <3DDD16F8.8080201@debian.org> References: <3DDD16F8.8080201@debian.org> <3DDD7BE5.604@is.kochi-u.ac.jp> Message-ID: <3DDD7C6A.9020100@debian.org> Tokio Kikuchi wrote: > 'Iso-2022-jp' is designated as VERBATIM_ENCODING in Defaults.py, > and vervatims are treated differently I suppose. > > You will need considerable work to display iso-2022 characters > in web page which need html escaping. That's why I prefer euc-jp > as the standard charcterset for Japanese. > I actually have written some Python code to safely escape iso-2022 characters for HTML. Maybe we can use this for Pipermail! Ben From sb.list@sb.org Fri Nov 22 00:44:01 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Thu, 21 Nov 2002 19:44:01 -0500 Subject: [Mailman-Developers] Re: Qrunner suddenly doesn't work anymore In-Reply-To: <5.1.1.6.0.20021121181147.04295ac0@pop.ftel.co.uk> Message-ID: I don't know if this is related to the other messages in this thread, but I'm having this problem since I installed what I cvs up'd on the 19th. Since SourceForge is down right now, I don't recall the cvs incantation to get a fresh copy of Mailman - can anyone tell me? I'm really puzzled because all the qrunners just die (after restarting 10 times), but without any error messages. All the perms check out. - Stoney From sb.list@sb.org Fri Nov 22 01:46:31 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Thu, 21 Nov 2002 20:46:31 -0500 Subject: [Mailman-Developers] Re: Qrunner suddenly doesn't work anymore In-Reply-To: Message-ID: I managed to fix this. Somehow, bin/qrunner got corrupted in my CVS tree, and the update wasn't updating it because CVS thought it was modified. - Stoney On 11/21/02 7:44 PM, "Stonewall Ballard" wrote: > I don't know if this is related to the other messages in this thread, but > I'm having this problem since I installed what I cvs up'd on the 19th. > > Since SourceForge is down right now, I don't recall the cvs incantation to > get a fresh copy of Mailman - can anyone tell me? > > I'm really puzzled because all the qrunners just die (after restarting 10 > times), but without any error messages. All the perms check out. > > - Stoney > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From tkikuchi@is.kochi-u.ac.jp Fri Nov 22 01:56:41 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 22 Nov 2002 10:56:41 +0900 Subject: [Mailman-Developers] 2.1b5 pipermail archives assume all posts are in list language charset? References: <3DDD16F8.8080201@debian.org> <3DDD7BE5.604@is.kochi-u.ac.jp> <3DDD7C6A.9020100@debian.org> Message-ID: <3DDD8ED9.5090705@is.kochi-u.ac.jp> Ben Gertzfield wrote: > > I actually have written some Python code to safely escape iso-2022 > characters for HTML. Maybe we can use this for Pipermail! > Well, I like fix once for all (in Entry.py). ;-) Or, you have to worry about it every time you add new modules. Maybe we shuould use global altcharsets for non japanese mlist. global_altcharsets = { 'iso-2022-jp': 'euc-jp', 'shift_jis': 'euc-jp', ... 'iso-8859-15': 'iso-8859-1', # or reverse? ... } This can be generated from charset list for languages. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From noreply@sourceforge.net Fri Nov 22 06:08:47 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 21 Nov 2002 22:08:47 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-621689 ] Subscribe requests dropped from admin db Message-ID: Bugs item #621689, was opened at 2002-10-10 20:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Subscribe requests dropped from admin db Initial Comment: Occasionally, subscribe requests (via the web page) to a list that requires moderator approval for subscriptions never make it to the admin db for that list. They are listed in the subscribe log file, but never show up on the admin db page. Log file entries look like this: Oct 10 18:43:43 2002 (31168) eventmasters: pending XXXXXX.swfla.rr.com But the admin db page for the list shows no outstanding issues. I have verified that there was an actual subscription request behind this log entry. ---------------------------------------------------------------------- >Comment By: Mark Dadgar (mdadgar) Date: 2002-11-21 22:08 Message: Logged In: YES user_id=598228 Unfortunately, it's still occurring under 2.1b4. I'll check it under 2.1b5 as soon as the patches for htdig integration are released, as I need those to implement. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-22 07:11 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1b4 goes out. I've fixed some related bugs in cvs, so hopefully this will be fixed in the new version. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-10-20 10:14 Message: Logged In: YES user_id=598228 Sorry - I'm running 2.1b3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-20 08:48 Message: Logged In: YES user_id=12800 What version of Mailman are you using. It's import to know the exact version, i.e. 2.1beta3, or if you're running from cvs. A lot of these problems have been fixed in cvs, which will soon be released as 2.1 beta 4. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-10-10 21:29 Message: Logged In: YES user_id=598228 I just verified, by cat'ing pending.pck, that the appropriate changes seem to be in there. But the web interface never picks them up. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103 From R.Barrett@ftel.co.uk Fri Nov 22 09:31:49 2002 From: R.Barrett@ftel.co.uk (Richard Barrett) Date: Fri, 22 Nov 2002 09:31:49 +0000 Subject: Fwd: [Mailman-Developers] [ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore Message-ID: <5.1.1.6.0.20021122092620.00afce70@pop.ftel.co.uk> Barry et al You can ignore what I said below in my posting yesterday evening about the subject bug report; a complete non sequitur. The problem I had was with UserDict.pyc (not Utils.pyc) appearing out of place in $prefix/Mailman/ The bug report suggests corruption of Utils.pyc in its correct place. Richard I had said: Barry I posted on the subject '[Mailman-Users] Spurious ImportError stopping the qrunner' and you responded on 19 Nov If you recollect I said that the problem was cured by removing a file $prefix /Mailman/Utils.pyc which had automagically appeared out of place. Looks like someone else has found the same cure is necessary, albeit for a different spurious exception Python or Mailman problem or a conspiracy ?? Richard >X-Sieve: cmu-sieve 1.3 >To: noreply@sourceforge.net >From: noreply@sourceforge.net >Date: Thu, 21 Nov 2002 09:39:11 -0800 >Bugs item #640775, was opened at 2002-11-19 16:28 >You can respond by visiting: >https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 > >Category: command line scripts >Group: 2.0.x >Status: Open > >Resolution: Works For Me >Priority: 7 >Submitted By: David Weisgerber (davidweisgerber) >Assigned to: Nobody/Anonymous (nobody) >Summary: Qrunner suddenly doesn't work anymore > >Initial Comment: >Since I checked my e-mail-account today I had over 1000 >new mails where my cron daemon worries about those >errors with your qrunner and listinfo.py: > >(1) "Traceback (most recent call last): > File "/home/mailman/cron/qrunner", line 84, in ? > from Mailman import Utils >EOFError: EOF read where object expected" > >(2) "Traceback (most recent call last): > File "/home/mailman/cron/gate_news", line 40, in ? > from Mailman import MailList > File "/home/mailman/Mailman/MailList.py", line 36, in ? > from Mailman import Utils >EOFError: EOF read where object expected" >---------------------------------------------------------------------- > > >Comment By: David Weisgerber (davidweisgerber) >Date: 2002-11-21 17:39 > >Message: >Logged In: YES >user_id=477011 > >This fixed it for me: >Delete /Mailman/Utils.pyc >==> Maybe it's just a python error From noreply@sourceforge.net Fri Nov 22 16:55:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 22 Nov 2002 08:55:41 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642392 ] 2.1b5 - Posters getting duplicate msgs Message-ID: Bugs item #642392, was opened at 2002-11-22 07:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b5 - Posters getting duplicate msgs Initial Comment: obscure_addresses does not work. Posters e-mail addresses appear in archives even with obscure_addresses set ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 From noreply@sourceforge.net Fri Nov 22 17:36:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 22 Nov 2002 09:36:43 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-642417 ] Add X-Listmember header Message-ID: Feature Requests item #642417, was opened at 2002-11-22 08:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=642417&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Add X-Listmember header Initial Comment: Currently there is no way to determine who list messages were originally sent to. Adding the list members subscribed e-mail address would allow us to track messages that get forwarded, members subscribed multiple times with different addresses, etc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=642417&group_id=103 From wheakory@isu.edu Fri Nov 22 18:43:13 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Fri, 22 Nov 2002 11:43:13 -0700 Subject: [Mailman-Developers] Subscrib user through email client withou notification Message-ID: <3DDE7AC1.901D6740@isu.edu> How can I subscribe an user to a mailman list through an email client, (using the listname-request commands), without them being notified and having to confirm the subscription? I know you can do this through the command line, but I want to be able to do it through a webmail client. Here is the command I used below. subscribe password address=email@yahoo.com -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From danny@terweij.nl Fri Nov 22 23:45:38 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 23 Nov 2002 00:45:38 +0100 Subject: [Mailman-Developers] make install error (21b5+) Message-ID: <09f901c29281$58d55e50$1e00a8c0@onsnet.org> Hi, I created a vmware linux setup (rh8) and want to try some things out. I installed this rh8 with minimum packages and no GUI. Just a few minutes ago i retreived a fresh CVS. Created user mailman. Did the staps from INSTALL ./configure --with-python=/usr/bin/python2 --with-mail-gid=12 --with-cgi-gid =apache su - mailman make install and got finaly : Compiling /usr/local/mailman/Mailman/i18n.py ... Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 44, in ? import paths File "bin/paths.py", line 59, in ? import korean ImportError: No module named korean make: *** [update] Error 1 So i think something is not good at the CVS. Until it does not install , my rh7.2 machine will be running the (buggy) b4+ version :( Whats wrong and fix it :) Danny Terweij Dutch Translator From dax@gurulabs.com Sat Nov 23 04:12:38 2002 From: dax@gurulabs.com (Dax Kelson) Date: Sat, 23 Nov 2002 04:12:38 -0000 Subject: [Mailman-Developers] SOLVED: Postfix+Mailman alias-free and in separate namespace Message-ID: <1032247796.1341.15.camel@mentor> I've created the script postfix-to-mailman.py. Python seemed natural, as mailman is written in python, and invoking postfix-to-mailman.py script on delivery to mailman just warms up the disk cache with all the python code and speeds invocation of mailman. Postfix configuration samples (thanks Wietse) can be found inside the script itself. The script is heavily based on the qmail-to-postfix script by Bruce Perens. You can get the script at: http://www.gurulabs.com/downloads.html Dax Kelson Guru Labs - To unsubscribe, send mail to majordomo@postfix.org with content (not subject): unsubscribe postfix-users From fil@rezo.net Sat Nov 23 07:44:36 2002 From: fil@rezo.net (Fil) Date: Sat, 23 Nov 2002 08:44:36 +0100 Subject: [Mailman-Developers] SOLVED: Postfix+Mailman alias-free and in separate namespace In-Reply-To: <1032247796.1341.15.camel@mentor> References: <1032247796.1341.15.camel@mentor> Message-ID: <20021123074436.GC1017@rezo.net> Hi Dax, I've been doing something similar for a while, but without a script, just by using postfix's virtual and regexp tools. - http://listes.rezo.net/how.php This approach first checks if the address is a "hard" one (ie mentioned in the virtual for rezo.net), then , if not, sends it to a regexp domain where everything is sent to Mailman, either to a -bounce, -on, -off (and so on) script, or else to the 'post' script. @ Dax Kelson : > I've created the script postfix-to-mailman.py. Python seemed natural, as > mailman is written in python, and invoking postfix-to-mailman.py script > on delivery to mailman just warms up the disk cache with all the python > code and speeds invocation of mailman. > > Postfix configuration samples (thanks Wietse) can be found inside the > script itself. The script is heavily based on the qmail-to-postfix > script by Bruce Perens. > > You can get the script at: > > http://www.gurulabs.com/downloads.html > > Dax Kelson > Guru Labs -- Fil From tkikuchi@is.kochi-u.ac.jp Sat Nov 23 10:10:41 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sat, 23 Nov 2002 19:10:41 +0900 Subject: [Mailman-Developers] Digest Subject Message-ID: <3DDF5421.8000904@is.kochi-u.ac.jp> I am not very sure but looks like subject header of digest is not mime encoded. Here is a patch. --- /home/mailman/src/mailman/Mailman/Handlers/ToDigest.py Sat Oct 19 08:25:57 2002 +++ ToDigest.py Sat Nov 23 19:02:39 2002 @@ -37,6 +37,7 @@ from email.MIMEText import MIMEText from email.MIMEMessage import MIMEMessage from email.Utils import getaddresses +from email.Header import Header from Mailman import mm_cfg from Mailman import Utils @@ -139,20 +140,22 @@ volume = mlist.volume issue = mlist.next_digest_number digestid = _('%(realname)s Digest, Vol %(volume)d, Issue %(issue)d') + charset = Utils.GetCharSet(lang) + digestid_h = Header(digestid, charset) # Set things up for the MIME digest. Only headers not added by # CookHeaders need be added here. mimemsg = Message.Message() mimemsg['Content-Type'] = 'multipart/mixed' mimemsg['MIME-Version'] = '1.0' mimemsg['From'] = mlist.GetRequestEmail() - mimemsg['Subject'] = digestid + mimemsg['Subject'] = digestid_h mimemsg['To'] = mlist.GetListEmail() mimemsg['Reply-To'] = mlist.GetListEmail() # Set things up for the rfc1153 digest plainmsg = StringIO() rfc1153msg = Message.Message() rfc1153msg['From'] = mlist.GetRequestEmail() - rfc1153msg['Subject'] = digestid + rfc1153msg['Subject'] = digestid_h rfc1153msg['To'] = mlist.GetListEmail() rfc1153msg['Reply-To'] = mlist.GetListEmail() separator70 = '-' * 70 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From tneff@bigfoot.com Sat Nov 23 16:37:20 2002 From: tneff@bigfoot.com (Tom Neff) Date: Sat, 23 Nov 2002 11:37:20 -0500 Subject: [Mailman-Developers] Minor templates error In-Reply-To: References: Message-ID: <171553921.1038051440@[192.168.254.37]> This is hardly worth filing a bug or patch, I just noticed that in templates/en/verify.txt under the latest 2.1, it says: If you do not wish to be subscribed from this list, please simply... "Subscribed from" is ungrammatical, probably this text was boilerplated from something that said "removed" or "unsubscribed from". The line should read If you do not wish to be subscribed TO this list, please simply... (emphasis added) Thanks for a great product! From noreply@sourceforge.net Sun Nov 24 07:42:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 23 Nov 2002 23:42:42 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg. Message-ID: Bugs item #642996, was opened at 2002-11-24 16:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: can't send Plain Digest w/multipart msg. Initial Comment: cron/senddigests and cgi-bin/admin/digest can't send plain digest when multipart message(s) are contained. Note: Attached file will solve this problem for only cron/senddigests, but not for cgi. Traceback: admin(17454): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(17454): [----- Mailman Version: 2.1b5 -----] admin(17454): [----- Traceback ------] admin(17454): Traceback (most recent call last): admin(17454): File "/usr/local/mail/mailman/scripts/driver", line 87, in run_main admin(17454): main() admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 169, in main admin(17454): change_options(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 1229, in change_options admin(17454): gui.handleForm(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line 169, in handleForm admin(17454): self._setValue(mlist, property, val, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/Digest.py", line 148, in _setValue admin(17454): status = mlist.send_digest_now() admin(17454): File "/usr/local/mail/mailman/Mailman/Digester.py", line 60, in send_digest_now admin(17454): ToDigest.send_digests(self, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests admin(17454): send_i18n_digests(mlist, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 301, in send_i18n_digests admin(17454): g(msg, unixfrom=0) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 100, in flatten admin(17454): self._write(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 128, in _write admin(17454): self._dispatch(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 154, in _dispatch admin(17454): meth(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 212, in _handle_text admin(17454): raise TypeError, 'string payload expected: %s' % type(payload) admin(17454): TypeError: string payload expected: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103 From noreply@sourceforge.net Sun Nov 24 10:21:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 02:21:24 -0800 Subject: [Mailman-Developers] [ mailman-Patches-643011 ] bug: Scrubbed messages are re-decoded Message-ID: Patches item #643011, was opened at 2002-11-24 19:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: bug: Scrubbed messages are re-decoded Initial Comment: Content-Transfer-Encoding must be cleared. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 From noreply@sourceforge.net Sun Nov 24 20:57:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 12:57:08 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643231 ] Last archived date is incorrect Message-ID: Bugs item #643231, was opened at 2002-11-24 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Last archived date is incorrect Initial Comment: The last archived date/time is incorrect. Time appears to be GMT, not local time (e.g. ahead 5 hrs for sites in EST) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_id=103 From noreply@sourceforge.net Sun Nov 24 21:09:10 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 13:09:10 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643233 ] E-mail addresses not being obscured Message-ID: Bugs item #643233, was opened at 2002-11-24 12:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: E-mail addresses not being obscured Initial Comment: In 2.1b5, the archives contain the posters e-mail address even if the option to obscure the posters identity has been selected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103 From noreply@sourceforge.net Sun Nov 24 21:10:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 13:10:21 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642392 ] 2.1b5 - Posters getting duplicate msgs Message-ID: Bugs item #642392, was opened at 2002-11-22 07:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b5 - Posters getting duplicate msgs Initial Comment: obscure_addresses does not work. Posters e-mail addresses appear in archives even with obscure_addresses set ---------------------------------------------------------------------- >Comment By: Terry Grace (tgrace) Date: 2002-11-24 12:10 Message: Logged In: YES user_id=87771 Please ignore. Had two instances of the daemons running. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 From noreply@sourceforge.net Sun Nov 24 21:11:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 13:11:27 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642392 ] 2.1b5 - Posters getting duplicate msgs Message-ID: Bugs item #642392, was opened at 2002-11-22 07:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Deleted Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b5 - Posters getting duplicate msgs Initial Comment: obscure_addresses does not work. Posters e-mail addresses appear in archives even with obscure_addresses set ---------------------------------------------------------------------- Comment By: Terry Grace (tgrace) Date: 2002-11-24 12:10 Message: Logged In: YES user_id=87771 Please ignore. Had two instances of the daemons running. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 From noreply@sourceforge.net Sun Nov 24 21:13:39 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 13:13:39 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642392 ] 2.1b5 - Posters getting duplicate msgs Message-ID: Bugs item #642392, was opened at 2002-11-22 07:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 Category: mail delivery Group: 2.1 beta Status: Deleted Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b5 - Posters getting duplicate msgs Initial Comment: obscure_addresses does not work. Posters e-mail addresses appear in archives even with obscure_addresses set ---------------------------------------------------------------------- Comment By: Terry Grace (tgrace) Date: 2002-11-24 12:10 Message: Logged In: YES user_id=87771 Please ignore. Had two instances of the daemons running. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 From noreply@sourceforge.net Sun Nov 24 21:14:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 24 Nov 2002 13:14:12 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642392 ] 2.1b5 - Posters getting duplicate msgs Message-ID: Bugs item #642392, was opened at 2002-11-22 07:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 Category: mail delivery Group: 2.1 beta Status: Deleted Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b5 - Posters getting duplicate msgs Initial Comment: obscure_addresses does not work. Posters e-mail addresses appear in archives even with obscure_addresses set ---------------------------------------------------------------------- Comment By: Terry Grace (tgrace) Date: 2002-11-24 12:10 Message: Logged In: YES user_id=87771 Please ignore. Had two instances of the daemons running. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642392&group_id=103 From jwblist@olympus.net Mon Nov 25 05:48:55 2002 From: jwblist@olympus.net (John W Baxter) Date: Sun, 24 Nov 2002 21:48:55 -0800 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: <200211200102.55148.philb@philb.us> References: <200211200102.55148.philb@philb.us> Message-ID: At 1:02 -0500 11/20/2002, Phil Barnett wrote: >Sending passwords as plaintext in 2002 is downright negligent considering the >current state of sniffing, monitoring and penetration. So...we stop calling them passwords. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From noreply@sourceforge.net Mon Nov 25 13:37:39 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 25 Nov 2002 05:37:39 -0800 Subject: [Mailman-Developers] [ mailman-Patches-643547 ] Update portuguese translation Message-ID: Patches item #643547, was opened at 2002-11-25 11:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643547&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Update portuguese translation Initial Comment: I've done a quick lookover the portuguese translation and I have a number of small fixes and unfuzzys to be added. This fixes mostly the listinfo page, which is the page my users actually hit the most, and there are some other assorted fixes (typos non-existant words etc). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643547&group_id=103 From noreply@sourceforge.net Mon Nov 25 13:43:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 25 Nov 2002 05:43:23 -0800 Subject: [Mailman-Developers] [ mailman-Patches-643556 ] Update to portuguese listinfo template Message-ID: Patches item #643556, was opened at 2002-11-25 11:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643556&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Update to portuguese listinfo template Initial Comment: This is the second half of the quick fixups I've done to the pt_BR translation. I've only hacked the listinfo template so far because it's the only thing that's been really bothering me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643556&group_id=103 From bryanf@samurai.com Mon Nov 25 14:42:28 2002 From: bryanf@samurai.com (Bryan Fullerton) Date: Mon, 25 Nov 2002 09:42:28 -0500 Subject: [Mailman-Developers] Re: [Mailman-Announce] RELEASED Mailman 2.1 beta5 In-Reply-To: Message-ID: <1E9D8028-0084-11D7-ADA9-000393013B04@samurai.com> On Monday, November 25, 2002, at 12:48 AM, John W Baxter wrote: > At 1:02 -0500 11/20/2002, Phil Barnett wrote: >> Sending passwords as plaintext in 2002 is downright negligent >> considering the >> current state of sniffing, monitoring and penetration. > > So...we stop calling them passwords. I'm on so many Mailman lists that I can never remember which ones I've chosen passwords for and which I've let the software choose, so whenever I want to change any settings on a list I always mail myself the password. I'd be happy with randomly generated one-time time-limited (hours? days?) tokens - perhaps somewhat longer Base64 or MD5 hashes - and have the software mail out a URL. I like the idea of sending a URL - users are frequently confused about what they should be doing with the password, if they can just click they'd be happier. To continue supporting email commands, perhaps have a system of requesting a time-limited token by return email. Bryan (finally read the backlog of 800 messages I had on this list - yay!) From noreply@sourceforge.net Mon Nov 25 15:55:59 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 25 Nov 2002 07:55:59 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643605 ] RFC2882 and / in subscriber address Message-ID: Bugs item #643605, was opened at 2002-11-25 09:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: RFC2882 and / in subscriber address Initial Comment: Reproduced from the mailman-users list. Thanks to Bill for the followup. --chris [][][][][][] Majordomo would tell you the same thing but I agree that it is a legal address (we use similar addresses internally at work) and should be accepted. RFC2822 (http://www.faqs.org/rfcs/rfc2822.html) clearly allows it in the local-part (Section 3.4.1) as a dot-atom. This should be fixed but in the mean time I don't think you are going to get it into mailman. Bill W. At 09:31 AM 11/25/2002 -0600, Christopher Kolar wrote: Hello. I am trying to add a person to a mail list and having some problems. Their organization runs some sort of bestial mail system where the addresses are of the form: schmoe.j/bhs@dns.u99.k12.il.us When I try to drop the address in through the mass subscribe screen I get the following message from Mailman: * Joe Schmoe -- Hostile address (illegal characters) My guess is that the / is getting parsed by Mm as an attempt to reference a file (a la majordomo). Is there a way to force the address onto the subscriber list? It is an actual valid address for delivery. Thanks in advance, --chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103 From noreply@sourceforge.net Mon Nov 25 20:56:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 25 Nov 2002 12:56:09 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro Message-ID: Bugs item #643762, was opened at 2002-11-25 21:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 From noreply@sourceforge.net Mon Nov 25 20:58:15 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 25 Nov 2002 12:58:15 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro Message-ID: Bugs item #643762, was opened at 2002-11-25 21:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None >Priority: 6 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2002-11-25 21:58 Message: Logged In: YES user_id=60479 Uops, I forgot to say that archiving is broken. I do not know if this related to the reported error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 From noreply@sourceforge.net Mon Nov 25 21:15:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 25 Nov 2002 13:15:26 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro Message-ID: Bugs item #643762, was opened at 2002-11-25 21:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 6 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2002-11-25 22:15 Message: Logged In: YES user_id=60479 Argh, please forget the comment about archiving... ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2002-11-25 21:58 Message: Logged In: YES user_id=60479 Uops, I forgot to say that archiving is broken. I do not know if this related to the reported error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 From gward@mems-exchange.org Tue Nov 26 03:04:00 2002 From: gward@mems-exchange.org (Greg Ward) Date: Mon, 25 Nov 2002 22:04:00 -0500 Subject: [Mailman-Developers] How to lose friends and alienate people Message-ID: <20021126030400.GA4700@cthulhu.gerg.ca> After upgrading our only large, busy, high-profile list to MM 2.1 a few days ago, we've already got our first customer feedback: """ You've got some nerve quarantining my messages when all I've ever done on your forum is attempt to provide specific help to people who have requested it. Don't worry about my participation in the future. """ Ouch. This, of course, is in response to the standard response to posts to a moderated list: """ The reason it is being held: Posts by member are currently quarantined for moderation """ Ironically, I did notice the change when I was installing MM 2.1, decided I did not like it, but did not do anything about it. I have now, with a simple-stupid patch to Mailman/Handlers/Moderate.py: --- Mailman/Handlers/Moderate.py.orig Mon Oct 28 10:24:28 2002 +++ Mailman/Handlers/Moderate.py Mon Nov 25 22:03:29 2002 @@ -34,3 +34,3 @@ class ModeratedMemberPost(Hold.ModeratedPost): - reason = _('Posts by member are currently quarantined for moderation') + reason = _('Post to moderated list') This will at least keep the wolves, err users, at bay for a while. May I suggest the following: * on a traditional moderated list, where all users are moderated, telling individuals that *their* post is quarantined is likely to cause confusion at best, offense at worst (see above) * on a list with mixed moderation, you might not want to reveal to users who are moderated that there is something "special" about them ...both of which argue for making my little patch permanent. Greg -- Greg Ward - software developer gward@mems-exchange.org MEMS Exchange http://www.mems-exchange.org From noreply@sourceforge.net Tue Nov 26 09:57:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 26 Nov 2002 01:57:21 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644005 ] sync_members: problems with u umlaut Message-ID: Bugs item #644005, was opened at 2002-11-26 09:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members: problems with u umlaut Initial Comment: Running sync_members -n, I get this error, when a member with an umlaut-u in it's real name gets removed. Traceback (most recent call last): File "/usr/sbin/sync_members", line 283, in ? main() File "/usr/sbin/sync_members", line 275, in main print _('Removed: <%(addr)30s> %(name)s') UnicodeError: ASCII encoding error: ordinal not in range(128) Changing the ü in the web-frontend to ue, and then running again sync_members "fixes" the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_id=103 From sb.list@sb.org Tue Nov 26 13:28:30 2002 From: sb.list@sb.org (Stonewall Ballard) Date: Tue, 26 Nov 2002 08:28:30 -0500 Subject: [Mailman-Developers] How to lose friends and alienate people In-Reply-To: <20021126030400.GA4700@cthulhu.gerg.ca> Message-ID: I strongly endorse this change. While I have not had any negative feedback, the current wording seems rather harsh. - Stoney On 11/25/02 10:04 PM, "Greg Ward" wrote: >... > May I suggest the following: > > * on a traditional moderated list, where all users are moderated, > telling individuals that *their* post is quarantined is likely > to cause confusion at best, offense at worst (see above) > > * on a list with mixed moderation, you might not want to reveal > to users who are moderated that there is something "special" > about them > > ...both of which argue for making my little patch permanent. > > Greg From noreply@sourceforge.net Tue Nov 26 14:44:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 26 Nov 2002 06:44:34 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message header/body Message-ID: Patches item #644129, was opened at 2002-11-26 14:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Edit held message header/body Initial Comment: Here is my preliminary (brute force) patch to allow full editing of headers and bodies of messages being held for approval in Mailman 2.1 (as of beta 5). I have released versions of this for 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before releasing this one. You must set HOLD_MESSAGES_AS_PICKLES = 0 in your installation's mm_cfg.py for this to work. I may support pickles in a future version. Personally I don't see that much performance difference anyway, not on the held stuff... Also note that if you had HOLD_MESSAGES_AS_PICKLES = 1 (the default) when you created a list, you must recreate it after changing that variable. (Learned the hard way) This patch overrides the ADMINDB_PAGE_TEXT_LIMIT setting, so if you have megabyte messages being held, be ready to wait. Also - this version doesn't change the request database, so if you change the Subject: header you won't see the change reflected in the summary list (but it will be sent out your way when you Approve). Happy mailmanning! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 From Jost.Krieger+mailman@rub.de Tue Nov 26 16:24:57 2002 From: Jost.Krieger+mailman@rub.de (Jost Krieger) Date: Tue, 26 Nov 2002 17:24:57 +0100 Subject: [Mailman-Developers] 2.1b5: Decoration doesn't work that well for German lists Message-ID: <20021126162457.GS8418@ruhr-uni-bochum.de> The current MIME decoration logic is as follows: If the list language charset is ASCII or the same as the message charset, just put on header and footer, else put on extra parts in some way. Unfortunately, for "almost ASCII" languages like German, this leads to quite a few messages arriving with 2 or 3 text/plain; charset="us-ascii" parts. This always happens when header and footer are just in ASCII, although the list language is not. Someone along the way detects this and follows the RFC in making the parts ASCII, but Decorate.py doen't know about it. I can think of two solutions: 1. Have Decorate.py analyse header and footer for 8bit characters. 2. If the message charset is "below" the list charset, i.e., ASCII, upgrade the message charset and concatenate the parts. If this works as I think it works, it will be corrected back to US-ASCII later on if there were no 8bit characters after all. Jost -- | Jost.Krieger+sig@ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine am RZ der RUB | | Pluralitas non est ponenda sine necessitate | | William of Ockham (1285-1347/49) | From noreply@sourceforge.net Tue Nov 26 19:23:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 26 Nov 2002 11:23:00 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644294 ] Uncaught runner exception Message-ID: Bugs item #644294, was opened at 2002-11-26 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: Getting these repeatedly: Nov 26 14:17:11 2002 (327) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 26 14:17:11 2002 (327) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/opt/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103 From noreply@sourceforge.net Wed Nov 27 01:40:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 26 Nov 2002 17:40:41 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644294 ] Uncaught runner exception Message-ID: Bugs item #644294, was opened at 2002-11-26 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: Getting these repeatedly: Nov 26 14:17:11 2002 (327) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 26 14:17:11 2002 (327) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/opt/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Terry Grace (tgrace) Date: 2002-11-26 16:40 Message: Logged In: YES user_id=87771 Archives broken too. After restarting the deamons, only the first article posted gets archived. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103 From Dale@Newfield.org Wed Nov 27 06:46:07 2002 From: Dale@Newfield.org (Dale Newfield) Date: Wed, 27 Nov 2002 01:46:07 -0500 (EST) Subject: [Mailman-Developers] One last bug before I leave for Tday Message-ID: Current CVS. When approving a message with the "Preserve" box checked, I got the following error. It worked fine w/o checking that box. BTW, this is working really well, and the VERP-like bounce processing is excellent! It's possible I caused this--I had this list created before 2.1 that got upgraded while SAVE_AS_PICKLES was 1, and I since changed it in mm_cfg.py to 0. I thought I saw that a qrunner restart was all that was required--is there something hidden inside the MailList object that stores this bit and needs to be reset to prevent this breakage? -Dale -------------- next part -------------- Bug in Mailman version 2.1b5+ 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 "/Users/mailman/scripts/driver", line 87, in run_main main() File "/Users/mailman/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/Users/mailman/Mailman/Cgi/admindb.py", line 736, in process_form preserve, forward, forwardaddr) File "/Users/mailman/Mailman/ListAdmin.py", line 178, in HandleRequest forward, addr) File "/Users/mailman/Mailman/ListAdmin.py", line 256, in __handlepost msg = cPickle.load(fp) ValueError: could not convert string to float ------------------------------------------------------------------------ Python information: Variable Value sys.version 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform darwin ------------------------------------------------------------------------ Environment variables: Variable Value HTTP_UA_OS MacOS HTTP_ACCEPT */* HTTP_PRAGMA no-cache CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.spiralentertainment.com/admindb/spiral-announce?msgid=20 SERVER_SOFTWARE Apache/1.3.27 (Darwin) PYTHONPATH /Users/mailman SCRIPT_FILENAME /Users/mailman/cgi-bin/admindb SERVER_ADMIN [no address given] SCRIPT_NAME /admindb QUERY_STRING SERVER_SIGNATURE Apache/1.3.27 Server at mail.spiralentertainment.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.spiralentertainment.com PATH_INFO /spiral-announce SERVER_PROTOCOL HTTP/1.1 HTTP_EXTENSION Security/Remote-Passphrase HTTP_UA_CPU PPC REQUEST_URI /admindb/spiral-announce CONTENT_LENGTH 23237 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.22; Mac_PowerPC) HTTP_CONNECTION Keep-Alive HTTP_COOKIE spiral-announce+admin=2802000000691855e43d732800000036653935393031326632623035663266366537663237376166653534656263303962333866613666 SERVER_NAME mail.spiralentertainment.com REMOTE_ADDR 64.192.58.25 REMOTE_PORT 49682 HTTP_ACCEPT_LANGUAGE en __CF_USER_TEXT_ENCODING 0x46:0:0 PATH_TRANSLATED /Users/mailman/cgi-bin/spiral-announce SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 REMOTE_HOST dsl-64-192-58-25.telocity.com SERVER_ADDR 64.192.58.25 DOCUMENT_ROOT /Library/WebServer/Documents/Newfield.org From noreply@sourceforge.net Wed Nov 27 10:24:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 02:24:19 -0800 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd patch -p1 < ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:24 Message: Logged In: YES user_id=75166 htdig-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 11:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 16:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 14:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 11:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 16:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 15:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply@sourceforge.net Wed Nov 27 10:22:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 02:22:33 -0800 Subject: [Mailman-Developers] [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From Jost.Krieger+mailman@rub.de Wed Nov 27 13:15:01 2002 From: Jost.Krieger+mailman@rub.de (Jost Krieger) Date: Wed, 27 Nov 2002 14:15:01 +0100 Subject: [Mailman-Developers] Slightly lame logging: web subscription request In-Reply-To: <15805.25296.355815.747438@gargle.gargle.HOWL> References: <20021028161244.GA30884@cthulhu.gerg.ca> <15805.25296.355815.747438@gargle.gargle.HOWL> Message-ID: <20021127131501.GE8418@ruhr-uni-bochum.de> On Mon, Oct 28, 2002 at 11:16:16AM -0500, Barry A. Warsaw wrote: > > >>>>> "GW" == Greg Ward writes: > > GW> It appears that MM 2.1b4's logging of web subscription > GW> requests is a bit lame -- it doesn't actually log the email > GW> address involved, just the real name. Is this deliberate? > > No. I'll have to double check this when I get a chance. As this ist still in 2.1b5, I had a look. The following patch fixed it for me, but I don't understand the case I didn't fix (umbrella lists?). Jost --- /usr/local/mailman/Mailman/MailList.py.ORIG Wed Nov 27 12:01:18 2002 +++ /usr/local/mailman/Mailman/MailList.py Wed Nov 27 12:01:44 2002 @@ -821,7 +821,7 @@ if recipient <> email: who = "%s (%s)" % (email, recipient.split('@')[0]) else: - who = name + who = "%s (%s)" % (email, name) syslog('subscribe', '%s: pending %s %s', self.internal_name(), who, by) raise Errors.MMSubscribeNeedsConfirmation -- | Jost.Krieger+sig@ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine am RZ der RUB | | Pluralitas non est ponenda sine necessitate | | William of Ockham (1285-1347/49) | From anser@pobox.com Tue Nov 26 14:55:17 2002 From: anser@pobox.com (anser@pobox.com) Date: Tue, 26 Nov 2002 09:55:17 -0500 Subject: [Mailman-Developers] I finally released an editing header/body patch for MM 2.1 In-Reply-To: References: Message-ID: <424639671.1038304517@[192.168.254.37]> A lot of people were asking me for a 2.1 version of my "edit held message headers/bodies" patch, but I held off because I wasn't sure if 2.1 was gonna change under me and make me repeat the work. It seems pretty stable, now so here we go. This is the quick and dirty version, no frills, but it works for me. I like a lot of the new functionality in MM2.1, and now I can actually use it to run clean lists. Let me know if you encounter any problems. https://sourceforge.net/tracker/index.php?func=detail&aid=644129&group_id=1 03&atid=300103 From lists@konfido.de Wed Nov 27 00:51:28 2002 From: lists@konfido.de (Matthias Juchem) Date: Wed, 27 Nov 2002 01:51:28 +0100 Subject: [Mailman-Developers] [PATCH] Clean all Makefiles on make distclean Message-ID: Hi. Here is a patch for Mailman CVS head. mailman/messages/Makefile and mailman/tests/*/Makefile do not get cleaned up when doing a 'make distclean'. This should patch fix it. Tested like this: 'configure --some-options; make distclean'; seems to work Regards, Matthias diff -urN mailman/messages/Makefile.in mailman-matthias/messages/Makefile.in --- mailman/messages/Makefile.in Mon Nov 4 23:47:30 2002 +++ mailman-matthias/messages/Makefile.in Wed Nov 27 01:38:29 2002 @@ -115,6 +115,7 @@ -rm -f marked.files docstring.files distclean: clean + -rm -f Makefile catclean: -rm -f Makefile */LC_MESSAGES/mailman.mo */LC_MESSAGES/mailman.po.old $(POTFILE) diff -urN mailman/tests/Makefile.in mailman-matthias/tests/Makefile.in --- mailman/tests/Makefile.in Mon Oct 1 18:39:12 2001 +++ mailman-matthias/tests/Makefile.in Wed Nov 27 01:40:37 2002 @@ -71,5 +71,9 @@ clean: distclean: + @for d in $(SUBDIRS); \ + do \ + (cd $$d; $(MAKE) distclean); \ + done -rm *.pyc -rm Makefile From lists@konfido.de Wed Nov 27 01:00:17 2002 From: lists@konfido.de (Matthias Juchem) Date: Wed, 27 Nov 2002 02:00:17 +0100 Subject: [Mailman-Developers] [PATCH] Do not use hardcoded $prefix in contrib/qmail-to-mailman.py Message-ID: Hi. The intention of this patch should be clear. Diff against CVS head. Tested, works for me. Regards, Matthias diff -urN mailman/contrib/qmail-to-mailman.py mailman-matthias/contrib/qmail-to-mailman.py --- mailman/contrib/qmail-to-mailman.py Sat Apr 6 00:49:32 2002 +++ mailman-matthias/contrib/qmail-to-mailman.py Wed Nov 27 01:34:35 2002 @@ -1,7 +1,7 @@ #! @PYTHON@ # Configuration variables - Change these for your site if necessary. -MailmanHome = "/usr/local/mailman"; # Mailman home directory. +MailmanHome = "@prefix@"; # Mailman home directory. MailmanOwner = "postmaster@localhost"; # Postmaster and abuse mail recepient. # End of configuration variables. @@ -32,7 +32,7 @@ # To configure a virtual domain to connect to mailman, create these files: # # ~mailman/.qmail-default -# |preline /usr/bin/python /usr/local/mailman/mail-in.py +# |preline /usr/bin/python @prefix@/mail-in.py # # /var/qmail/control/virtualdomains: # DOMAIN.COM:mailman From pieterb@gewis.nl Mon Nov 25 19:13:23 2002 From: pieterb@gewis.nl (PieterB) Date: Mon, 25 Nov 2002 20:13:23 +0100 (CET) Subject: [Mailman-Developers] UTF8 problem with Microsoft Exchange and Mailman 2.1b4 Message-ID: <20021125191323.53A5921124@gewis.win.tue.nl> Hi, I have a problem with UTF8-encoded e-mails from a Microsoft Exchange 2000 server which are sent to a Mailman 2.1b4 mailinglist server. Exchange uses "utf8" characterset, so that the users will get an extra "attachement" with every mailinglist message (charset "utf-8" is used for the body, and charset "us-ascii" is used for the signature of the mailinglist). An example of the headers and body is included, below. Is there a way to change the filtering in Mailman, so that these messages are converted to a more common charset, such as: us-ascii or iso-8859-1 For more information see: http://www.microsoft.com/exchange/techinfo/tips/Mail_utf8.asp (Mailbox Tip: Allow Non-UTF-8 Mail Clients To View Messages Sent from Exchange). I tried to get the Exchange server changed, but didn't get any response of the local administrator. ;( Regards, Pieter 8<-------------------------------------------- X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C29496.DF565EF8" Date: Mon, 25 Nov 2002 16:25:23 +0100 X-MS-TNEF-Correlator: Thread-Topic: foo.bar Thread-Index: AcKUlojItUqNGxBLS1mNvYY31kEXygAACufy X-Content-Filtered-By: Mailman/MimeDel 2.1b4 X-Mailman-Version: 2.1b4 This is a multi-part message in MIME format. ------_=_NextPart_001_01C29496.DF565EF8 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 [base64 attachement removed] ------_=_NextPart_001_01C29496.DF565EF8 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit -- footer of the mailinglist ------_=_NextPart_001_01C29496.DF565EF8-- From sagi@boom.org.il Wed Nov 20 09:32:13 2002 From: sagi@boom.org.il (Sagi Bashari) Date: Wed, 20 Nov 2002 11:32:13 +0200 Subject: [Mailman-Developers] [Fwd: automating daily send to moderated list] Message-ID: <3DDB569D.5020604@boom.org.il> No answer on users list, forwarding to developers. -------------- next part -------------- An embedded message was scrubbed... From: Sagi Bashari Subject: automating daily send to moderated list Date: Tue, 19 Nov 2002 13:44:13 +0200 Size: 803 Url: http://mail.python.org/pipermail/mailman-developers/attachments/20021120/46096e27/automatingdailysendtomoderatedlist.txt From thekkumt@uchastings.edu Tue Nov 26 22:11:52 2002 From: thekkumt@uchastings.edu (Sony Z Thekkumthara) Date: Tue, 26 Nov 2002 14:11:52 -0800 Subject: [Mailman-Developers] error reading SMTP packet; response to dot-stuffed message expected Message-ID: <3DE38128.24292.1344C99@localhost> Hi All, I am using mailman since 5 months and very impressed with its efficiency. Lately I was told by some users that they are not getting few messages or they are getting a delivery delay error from their internet service provider saying somthing like "error reading SMTP packet; response to dot-stuffed message expected" This is happens sometimes when the user trys to post a message from outside. Could anyone please shed some light on this ... Thank You So Much... Zach From danny@terweij.nl Wed Nov 27 14:06:26 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 27 Nov 2002 15:06:26 +0100 Subject: [Mailman-Developers] [Fwd: automating daily send to moderated list] References: <3DDB569D.5020604@boom.org.il> Message-ID: <0fd801c2961e$2cf2f360$1e00a8c0@onsnet.org> Which version of mailman? mailman 2.1bx can do it. If i remember somthing with senders filters at the web GUI interface. Then you can enter a email adress that can send messages without aproving it. Or just subscribe the email address which started the cronjob. Danny. ----- Original Message ----- From: "Sagi Bashari" To: Sent: Wednesday, November 20, 2002 10:32 AM Subject: [Mailman-Developers] [Fwd: automating daily send to moderated list] > No answer on users list, forwarding to developers. > Hello, I'm trying to set up a large mailing list (~80k subscribers) using mailman. It is a moderated list. I would like to automate send of a daily newsletter to all the subscribers (by script that runs as a cronjob on the same machine as mailman). However, I don't want to go and approve the mail manually everyday. Is that possible? Sagi ---------------------------------------------------------------------------- ---- > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > From noreply@sourceforge.net Wed Nov 27 14:04:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 06:04:18 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message header/body Message-ID: Patches item #644129, was opened at 2002-11-26 09:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Edit held message header/body Initial Comment: Here is my preliminary (brute force) patch to allow full editing of headers and bodies of messages being held for approval in Mailman 2.1 (as of beta 5). I have released versions of this for 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before releasing this one. You must set HOLD_MESSAGES_AS_PICKLES = 0 in your installation's mm_cfg.py for this to work. I may support pickles in a future version. Personally I don't see that much performance difference anyway, not on the held stuff... Also note that if you had HOLD_MESSAGES_AS_PICKLES = 1 (the default) when you created a list, you must recreate it after changing that variable. (Learned the hard way) This patch overrides the ADMINDB_PAGE_TEXT_LIMIT setting, so if you have megabyte messages being held, be ready to wait. Also - this version doesn't change the request database, so if you change the Subject: header you won't see the change reflected in the summary list (but it will be sent out your way when you Approve). Happy mailmanning! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 09:04 Message: Logged In: YES user_id=12800 I'm moving this to the 2.2/3.0 group since we're in feature freeze for 2.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 From noreply@sourceforge.net Wed Nov 27 15:21:10 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 07:21:10 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644773 ] "description" doesn't get encoded Message-ID: Bugs item #644773, was opened at 2002-11-27 16:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_id=103 From noreply@sourceforge.net Wed Nov 27 15:21:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 07:21:33 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644774 ] "description" doesn't get encoded Message-ID: Bugs item #644774, was opened at 2002-11-27 16:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_id=103 From noreply@sourceforge.net Wed Nov 27 15:23:16 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 07:23:16 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644774 ] "description" doesn't get encoded Message-ID: Bugs item #644774, was opened at 2002-11-27 16:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_id=103 Category: None Group: 2.1 beta >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) >Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_id=103 From noreply@sourceforge.net Wed Nov 27 15:56:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 07:56:42 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply@sourceforge.net Wed Nov 27 15:58:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 07:58:33 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:13:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:13:30 -0800 Subject: [Mailman-Developers] [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 00:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:16:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:16:18 -0800 Subject: [Mailman-Developers] [ mailman-Patches-634303 ] Recode pipermail templates Message-ID: Patches item #634303, was opened at 2002-11-06 03:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 Category: Pipermail Group: Mailman 2.1 >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Recode pipermail templates Initial Comment: This patch transparently recodes the pipermail templates and messages if the article and index files have a different encoding than the template language If necessary, HTML character references are generate. If recoding fails, it will proceed without exception, but produce garbage. For messages, this uses a method self._, which first invokes _, then does the recoding. This makes it necessary for _ to go back more than one frame, so the number of frames is now an optional parameter (defaulting to 1). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:16 Message: Logged In: YES user_id=12800 That's a good point (not having the codec). I'm happy with producing an error if the message comes in a charset for which there's no installed codec. I'll make sure that happens. ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-11-18 18:25 Message: Logged In: YES user_id=21627 My concern with this approach is that we might not have a codec for the encoding of the message. That means we cannot decode the message to unicode, which means we cannot htmlify unsupported characters. OTOH, we do have codecs for the preferred encodings of all supported languages. [Sorry I didn't think of this issue when we were talking about it recently] If we consider this case unlikely to occur in real life, and are prepared to produce some error message in the page if it does happen, then the approach is fine. As for PEP293: Yes, this is precisely the intention: it simplifies generating html-escaped strings, and it is more efficient than any other strategy (since the codec will call the error handling only when an encoding error occurs). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 15:46 Message: Logged In: YES user_id=12800 Feel free to shoot holes in this, but I think it might not be simpler to just get rid of the multiple _charsets stuff in HyperArch.HyperArchive. Say we always encode the indices pages with the character set of the list's preferred language, except that we also html-ify any bogus characters outside that charset. Seems to me we can chop a bunch of code and still get the results we want, even if at the expense of potentially bigger pages (which I don't care about). I'm going to commit some changes and test them out on the playground list. This seem to work well here for my test lists. Semi-related: would PEP 293 allow us to get rid of unicode_quote? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:53 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634274 ] Some digest seems to have a wrong Message-ID: Bugs item #634274, was opened at 2002-11-06 01:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: divine rites (divinerites) Assigned to: Nobody/Anonymous (nobody) Summary: Some digest seems to have a wrong Initial Comment: Some Zope digests looks ugly with Evolution. Some digests on some lists are concerned. Not predictable. Digest should look like all normal ones (like for all digests who works fine in evolution) This link give the whole explanation for the digest problem from the evolution point of view. It seems that the mail has some wrong type. http://bugzilla.ximian.com/show_bug.cgi?id=33282 I don't know what Mailman version it is but i guess zope lists use a brand new mailman ;-)) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-07 15:44 Message: Logged In: YES user_id=12800 Actually the Zope lists use Mailman 2.0. I've tested this for MM2.1 plaintext (RFC 1153) digest and can't verify it, so I suspct it's no longer a bug. If it's happening in MM2.0 I can't see it in the code, but I doubt it will get fixed in that branch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:53 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631200 ] qrunner in loop, keeps eating memory Message-ID: Bugs item #631200, was opened at 2002-10-30 14:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631200&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Andreas Hasenack (pandora) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner in loop, keeps eating memory Initial Comment: mailman-2.0.13 python-2.2.1 Every now and then qrunner goes nuts and starts eating up all available memory on the system. I'm attaching a .msg and .db file which seems to reproduce the problem at all times, and also a log trace which showed up in the error log when I pressed CTRL-C. This last log shows where qrunner was looping, and it's in pickle.loads (log below). Oct 30 16:06:47 2002 qrunner(25698): Traceback (most recent call last): Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 222, in ArchiveMail Oct 30 16:06:47 2002 qrunner(25698): h.close() Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 304, in close Oct 30 16:06:47 2002 qrunner(25698): self.update_dirty_archives() Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 935, in update_dirty _archives Oct 30 16:06:47 2002 qrunner(25698): self.__super_update_dirty_archives() Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 513, in update_dirty _archives Oct 30 16:06:47 2002 qrunner(25698): self.update_archive(i) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 938, in update_archi ve Oct 30 16:06:47 2002 qrunner(25698): self.__super_update_archive(archive) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 420, in update_archi ve Oct 30 16:06:47 2002 qrunner(25698): self._update_simple_index(hdr, archive, arcdir) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 437, in _update_simp le_index Oct 30 16:06:47 2002 qrunner(25698): article = self.database.getArticle(self.archive, msgid) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 281, in getArtic le Oct 30 16:06:47 2002 qrunner(25698): article = self.__cache[msgid] = pickle.loads(buf) Oct 30 16:06:47 2002 qrunner(25698): File "", line 0, in ? Oct 30 16:06:47 2002 qrunner(25698): KeyboardInterrupt Oct 30 16:06:47 2002 (25698) CORRUPT ARCHIVE FOR LIST: commits I don't know if the CORRUPT ARCHIVE message is due to me pressing CTRL-C or if there is actually something wrong with it. Any help would be greatly appreciated. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631200&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:54 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-611185 ] rmlist doesn't delete lock files Message-ID: Bugs item #611185, was opened at 2002-09-18 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Linda Julien (leira) Assigned to: Nobody/Anonymous (nobody) Summary: rmlist doesn't delete lock files Initial Comment: I'm using 2.0.13. The rmlist script doesn't delete lock files associated with the list (if any exist). Removing a list and creating a new one with the same name can have unexpected results. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:54 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-612784 ] feature-request : Use of Spamassassintag Message-ID: Bugs item #612784, was opened at 2002-09-22 06:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Alexandre Dulaunoy (adulau) Assigned to: Nobody/Anonymous (nobody) Summary: feature-request : Use of Spamassassintag Initial Comment: Mail::SpamAssassin is adding a tag when He suspects to be a spam. Do you plan to add a test on it and not forward mail into the mailing if the tag is present ? It's also useful when the list is moderated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:54 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-610265 ] Bad date field causes archiver to crash Message-ID: Bugs item #610265, was opened at 2002-09-16 19:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610265&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Tim Potter (tpot) Assigned to: Nobody/Anonymous (nobody) Summary: Bad date field causes archiver to crash Initial Comment: The following date header causes the archiver to crash with an exception. Date: Fri, 1 Jan 1904 10:52:29 +1000 Traceback (innermost last): File "/var/mailman/bin/arch", line 129, in ? main() File "/var/mailman/bin/arch", line 119, in main archiver.close() File "/var/mailman/Mailman/Archiver/pipermail.py", line 306, in close self.write_TOC() File "/var/mailman/Mailman/Archiver/HyperArch.py", line 897, in write_TOC self.sortarchives() File "/var/mailman/Mailman/Archiver/HyperArch.py", line 835, in sortarchives self.archives.sort(sf) File "/var/mailman/Mailman/Archiver/HyperArch.py", line 826, in sf al=s.volNameToDate(a) File "/var/mailman/Mailman/Archiver/HyperArch.py", line 821, in volNameToDate return time.mktime((year,month,1,0,0,0,0,1,-1)) OverflowError: mktime argument out of range [whoops - the line numbers are out by one because I added some debugging] [tpot@dp:~]$ rpm -qa | grep mailman mailman-2.0.11-1 Regards, Tim. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610265&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-553557 ] Message Size not enforced properly Message-ID: Bugs item #553557, was opened at 2002-05-07 23:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=553557&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: rich cowan (leftlink) Assigned to: Nobody/Anonymous (nobody) Summary: Message Size not enforced properly Initial Comment: I sent an 26K message that also was sent out by my eudora in an HTML version to a list that is supposed to be capped at a 40K limit. The html made the message into a 112K message, and it apparently went out anyway. the msg is at: http://lists.democracygroups.org/pipermail/rwwatch/2002 q2.txt This message was sent as both plain and styled text from eudora. It seems to me that if someone makes the mistake of leaving styled text on then Mailman should catch that, i.e. the "message body" should be calculated as the number of KB of both the plain and html portions of a message. the whole idea of the message size limit is to enforce a restriction so that a moderator of the list can make the email list more friendly to modem users, and when you end up letting huge html mail through, it kind of defeats the purpose. -rich cowan "Nonprofit Open Source Initiative" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=553557&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-596215 ] html bugs in 2.0.13 Message-ID: Bugs item #596215, was opened at 2002-08-16 14:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596215&group_id=103 Category: Web/CGI Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Chuq Von Rospach (chuqui) Assigned to: Nobody/Anonymous (nobody) Summary: html bugs in 2.0.13 Initial Comment: Ran into some HTML bugs in 2.0.13. For instance, going to the listinfo/mailman-subscribers page and subscribing, it returns the "confirmation is required" warning. It looks good, but view source it. An unterminated " is in the body, not in the head. While it seems to format okay in browsers, it's seriously broken HTML, and it's driving mod_layout nuts, since it depends on the body tags to do header/footer insertions right. I think there's one other generated page with similar problems, too, but I'm not sure which it is yet. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596215&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:53 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631447 ] error during subscription process Message-ID: Bugs item #631447, was opened at 2002-10-31 04:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631447&group_id=103 Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Carlo Meme' (cmeme) Assigned to: Nobody/Anonymous (nobody) Summary: error during subscription process Initial Comment: One user trying to subscribe got the following email message: Bug in Mailman version 2.0.13 We're sorry, we hit a bug! The information in the log are: admin(8347): [----- Mailman Version: 2.0.13 -----] admin(8347): [----- Traceback ------] admin(8347): Traceback (innermost last): admin(8347): File "/var/mailman/scripts/driver", line 96, in run_main admin(8347): main() admin(8347): File "/var/mailman/Mailman/Cgi/subscribe.py", line 76, in main admin(8347): process_form(mlist, doc) admin(8347): File "/var/mailman/Mailman/Cgi/subscribe.py", line 104, in process_form admin(8347): if form.has_key("UserOptions") or \ admin(8347): File "/var/mailman/Mailman/pythonlib/cgi.py", line 564, in has_key admin(8347): raise TypeError, "not indexable" admin(8347): TypeError: not indexable admin(8347): [----- Python Information -----] admin(8347): sys.version = 1.5.2 (#1, Jul 5 2001, 03:02:19) [GCC 2.96 20000731 (Red Hat Linux 7.1 2 admin(8347): sys.executable = /usr/bin/python admin(8347): sys.prefix = /usr admin(8347): sys.exec_prefix= /usr admin(8347): sys.path = /usr admin(8347): sys.platform = linux-i386 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631447&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:53 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631186 ] Postfix msg.type Message-ID: Bugs item #631186, was opened at 2002-10-30 14:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631186&group_id=103 Category: bounce detection Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Gregory Karpinsky, TIV.NET Inc. (tivnet) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix msg.type Initial Comment: In Postfix.py, I replaced 'multipart/mixed' with 'multipart/report' -- and now the bouncing works for me. I have: postfix-20011210_1 mailman-2.0.13 gregory at tiv.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631186&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:53 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-634026 ] Spurious option text on subscription GUI Message-ID: Bugs item #634026, was opened at 2002-11-05 15:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634026&group_id=103 Category: Web/CGI Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Spurious option text on subscription GUI Initial Comment: Mailman version 2.0.13 Nondigest option: nondigestable = 1 Subscription Page with option text without radio button confuses subscriber. Would you like to receive list mail batched in a daily digest? No Yes ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634026&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:52 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-641436 ] traceback for set nomail for non-member Message-ID: Bugs item #641436, was opened at 2002-11-20 15:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641436&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Marilyn Davis (marilyndavis) Assigned to: Nobody/Anonymous (nobody) Summary: traceback for set nomail for non-member Initial Comment: If a non-member of a list sends a mail message to the request address to "set nomail on passwd", the non-member gets a traceback and the admin gets an "unexpected mailman error" message. Instead, the MailCommandHandler probably wants to catch the exception and suggest to the non-user that she joins the list before she turns off her mail stream. I did this accidentally, first with an unknown password and the second time with the admin's password. Each traceback is a little different. I hope this is helpful. Thank you, Marilyn Davis The MailCommandHandler.py >From t2-request@localhost.localdomain Tue Nov 19 14:24:13 2002 Date: Tue, 19 Nov 2002 13:31:01 -0800 From: t2-request@localhost.localdomain To: marilyn@localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. >>>>> Subject line ignored: >>>>> Re: Mailman results for T2 ***** set nomail on XXXXXXXX >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at . The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 376, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/home/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError >From t2-request@localhost.localdomain Tue Nov 19 14:24:19 2002 Date: Tue, 19 Nov 2002 13:32:01 -0800 From: t2-request@localhost.localdomain To: marilyn@localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. ***** set nomail on (the admin password) >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at . The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 412, in ProcessSetCmd self.SetUserOption(sender, option_info[args[0]], value) File "/home/mailman/Mailman/MailList.py", line 206, in SetUserOption user = self.GetUserCanonicalAddress(user) File "/home/mailman/Mailman/MailList.py", line 174, in GetUserCanonicalAddress cpuser = self.GetUserSubscribedAddress(member) File "/home/mailman/Mailman/MailList.py", line 159, in GetUserSubscribedAddress member = string.lower(member) File "/usr/local/lib/python2.2/string.py", line 54, in lower return s.lower() AttributeError: 'NoneType' object has no attribute 'lower' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641436&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-449677 ] HyperArch.py assumes charsets are in \w+ Message-ID: Bugs item #449677, was opened at 2001-08-09 21:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=449677&group_id=103 Category: Pipermail Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Ben Gertzfield (che_fox) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py assumes charsets are in \w+ Initial Comment: Using Mailman 2.0.6, I noticed that Japanese messages in charset iso-2022-jp are not archived correctly; their subject lines stay in MIME-encoded format, like Subject: =?ISO-2022-JP?B?WxskQiQqTD5BMBsoQi5jb21dLmNvbS8uag==?= etc. I tracked this down to the following line in HyperArch.py:158 # content-type charset rx_charset = re.compile('charset="(\w+)"') This is incorrect. According to the de-facto list of charsets at http://www.iana.org/assignments/character-sets charsets can have all sorts of characters outside of [a-zA-Z0-9_] , such as - ( ) : . etc. So, we must accept anything between the quotes with a fuzzy .+? match, instead of forcing \w+. Patch attached, against Mailman 2.0.6. ---------------------------------------------------------------------- Comment By: Ben Gertzfield (che_fox) Date: 2001-08-09 22:53 Message: Logged In: YES user_id=89313 Note: this is the solution to the problem in Bug #431511. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=449677&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-606978 ] explicit email Reply-To header Problem Message-ID: Bugs item #606978, was opened at 2002-09-09 17:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=606978&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Joel Webb (webbgroup) Assigned to: Nobody/Anonymous (nobody) Summary: explicit email Reply-To header Problem Initial Comment: I am running RH 7.3 with mailman 2.0.12 I have configured some list to use a specific email address to reply to. Now I am trying to delete the address and have the list server replies to back to the original poster. I have clicked on the Poster radiobox and delete the email address that is in the explicit email Reply-To header. After I click save changes, the Poster radiobox has been changed but the explicit email Reply-To header still stays inside the textbox without deletion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=606978&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:52 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore Message-ID: Bugs item #640775, was opened at 2002-11-19 11:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: Works For Me >Priority: 1 Submitted By: David Weisgerber (davidweisgerber) Assigned to: Nobody/Anonymous (nobody) Summary: Qrunner suddenly doesn't work anymore Initial Comment: Since I checked my e-mail-account today I had over 1000 new mails where my cron daemon worries about those errors with your qrunner and listinfo.py: (1) "Traceback (most recent call last): File "/home/mailman/cron/qrunner", line 84, in ? from Mailman import Utils EOFError: EOF read where object expected" (2) "Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 40, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 36, in ? from Mailman import Utils EOFError: EOF read where object expected" Don't know why, I didn't changed something on the machine and there is noone who could change something. Hard disk space is also okay. So I couldn't figure out where the problem was but I hope you can fix it, the web page shows your 'A bug in mailman' page and this is a cat from /logs/error: "Oct 01 10:10:46 2002 (12542) listinfo: no such list "csi172": Oct 01 10:11:05 2002 (12546) Someone tried to access the admin interface for a non-existent list: csi172 Nov 19 18:10:17 2002 admin(9683): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9683): [----- Mailman Version: 2.0.11 -----] admin(9683): [----- Traceback ------] admin(9683): Traceback (most recent call last): admin(9683): File "/home/mailman/scripts/driver", line 90, in run_main admin(9683): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9683): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9683): from Mailman import Utils admin(9683): EOFError: EOF read where object expected admin(9683): [----- Python Information -----] admin(9683): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9683): sys.executable = /usr/bin/python admin(9683): sys.prefix = /usr admin(9683): sys.exec_prefix= /usr admin(9683): sys.path = /usr admin(9683): sys.platform = linux-i386 admin(9683): [----- Environment Variables -----] admin(9683): PATH_INFO: /kutro admin(9683): PYTHONPATH: /home/mailman admin(9683): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9683): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9683): SERVER_ADMIN: root@localhost admin(9683): SCRIPT_NAME: /mailman/listinfo admin(9683): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9683): REQUEST_METHOD: GET admin(9683): HTTP_HOST: md.2y.net admin(9683): HTTP_KEEP_ALIVE: 300 admin(9683): SERVER_PROTOCOL: HTTP/1.1 admin(9683): QUERY_STRING: admin(9683): REQUEST_URI: /mailman/listinfo/kutro admin(9683): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9683): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9683): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9683): HTTP_CONNECTION: keep-alive admin(9683): SERVER_NAME: md.2y.net admin(9683): REMOTE_ADDR: 192.168.0.2 admin(9683): REMOTE_PORT: 32951 admin(9683): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9683): PATH_TRANSLATED: /home/kutro-homepage admin(9683): SERVER_PORT: 80 admin(9683): GATEWAY_INTERFACE: CGI/1.1 admin(9683): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9683): SERVER_ADDR: 192.168.0.1 admin(9683): DOCUMENT_ROOT: /var/www/html Nov 19 18:10:32 2002 admin(9684): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9684): [----- Mailman Version: 2.0.11 -----] admin(9684): [----- Traceback ------] admin(9684): Traceback (most recent call last): admin(9684): File "/home/mailman/scripts/driver", line 90, in run_main admin(9684): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9684): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9684): from Mailman import Utils admin(9684): EOFError: EOF read where object expected admin(9684): [----- Python Information -----] admin(9684): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9684): sys.executable = /usr/bin/python admin(9684): sys.prefix = /usr admin(9684): sys.exec_prefix= /usr admin(9684): sys.path = /usr admin(9684): sys.platform = linux-i386 admin(9684): [----- Environment Variables -----] admin(9684): PYTHONPATH: /home/mailman admin(9684): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9684): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9684): SERVER_ADMIN: root@localhost admin(9684): SCRIPT_NAME: /mailman/listinfo admin(9684): SERVER_SIGNATURE:
    Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80
    admin(9684): REQUEST_METHOD: GET admin(9684): HTTP_HOST: md.2y.net admin(9684): HTTP_KEEP_ALIVE: 300 admin(9684): SERVER_PROTOCOL: HTTP/1.1 admin(9684): QUERY_STRING: admin(9684): REQUEST_URI: /mailman/listinfo admin(9684): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9684): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9684): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9684): HTTP_CONNECTION: keep-alive admin(9684): SERVER_NAME: md.2y.net admin(9684): REMOTE_ADDR: 192.168.0.2 admin(9684): REMOTE_PORT: 32951 admin(9684): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9684): SERVER_PORT: 80 admin(9684): GATEWAY_INTERFACE: CGI/1.1 admin(9684): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9684): SERVER_ADDR: 192.168.0.1 admin(9684): DOCUMENT_ROOT: /var/www/html" PS: The logs say that there were no recent activities on any list. ---------------------------------------------------------------------- Comment By: David Weisgerber (davidweisgerber) Date: 2002-11-21 12:39 Message: Logged In: YES user_id=477011 This fixed it for me: Delete /Mailman/Utils.pyc ==> Maybe it's just a python error ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:56 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-431511 ] charset="Windows-1252" in archive Message-ID: 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_id=103 Category: Pipermail Group: 2.0.x Status: Open Resolution: None >Priority: 1 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=103&atid=100103 -- 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_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-545956 ] digest mode dont recognize latin-1 Message-ID: Bugs item #545956, was opened at 2002-04-19 01:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=545956&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: Out of Date >Priority: 1 Submitted By: Veronica Loell (mindtrader) Assigned to: Nobody/Anonymous (nobody) Summary: digest mode dont recognize latin-1 Initial Comment: We just started a list where we commicate in swedish and hence use åäö from Latin-1. One of the members have choosen digest-mode and we have discovered a problem. All our mails use latin-1, and in the non-digest form and also in the archives all charachters are displayed correctly. In digest form however, the letters äåö are marked as unknown, with their hex-numbers given. I have tested this by having both digest and non-digest delivered to me, using the same mailer etc. --------- Digest --------- Date: Thu, 18 Apr 2002 07:55:22 +0200 (W. Europe Daylight Time) From: Veronica Loell To: Subject: [cvs] =?ISO-8859- 1?Q?test_med_=E5=E4=F6?= Detta =E4r bara ett test f=F6r att utreda problemet med latin-1 i digestversionen. =C5=C4=D6 =E5=E4=F6 --------- Non-digest --------- Date: Thu, 18 Apr 2002 07:55:22 +0200 (W. Europe Daylight Time) From: Veronica Loell To: ag-cling- cvs@lists.sourceforge.net Subject: [cvs] test med åäö Detta är bara ett test för att utreda problemet med latin-1 i digestversionen. ÅÄÖ åäö ---------------------------------------------------------------------- Comment By: Veronica Loell (mindtrader) Date: 2002-04-24 01:16 Message: Logged In: YES user_id=156789 It seems that this problem also is present when posts are held for approval. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-19 14:40 Message: Logged In: YES user_id=12800 Well, now I'm not positive. Can you send a message to mailman-developers and see what other people think? ---------------------------------------------------------------------- Comment By: Veronica Loell (mindtrader) Date: 2002-04-19 14:04 Message: Logged In: YES user_id=156789 Actually mailman does handle it perfectly, it only happens in the digest mode. And it is also not the header that is the problem it's the body of the email. But if this has been corrected I'll report it to sourceforge because they apperantly are using an old version. I do get plenty of email where the header is messed up, but the rest of the message is not. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-19 13:53 Message: Logged In: YES user_id=12800 Mailman 2.1 will correctly handle non-ascii characters in headers. The problem is (probably) that the addition of the prefix breaks rfc2047 encoding of the non-ascii characters in the Subject: header. ---------------------------------------------------------------------- Comment By: Veronica Loell (mindtrader) Date: 2002-04-19 01:28 Message: Logged In: YES user_id=156789 I forgot to say. This is the listmanager managed by Sourceforge. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=545956&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:55 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11 Message-ID: Bugs item #563336, was opened at 2002-06-01 12:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:56 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-427421 ] Configure script problem on Mac OS X. Message-ID: 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_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: Works For Me >Priority: 1 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 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_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:54 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-608524 ] QRUNNER is fucking the machine perform.. Message-ID: Bugs item #608524, was opened at 2002-09-12 13:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Jozeph Brasil (jozeph) Assigned to: Nobody/Anonymous (nobody) Summary: QRUNNER is fucking the machine perform.. Initial Comment: Hello Everybody, I'm with a big problem... :( I'm running mailman-2.0.13-1U70_1cl under python-2.1-14cl with gcc-2.95.3-20U70_1cl in an IBM NETFINITY 300 PIII 500 XEXON with 64MiB. When qrunner starts the proccess my machine stay totally SLOWLY... Look the qrunner proccess: mailman 12365 95.7 51.2 32340 30092 tty1 R 15:27 4:37 python -S cron/qrunner How you can see... look at the CPU / MEM usage... I need to wait more less 30 minutes to qrunner stop the proccess and... In qfiles directory have only 10 or 15 messages in delivery... Anyone have idea what's up? How fix that? PS: I disable my mailman at moment... :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:19:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:19:53 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640664 ] autowrap lines over 1000 chars Message-ID: Bugs item #640664, was opened at 2002-11-19 07:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103 Category: nntp/news Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Chris Dudley (dudleyc) Assigned to: Nobody/Anonymous (nobody) Summary: autowrap lines over 1000 chars Initial Comment: NNTP has a maximum line length of 1000 chars. emails do not have the same restriction. Would it be possible for the script which posts emails to the mailing list to autowrap all the emails at 1000 characters so that they would still be valid nntp posts? Currently i'm getting a fair few error 441 returns from NNTP because some emails exceed the line length limit. It could wrap at the last space or hyphon before the 1000th character, or something similar. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:26:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:26:32 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-626125 ] listinfo page doesn't show newsgrp name Message-ID: Bugs item #626125, was opened at 2002-10-20 19:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=626125&group_id=103 Category: Web/CGI >Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ben Elliston (elliston) Assigned to: Nobody/Anonymous (nobody) Summary: listinfo page doesn't show newsgrp name Initial Comment: If a mailing list is gatewayed to a newsgroup, the listinfo page does not help a user discover what the newsgroup is, or where to read it! Can this be added? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=626125&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-610570 ] RFC 2369 URL is broken Message-ID: Bugs item #610570, was opened at 2002-09-17 10:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Nick Arnett (narnett) Assigned to: Nobody/Anonymous (nobody) Summary: RFC 2369 URL is broken Initial Comment: Paths to RFCs have changed. The correct one for 2369 is now http://www.faqs.org/rfcs/rfc2369.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643233 ] E-mail addresses not being obscured Message-ID: Bugs item #643233, was opened at 2002-11-24 16:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: E-mail addresses not being obscured Initial Comment: In 2.1b5, the archives contain the posters e-mail address even if the option to obscure the posters identity has been selected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643233&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644294 ] Uncaught runner exception Message-ID: Bugs item #644294, was opened at 2002-11-26 14:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: Getting these repeatedly: Nov 26 14:17:11 2002 (327) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 26 14:17:11 2002 (327) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/opt/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- Comment By: Terry Grace (tgrace) Date: 2002-11-26 20:40 Message: Logged In: YES user_id=87771 Archives broken too. After restarting the deamons, only the first article posted gets archived. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643231 ] Last archived date is incorrect Message-ID: Bugs item #643231, was opened at 2002-11-24 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Last archived date is incorrect Initial Comment: The last archived date/time is incorrect. Time appears to be GMT, not local time (e.g. ahead 5 hrs for sites in EST) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE Message-ID: Bugs item #612174, was opened at 2002-09-20 11:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Jay Luker (lbjay) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe_policy + ALLOW_OPEN_SUBSCRIBE Initial Comment: There is a flaw somewhere in the logic that alters the value of subscribe_policy based on the value of mm_cfg.ALLOW_OPEN_SUBSCRIBE. I have ALLOW_OPEN_SUBSCRIBE = 0. When I attempt to set subscribe_policy = 1 via the config_list script, subscribe_policy is always set to 2. ---------------------------------------------------------------------- Comment By: Jay Luker (lbjay) Date: 2002-09-20 12:02 Message: Logged In: YES user_id=51347 OK, I was just able to track this down further. The problem (I think) lies in Gui/Privacy.py. _setValue states: "For subscribe_policy when ALLOW_OPEN_SUBSCRIBE is true, we need to add one to the value because the page didn't present an open list as an option." ... but then the subsequent code actually adds one to the value if ALLOW_OPEN_SUBSCRIBE is untrue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643605 ] RFC2882 and / in subscriber address Message-ID: Bugs item #643605, was opened at 2002-11-25 10:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: RFC2882 and / in subscriber address Initial Comment: Reproduced from the mailman-users list. Thanks to Bill for the followup. --chris [][][][][][] Majordomo would tell you the same thing but I agree that it is a legal address (we use similar addresses internally at work) and should be accepted. RFC2822 (http://www.faqs.org/rfcs/rfc2822.html) clearly allows it in the local-part (Section 3.4.1) as a dot-atom. This should be fixed but in the mean time I don't think you are going to get it into mailman. Bill W. At 09:31 AM 11/25/2002 -0600, Christopher Kolar wrote: Hello. I am trying to add a person to a mail list and having some problems. Their organization runs some sort of bestial mail system where the addresses are of the form: schmoe.j/bhs@dns.u99.k12.il.us When I try to drop the address in through the mass subscribe screen I get the following message from Mailman: * Joe Schmoe -- Hostile address (illegal characters) My guess is that the / is getting parsed by Mm as an attempt to reference a file (a la majordomo). Is there a way to force the address onto the subscriber list? It is an actual valid address for delivery. Thanks in advance, --chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-626125 ] listinfo page doesn't show newsgrp name Message-ID: Bugs item #626125, was opened at 2002-10-20 19:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=626125&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Ben Elliston (elliston) Assigned to: Nobody/Anonymous (nobody) Summary: listinfo page doesn't show newsgrp name Initial Comment: If a mailing list is gatewayed to a newsgroup, the listinfo page does not help a user discover what the newsgroup is, or where to read it! Can this be added? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=626125&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640374 ] 2.1b4 Mailman bug Message-ID: Bugs item #640374, was opened at 2002-11-18 17:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b4 Mailman bug Initial Comment: When I try to access some of my lists via the web interface to moderate them I receive this error message: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admindb.py", line 227, in main show_pending_unsubs(mlist, form) File "/var/mailman/Mailman/Cgi/admindb.py", line 332, in show_pending_unsubs fullname = Utils.uncanonstr(mlist.getMemberName (addr), lang) File "/var/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/var/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member NotAMemberError: capeterson28@hotmail.com This is only a problem for some of my lists. Some lists I can log into and moderate successfully from the Web. I am running Mailman 2.1b4 on RedHat Linux 7.3. Let me know if you need more information. Thanks for your help. Paul Marshall ---------------------------------------------------------------------- Comment By: Paul Marshall (paulmarshll) Date: 2002-11-19 14:27 Message: Logged In: YES user_id=582441 I recently upgraded to Mailman 2.1b5, however I still receive this error when I try to log into some of the lists. Thanks. Paul. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-214205 ] e-mail<-> usenet gateway Reply-To header (PR#303) Message-ID: Bugs item #214205, was opened at 2000-09-11 16:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103 Category: nntp/news Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry A. Warsaw (bwarsaw) >Summary: e-mail<->usenet gateway Reply-To header (PR#303) Initial Comment: Jitterbug-Id: 303 Submitted-By: orion@tribble.dyndns.org Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT) Version: 2.0beta4 OS: Debian linux potato I'm running a plain e-mail<->usenet gateway. When someone replies to a usenet post through the list, his e-mail client sets an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to improperly thread messages. I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line 82: # if the message is a reply to a previous post, change the header so # that newsreaders can thread it properly if msg.getheader('in-reply-to'): msg.headers.append('References: %s\n' % msg.getheader('in-reply-to')) del msg['in-reply-to'] I'm happy to say that this solved the problem. (before you laugh at me, take note that I never looked at python before.) ==================================================================== Audit trail: None ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:38 Message: Logged In: YES user_id=12800 Changing the group to 2.1 beta because I want to look at threading issues for gated messages before 2.1 final is released. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-01 08:34 Message: Logged In: YES user_id=531451 What a coincidence! I had the same problem and I looked into the code, then modified it to work properly. The coincidence is that my patch is *identical* to yours. So, for sure it works :-) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-27 17:00 Message: RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-19 12:48 Message: This sounds like the email client in question is broken. Mine for example, correctly inserts References: headers and the news readers properly thread the messages. I'm not inclined to cater to broken email or news clients. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644005 ] sync_members: problems with u umlaut Message-ID: Bugs item #644005, was opened at 2002-11-26 04:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members: problems with u umlaut Initial Comment: Running sync_members -n, I get this error, when a member with an umlaut-u in it's real name gets removed. Traceback (most recent call last): File "/usr/sbin/sync_members", line 283, in ? main() File "/usr/sbin/sync_members", line 275, in main print _('Removed: <%(addr)30s> %(name)s') UnicodeError: ASCII encoding error: ordinal not in range(128) Changing the ü in the web-frontend to ue, and then running again sync_members "fixes" the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631569 ] conn.quit() -> SMTPServerDisconnected Message-ID: Bugs item #631569, was opened at 2002-10-31 09:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631569&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Denzel D'aviagio (uplink2sf) Assigned to: Nobody/Anonymous (nobody) >Summary: conn.quit() -> SMTPServerDisconnected Initial Comment: well this is driving me insane. had it since 2.1b3 on RedHat 7.2 using python 2.2 (stock rpm install). there's a few lists active but mail gets delivered rarely - seems when sending mail, Mailman/Handlers/SMTPDirect.py fails to conn.quit() thus raising a SMTPServerDisconnected: please run connect() first ...weird! please find attached looots of logfiles that hopefully make sense to you. I have too little knowledge of python (<=0) to investigate more. --- root [tweak] # $(which python2) -v # /usr/lib/python2.2/site.pyc matches /usr/lib/python2.2/site.py import site # precompiled from /usr/lib/python2.2/site.pyc # /usr/lib/python2.2/os.pyc matches /usr/lib/python2.2/os.py import os # precompiled from /usr/lib/python2.2/os.pyc import posix # builtin # /usr/lib/python2.2/posixpath.pyc matches /usr/lib/python2.2/posixpath.py import posixpath # precompiled from /usr/lib/python2.2/posixpath.pyc # /usr/lib/python2.2/stat.pyc matches /usr/lib/python2.2/stat.py import stat # precompiled from /usr/lib/python2.2/stat.pyc # /usr/lib/python2.2/UserDict.pyc matches /usr/lib/python2.2/UserDict.py import UserDict # precompiled from /usr/lib/python2.2/UserDict.pyc Python 2.2 (#1, Apr 12 2002, 15:29:57) [GCC 2.96 20000731 (Red Hat Linux 7.2 2.96-109)] on linux2 Type "help", "copyright", "credits" or "license" for more information. dlopen("/usr/lib/python2.2/lib-dynload/readline.so", 2); import readline # dynamically loaded from /usr/lib/python2.2/lib-dynload/readline.so >>> --- the following logfile mix is obfuscated a bit (email and IP addresses) 08017 >>> 220 companyMail ESMTP 08017 <<< EHLO company.at 08017 >>> 250-mx.company.at Hello fqdn.domain.net [2.3.4.5], pleased to meet you 08017 >>> 250-ENHANCEDSTATUSCODES 08017 >>> 250-PIPELINING 08017 >>> 250-8BITMIME 08017 >>> 250-SIZE 08017 >>> 250-DSN 08017 >>> 250-ETRN 08017 >>> 250-AUTH DIGEST-MD5 CRAM-MD5 08017 >>> 250-STARTTLS 08017 >>> 250-DELIVERBY 08017 >>> 250 HELP 08017 <<< STARTTLS 08017 >>> 220 2.0.0 Ready to start TLS 08018 >>> 220 companyMail ESMTP 08018 <<< HELO company.at 08018 >>> 250 mx.company.at Hello fqdn.domain.net [2.3.4.5], pleased to meet you 08018 <<< MAIL FROM: 08018 >>> 250 2.1.0 ... Sender ok 08018 <<< RCPT TO: 08018 >>> 250 2.1.5 ... Recipient ok 08018 <<< DATA 08018 >>> 354 Enter mail, end with "." on a line by itself 08018 <<< Date: Thu, 31 Oct 2002 15:05:15 +0100 08018 <<< Mime-Version: 1.0 (Apple Message framework v546) 08018 <<< Content-Type: text/plain; charset=US-ASCII; format=flowed 08018 <<< Subject: test 08018 <<< From: SENDER REALNAME 08018 <<< To: apfelsucht@company.at 08018 <<< Content-Transfer-Encoding: 7bit 08018 <<< Message-Id: 08018 <<< X-Mailer: Apple Mail (2.546) 08018 <<< 08018 <<< ENDOFTEST 08018 <<< 08018 <<< . 08018 >>> 250 2.0.0 g9VDs6Nu008018 Message accepted for delivery 08018 <<< QUIT 08018 >>> 221 2.0.0 mx.company.at closing connection 08019 === EXEC smrsh -c /opt/mailman/current/mail/mailman post apfelsucht 08019 >>> From SENDER@DOMAIN.NET Thu Oct 31 14:54:06 2002 08019 >>> Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; Thu, 31 Oct 2002 14:54:06 +0100 08019 >>> Date: Thu, 31 Oct 2002 15:05:15 +0100 08019 >>> Mime-Version: 1.0 (Apple Message framework v546) 08019 >>> Content-Type: text/plain; charset=US-ASCII; format=flowed 08019 >>> Subject: test 08019 >>> From: SENDER REALNAME 08019 >>> To: apfelsucht@company.at 08019 >>> Content-Transfer-Encoding: 7bit 08019 >>> Message-Id: 08019 >>> X-Mailer: Apple Mail (2.546) 08019 >>> 08019 >>> ENDOFTEST 08019 >>> Oct 31 14:54:06 tweak sm-mta[8018]: g9VDs6Nu008018: from=, size=377, class=0, nrcpts=1, msgid=, proto=SMTP, daemon=MTA, relay=fqdn.domain.net [2.3.4.5] 08019 <<< [EOF] Oct 31 14:54:07 tweak sm-mta[8019]: g9VDs6Nu008018: to="|/opt/mailman/current/mail/mailman post apfelsucht", ctladdr= (47/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30568, dsn=2.0.0, stat=Sent connect: ('localhost', 25) connect: ('localhost', 25) reply: '220 companyMail ESMTP\r\n' reply: retcode (220); Msg: companyMail ESMTP connect: companyMail ESMTP send: 'ehlo tweak.company.at\r\n' reply: '250-mx.company.at Hello localhost [127.0.0.1], pleased to meet you\r\n' reply: '250-ENHANCEDSTATUSCODES\r\n' reply: '250-PIPELINING\r\n' reply: '250-8BITMIME\r\n' reply: '250-SIZE\r\n' reply: '250-DSN\r\n' reply: '250-ETRN\r\n' reply: '250-AUTH DIGEST-MD5 CRAM-MD5\r\n' reply: '250-STARTTLS\r\n' reply: '250-DELIVERBY\r\n' reply: '250 HELP\r\n' reply: retcode (250); Msg: mx.company.at Hello localhost [127.0.0.1], pleased to meet you ENHANCEDSTATUSCODES PIPELINING 8BITMIME SIZE DSN ETRN AUTH DIGEST-MD5 CRAM-MD5 STARTTLS DELIVERBY HELP send: 'mail FROM: size=1168\r\n' reply: '250 2.1.0 ... Sender ok\r\n' reply: retcode (250); Msg: 2.1.0 ... Sender ok send: 'rcpt TO:\r\n' reply: '250 2.1.5 ... Recipient ok\r\n' reply: retcode (250); Msg: 2.1.5 ... Recipient ok send: 'data\r\n' reply: '354 Enter mail, end with "." on a line by itself\r\n' reply: retcode (354); Msg: Enter mail, end with "." on a line by itself data: (354, 'Enter mail, end with "." on a line by itself') send: "Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at\r\n\t(company.at/20021013) with SMTP id g9VDs6Nu008018 for ;\r\n\tThu, 31 Oct 2002 14:54:06 +0100\r\nDate: Thu, 31 Oct 2002 15:05:15 +0100\r\nMime-Version: 1.0 (Apple Message framework v546)\r\nContent-Type: text/plain; charset=US-ASCII; format=flowed\r\nFrom: SENDER REALNAME \r\nTo: apfelsucht@company.at\r\nContent-Transfer-Encoding: 7bit\r\nMessage-Id: \r\nX-Mailer: Apple Mail (2.546)\r\nSubject: [Apfelsucht] test\r\nX-BeenThere: apfelsucht@company.at\r\nPrecedence: list\r\nList-Id: Appl'o'holics, MacLovers & Switchers \r\nList-Post: \r\nList-Subscribe: ,\r\n\t\r\nList-Unsubscribe: ,\r\n\t\r\nList-Archive: \r\nList-Help: \r\nSender: apfelsucht-bounces@company.at\r\nErrors-To: apfelsucht-bounces@company.at\r\n\r\nENDOFTEST\r\n\r\n.\r\n" reply: '250 2.0.0 g9VDs9Nu008025 Message accepted for delivery\r\n' reply: retcode (250); Msg: 2.0.0 g9VDs9Nu008025 Message accepted for delivery data: (250, '2.0.0 g9VDs9Nu008025 Message accepted for delivery') send: 'mail FROM: size=1168\r\n' reply: '250 2.1.0 ... Sender ok\r\n' reply: retcode (250); Msg: 2.1.0 ... Sender ok send: 'rcpt TO:\r\n' send: 'quit\r\n' send: 'quit\r\n' Oct 31 14:54:09 2002 (7608) All recipients refused: please run connect() first 08025 >>> 220 companyMail ESMTP 08025 <<< ehlo tweak.company.at 08025 >>> 250-mx.company.at Hello localhost [127.0.0.1], pleased to meet you 08025 >>> 250-ENHANCEDSTATUSCODES 08025 >>> 250-PIPELINING 08025 >>> 250-8BITMIME 08025 >>> 250-SIZE 08025 >>> 250-DSN 08025 >>> 250-ETRN 08025 >>> 250-AUTH DIGEST-MD5 CRAM-MD5 08025 >>> 250-STARTTLS 08025 >>> 250-DELIVERBY 08025 >>> 250 HELP 08025 <<< mail FROM: size=1168 08025 >>> 250 2.1.0 ... Sender ok 08025 <<< rcpt TO: 08025 >>> 250 2.1.5 ... Recipient ok 08025 <<< data 08025 >>> 354 Enter mail, end with "." on a line by itself 08025 <<< Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at 08025 <<< (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; 08025 <<< Thu, 31 Oct 2002 14:54:06 +0100 08025 <<< Date: Thu, 31 Oct 2002 15:05:15 +0100 08025 <<< Mime-Version: 1.0 (Apple Message framework v546) 08025 <<< Content-Type: text/plain; charset=US-ASCII; format=flowed 08025 <<< From: SENDER REALNAME 08025 <<< To: apfelsucht@company.at 08025 <<< Content-Transfer-Encoding: 7bit 08025 <<< Message-Id: 08025 <<< X-Mailer: Apple Mail (2.546) 08025 <<< Subject: [Apfelsucht] test 08025 <<< X-BeenThere: apfelsucht@company.at 08025 <<< Precedence: list 08025 <<< List-Id: Appl'o'holics, MacLovers & Switchers 08025 <<< List-Post: 08025 <<< List-Subscribe: , 08025 <<< 08025 <<< List-Unsubscribe: , 08025 <<< 08025 <<< List-Archive: 08025 <<< List-Help: 08025 <<< Sender: apfelsucht-bounces@company.at 08025 <<< Errors-To: apfelsucht-bounces@company.at 08025 <<< 08025 <<< ENDOFTEST 08025 <<< 08025 <<< . 08025 >>> 250 2.0.0 g9VDs9Nu008025 Message accepted for delivery 08027 === CONNECT localhost 08025 <<< mail FROM: size=1168 08025 >>> 250 2.1.0 ... Sender ok 08025 <<< rcpt TO: 08027 <<< 220 company.at LMTP company 20021003 ready 08027 >>> LHLO mx.company.at Oct 31 14:54:09 tweak sm-mta[8025]: g9VDs9Nu008025: from=, size=1168, class=-30, nrcpts=1, msgid=, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Oct 31 14:54:09 2002 (7608) Uncaught runner exception: please run connect() first Oct 31 14:54:09 2002 (7608) Traceback (most recent call last): File "/opt/mailman/current/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/current/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/current/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/opt/mailman/current/Mailman/Handlers/SMTPDirect.py", line 149, in process conn.quit() File "/opt/mailman/current/Mailman/Handlers/SMTPDirect.py", line 79, in quit self.__conn.quit() File "/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first 08027 <<< 250-company.at 08027 <<< 250-8BITMIME 08027 <<< 250-ENHANCEDSTATUSCODES 08027 <<< 250-PIPELINING 08027 <<< 250-SIZE 08027 <<< 250-AUTH EXTERNAL 08027 <<< 250 IGNOREQUOTA 08027 >>> MAIL From: SIZE=1168 08027 <<< 250 2.1.0 ok 08027 >>> RCPT To: 08027 >>> DATA 08027 <<< 250 2.1.5 ok 08027 <<< 354 go ahead 08027 >>> Return-Path: 08027 >>> Received: from tweak.company.at (localhost [127.0.0.1]) by mx.company.at (company.at/20021013) with ESMTP id g9VDs9Nu008025 for ; Thu, 31 Oct 2002 14:54:09 +0100 08027 >>> Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at 08027 >>> (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; 08027 >>> Thu, 31 Oct 2002 14:54:06 +0100 08027 >>> Date: Thu, 31 Oct 2002 15:05:15 +0100 08027 >>> Mime-Version: 1.0 (Apple Message framework v546) 08027 >>> Content-Type: text/plain; charset=US-ASCII; format=flowed 08027 >>> From: SENDER REALNAME 08027 >>> To: apfelsucht@company.at 08027 >>> Content-Transfer-Encoding: 7bit 08027 >>> Message-Id: 08027 >>> X-Mailer: Apple Mail (2.546) 08027 >>> Subject: [Apfelsucht] test 08027 >>> X-BeenThere: apfelsucht@company.at 08027 >>> Precedence: list 08027 >>> List-Id: Appl'o'holics, MacLovers & Switchers 08027 >>> List-Post: 08027 >>> List-Subscribe: , 08027 >>> 08027 >>> List-Unsubscribe: , 08027 >>> 08027 >>> List-Archive: 08027 >>> List-Help: 08027 >>> Sender: apfelsucht-bounces@company.at 08027 >>> Errors-To: apfelsucht-bounces@company.at 08027 >>> 08027 >>> ENDOFTEST 08027 >>> 08027 >>> . 08027 <<< 250 2.1.5 Ok 08027 >>> QUIT 08027 <<< 221 2.0.0 bye Oct 31 14:54:10 tweak sm-mta[8027]: g9VDs9Nu008025: to=, delay=00:00:01, xdelay=00:00:01, mailer=local,pri=85157, relay=localhost, dsn=2.0.0, stat=Sent --- PLEASE SEND HELP! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:23 Message: Logged In: YES user_id=12800 Can you start by upgrading to Python 2.2.2? We need to eliminate any possibility that this is a problem that's been patched in the latest stable Python release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631569&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-640360 ] path relative URLs with /base vs /base/ Message-ID: Bugs item #640360, was opened at 2002-11-18 17:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640360&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: path relative URLs with /base vs /base/ Initial Comment: Our Apache server accepts path requests with or with a trailing slash, indifferently. (I understand there is no redirect.) This affects (cripples) relative paths, because http://host/mailman/private/name is the same page as http:// host/mailman/private/name/, but is different in reference to relative paths. The relative location of a month would be `href="name/2002-November/subject.html"' for the former, but `href="2002-November/subject.html"' for the latter. I suspect that the "private" URL is rarely entered by hand anyway, but FYI. /mailman/private/name/2002-November/ subject.html is OK, as far as I know. 2.1b4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640360&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-419992 ] bin/arch messed up existing web archive Message-ID: 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_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None >Priority: 7 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_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError Message-ID: Bugs item #635542, was opened at 2002-11-08 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught MMNoSuchUserError Initial Comment: I found an unsubscribe confirmation message in the shunt directory. The error log suggests that someone used both the web and the reply to unsubscribe, but when the email confirmation arrived, he was already gone and qrunner faulted. I'm running a CVS build about a week old. Here's the traceback: Nov 08 05:29:33 2002 (23820) Uncaught runner exception: Nov 08 05:29:33 2002 (23820) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 199, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 117, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1107, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/mailman/Mailman/MailList.py", line 936, in ApprovedDeleteMember raise Errors.MMNoSuchUserError MMNoSuchUserError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637410 ] autorespond_requests "w/discard" ignored Message-ID: Bugs item #637410, was opened at 2002-11-12 16:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) >Summary: autorespond_requests "w/discard" ignored Initial Comment: Gui/Autoresponse.py makes a distinction between autorespond_requests == 1 or == 2, but that's implemented in the MailCommandHandler.py module, which is unreferenced in b3 and gone in b4. CommandRunner._dispose could check for this after it calls Replybot.process(), I think. Or if the feature was intentionally left out, it could be left out of the web interface too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-616674 ] bin/arch not processing mbox import corr Message-ID: Bugs item #616674, was opened at 2002-09-30 13:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: fuzzy (fuzzynco) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch not processing mbox import corr Initial Comment: I needed to import an archive from yahoo!groups. a list formerly on Y!G is now on my server with MM2.1b3. After creating the mbox file with a perl script na dtesting it with pine (to make sure all the email is acuallu there), I tried to import it using arch. there are a few thousand emails in the file, but arch only finds 2? I posted to the mm users mailing list and got a reply from Larry Weeks, said to send him a copy of the file, and he tested it with bin/arch from 2.0.6 and it works as expected. since the mbox file is readable by pine, shouldn't arch handle it correctly? email me if i can provide any thing that would help diagnose the problem. thanks... fuzzy@pooh.asarian.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-629616 ] Invalid admin notification Message-ID: Bugs item #629616, was opened at 2002-10-27 19:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=629616&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Invalid admin notification Initial Comment: Using latest CVS (2.1b4). When someone subscribes through the web interface (listinfo page), the list admin will receive an invalid email if subscription notification has been turned on. The email contains the content of adminsubscribeack.txt, but no string interpolation is done. This is not the case if subscribing using the mail command interface or subscribed by the admin using the admin page. Also, if the subscribing user chooses a different language than the list language, the email notification sent to the admin will have a Subject: according to the list language, but body according to what the subscribing user chose. Which is probably not what we want... ;) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=629616&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-620033 ] gate_news should catch lost connection Message-ID: Bugs item #620033, was opened at 2002-10-07 22:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620033&group_id=103 Category: nntp/news Group: 2.1 beta Status: Open Resolution: Accepted >Priority: 7 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: gate_news should catch lost connection Initial Comment: Sep 20 10:51:35 2002 gate_news(9301): Traceback (most recent call last): Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 270, in ? Sep 20 10:51:35 2002 gate_news(9301): main() Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 250, in main Sep 20 10:51:35 2002 gate_news(9301): process_lists(lock) Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 194, in process_lists Sep 20 10:51:35 2002 gate_news(9301): conn, first, last = open_newsgroup(mlist) Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 89, in open_newsgroup Sep 20 10:51:35 2002 gate_news(9301): password=mm_cfg.NNTP_PASSWORD) Sep 20 10:51:35 2002 gate_news(9301): File "/usr/local/lib/python2.2/nntplib.py", line 117, in __init__ Sep 20 10:51:35 2002 gate_news(9301): self.welcome = self.getresp() Sep 20 10:51:35 2002 gate_news(9301): File "/usr/local/lib/python2.2/nntplib.py", line 203, in getresp Sep 20 10:51:35 2002 gate_news(9301): resp = self.getline() Sep 20 10:51:35 2002 gate_news(9301): File "/usr/local/lib/python2.2/nntplib.py", line 192, in getline Sep 20 10:51:35 2002 gate_news(9301): line = self.file.readline() Sep 20 10:51:35 2002 gate_news(9301): IOError : [Errno 131] Connection reset by peer ---------------------------------------------------------------------- Comment By: Ron Jarrell (jarrell) Date: 2002-10-22 11:19 Message: Logged In: YES user_id=34619 Didn't work... This comes up, btw, not during initial connection, but if the connection goes away during a gate_news run, like the daemon on the other end dies, or the news server reboots, etc. You get an IOerror on the mailman side. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-15 15:00 Message: Logged In: YES user_id=12800 I'm applying this patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-15 14:19 Message: Logged In: YES user_id=12800 I didn't realize that nntplib.NNTP() can raise an IOError -- I thought it would have been a socket.error. Oh well, here's an untested patch. I think I'll check this in just because I don't see how it could break anything. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620033&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-451475 ] header munging ruins threading Message-ID: Bugs item #451475, was opened at 2001-08-16 03:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_id=103 Category: nntp/news Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: CrackMonkey (monkeymaster) Assigned to: Barry A. Warsaw (bwarsaw) Summary: header munging ruins threading Initial Comment: The header hacking done by ToUsenet.py ruins threading in mail! It takes a perfectly good message ID, and throws it away! news replies to a mail message appear to be replies to the parent (since the news messag references contain the references of the parent + some crazy mailman message ID). This is bogus. At the very least, could you add the real message ID somewhere so that newsreaders will include it in the references headers? Some of us actually use threaded mailers, you know! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-12 12:16 Message: Logged In: YES user_id=12800 The problem is that many NNTP servers are really picky about message-id's; they won't allow duplicates, and they won't allow cross-postings with the same message-id. I suppose if the message had an id we could try to preserve it, attempt a post, and if that's rejected by the nntpd, we could try again with our own crafted message-id. I'm up for any suggestions that are rfc-compliant and work with the widest range of currently existing nntpds. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-219808 ] Missing dependancy for 'configure'. Message-ID: Bugs item #219808, was opened at 2000-10-30 17:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Thomas Wouters (twouters) Assigned to: Thomas Wouters (twouters) Summary: Missing dependancy for 'configure'. Initial Comment: The Mailman makefile is missing a dependancy on 'configure', so when 'configure' is updated, it isn't re-run automatically, and you aren't warned to reconfigure. (definately low-priority bug though :) (I also ran into something weird when running 'config.status' to do the reconfiguring for me... it set 'MAILMAN_UID' in Defaults.py to 'mailman', without quotes, instead of the numeric uid. That might be caused by a mix of an old config.status and a new configure, though, as I wasn't able to reproduce it on another box.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-630497 ] Traceback in error file Message-ID: Bugs item #630497, was opened at 2002-10-29 09:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Andy Carpenter (acarpenter) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in error file Initial Comment: Since I upgraded to 2.1b4, I have started to get the following tracebacks in the error log file. It is a characteristics of our busiest mail list that many of the posts come from the far east with unicode characters in their subject line. Oct 29 14:19:35 2002 (26533) Uncaught runner exception: ASCII decoding error: or dinal not in range(128) Oct 29 14:19:35 2002 (26533) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py" , line 129, in _dispo se status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py" , line 167, in _dopip eline mlist.BounceMessage(msg, msgdata, e) File "/usr/local/mailman/Mailman/Bouncer.py", line 273, in BounceMessage lang=self.preferred_language) File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:17 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644773 ] "description" doesn't get encoded Message-ID: Bugs item #644773, was opened at 2002-11-27 10:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) >Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-621597 ] list creation ignores DEFAULT_EMAIL_HOST Message-ID: Bugs item #621597, was opened at 2002-10-10 18:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621597&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: list creation ignores DEFAULT_EMAIL_HOST Initial Comment: If I set DEFAULT_EMAIL_HOST in mm_cfg.py, its value is ignored when creating a new list. It's pretty easy to see why: MailList.InitVars uses DEFAULT_HOST_NAME. But the two are only equal as long as mm_cfg.py is not used. If DEFAULT_HOST_NAME and DEFAULT_EMAIL_HOST are really supposed to be the same, perhaps DEFAULT_HOST_NAME should not be set in Defaults.py -- rather, any code that looks at DEFAULT_EMAIL_HOST should check to see if DEFAULT_HOST_NAME happens to be defined in mm_cfg, and use it if so. Or something like that. I'm happy to supply a patch if someone agrees that this is a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621597&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg. Message-ID: Bugs item #642996, was opened at 2002-11-24 02:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: can't send Plain Digest w/multipart msg. Initial Comment: cron/senddigests and cgi-bin/admin/digest can't send plain digest when multipart message(s) are contained. Note: Attached file will solve this problem for only cron/senddigests, but not for cgi. Traceback: admin(17454): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(17454): [----- Mailman Version: 2.1b5 -----] admin(17454): [----- Traceback ------] admin(17454): Traceback (most recent call last): admin(17454): File "/usr/local/mail/mailman/scripts/driver", line 87, in run_main admin(17454): main() admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 169, in main admin(17454): change_options(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 1229, in change_options admin(17454): gui.handleForm(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line 169, in handleForm admin(17454): self._setValue(mlist, property, val, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/Digest.py", line 148, in _setValue admin(17454): status = mlist.send_digest_now() admin(17454): File "/usr/local/mail/mailman/Mailman/Digester.py", line 60, in send_digest_now admin(17454): ToDigest.send_digests(self, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests admin(17454): send_i18n_digests(mlist, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 301, in send_i18n_digests admin(17454): g(msg, unixfrom=0) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 100, in flatten admin(17454): self._write(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 128, in _write admin(17454): self._dispatch(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 154, in _dispatch admin(17454): meth(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 212, in _handle_text admin(17454): raise TypeError, 'string payload expected: %s' % type(payload) admin(17454): TypeError: string payload expected: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-540978 ] List-* header multiline split bug Message-ID: Bugs item #540978, was opened at 2002-04-08 08:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Markus Mandalka (mandalka) Assigned to: Nobody/Anonymous (nobody) Summary: List-* header multiline split bug Initial Comment: I have a list antiatomforum@lists.kommunikationssystem.de and others with long names. It seems that mailman can not handle with such long names, because in the subscribe-mail (which you have to answer to be in the list) the first columns are some things from the header (unsubscribe: xxx@lists.xxx and so on). Whith names like atest@lists.kommunikationssystem.de it works. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 17:38 Message: Logged In: YES user_id=12800 Changing the summary ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-15 00:37 Message: Logged In: NO I just installed mailman and can confirm this bug as well. When the list address + hostname is too long (in my case the listname was north-texas-stovebolters- club@stovebolt.stovebolt.com -- 52 characters total) the headers overflow into the body of the message. The "break point" was at the List Subscribe line: ******************* This is header: List-Subscribe: , (total of 94 characters before the split) ******************* This is body List-Unsubscribe: , List-Archive: List-Help: Sender: north-texas-stovebolters-club- bounces@stovebolt.stovebolt.com Errors-To: north-texas-stovebolters-club- bounces@stovebolt.stovebolt.com ************************ This is the initial text of the message that was posted. I'm sure that I'll be there. :-) **************************** It looks like there's a line break or line limit that's causing the problem. Perhaps it's line 33: MAXLINELEN = 78 The first line that breaks (in my case) is a line that has 94 characters in the first part, none of which can be separated (no spaces or line breaks, just continuous text.) The very next line drops to the body. I believe giuans is correct that the problem is in the wrap section of the code, because the break occurs immediately after a comma, which, if I'm understanding the code correctly, is inserted by the program after an overlength line occurs, to split the line at 78 (or as close to that as it can get.) I think the correct fix would be to add the "h" portion subsequent to the split so that each line in the header would have the required semi-colon to indicate that it's header. If the MTA sees a line with no semicolon, it's going to think that it's body text, not header. ***************** Present code: if len(h) + 2 + len(v) > 78: v = CONTINUATION.join(v.split(', ')) msg[h] = v ****************** Possible fix if len(h) + 2 + len(v) > 78: v=CONTINUATION.join(h + v.split(',')) msg[h] = v or something like that. (I haven't worked with php, so I'm not familiar with its functions and syntax.) The idea is to split a line like this: Line exceeds 78 characters? h+v, h+ rest of v HTH. ---------------------------------------------------------------------- Comment By: Jean Millerat (drsigmund) Date: 2002-07-04 04:13 Message: Logged In: YES user_id=70686 I have reached the same bug with mailing list adresses such as <11 characters>@<30 characters> whereas <8 characters>@<30 characters> works properly. The effect of this bug is that the headers of the subcription annoucement or any further email from the list are "mangled" as was said on [mailman-developers]. As an example when one of the List-* header line is too long, it is broken in two parts (and the second part is indented). Since then, Outlook (and I suppose other email clients) think this second part of the broken header line is the beginning of the body of the message. Therefore the remaining headers are sent as part of the body of the message ! I think this bug does not only occur with too long email adresses but may occur with too long header lines whichever line it is (even with the Subject line especially when this subject line is very long because of quoted-printable characters). See [mailman-developers] for the description of maybe the same bug, in mails dealing with headers being "mangled". My current workarounds : - using short mailing list names. - and not sending quoted-printable characters within subject lines. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-02 10:27 Message: Logged In: YES user_id=531451 I've found it. A fast fix for is to comment lines 149-150 in Mailman/Handlers:/CookHeaders.py: --- CookHeaders.py 2002-05-02 14:51:36.000000000 +0200 +++ CookHeaders.py.new 2002-05-02 16:12:09.000000000 +0200 @@ -146,8 +146,8 @@ # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded, but is at least text-MUA friendly. The # adding of 2 is for the colon-space separator. - if len(h) + 2 + len(v) > 78: - v = CONTINUATION.join(v.split(', ')) +# if len(h) + 2 + len(v) > 78: +# v = CONTINUATION.join(v.split(', ')) msg[h] = v # Always delete List-Archive header, but only add it back if the list is # actually archiving Tested with Mailman 2.1b1, Source Mage GNU/Linux 2.4.18, Postfix 1.1.7. I know there should be a better way, but I'm not a Python programmer at all. :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-11 18:03 Message: Logged In: YES user_id=12800 I've confirmed this bug, but don't have a fix for it right now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses Message-ID: 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_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: Works For Me >Priority: 7 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" is resolved by pipermail as: listname@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@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: # 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 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@whereever.com displayed as "John Doe" whereas jdoe@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@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. ------------------------------------------------------------- [Philly_ambient] tool!

      [Philly_ambient] tool!

      Posted by . . . .. . . . on Mon Jun 3 23:17:02 2002 

      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

    • Previous message: [Philly_ambient] Noise Deafinitions and playlist
    • Next message: [Philly_ambient] Do you hear what I hear? (re: noise deaf)
    • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
      • --------------------------------------------------------------------- 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: Delivered-To: aharon@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@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 ; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn@aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for ; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn@aol.com Message-ID: To: philly_ambient@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@phobos.serve.com Errors-To: philly_ambient-admin@phobos.serve.com X-BeenThere: philly_ambient@phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient@phobos.serve.com List-Help: List-Post: List-Subscribe: , List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts List-Unsubscribe: , List-Archive: 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@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_id=103 From noreply@sourceforge.net Wed Nov 27 16:28:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:28:01 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color Message-ID: Bugs item #635462, was opened at 2002-11-08 07:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 Category: Web/CGI >Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Marcin Orlowski (carl-os) Assigned to: Nobody/Anonymous (nobody) Summary: Admin pages HTML does not set TEXT color Initial Comment: Mailman admin pages believe that TEXT color is always black and does not set it to, hoping nobody changes the defaults. And this is false assumption ;-) For testing purposes my defaults are black bg color and yellow text. And since admin pages sets bg to white it now exposes yellow fonts on white background here. Kinda unreadable. Solution -> fix template/css/whatever to set up text color to black. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:28:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:28:19 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-641564 ] quoted-printable in pipermail Message-ID: Bugs item #641564, was opened at 2002-11-20 18:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641564&group_id=103 Category: Pipermail >Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Thomas Krichel (thomaskrichel) Assigned to: Nobody/Anonymous (nobody) Summary: quoted-printable in pipermail Initial Comment: I am using version on debian 2.0.13-2. Some of my mail list owners send email with quoted- printable encoding. Such emails are distributed with the encoding stripped. In the ???.mbox/???.mbox file, a header that say that the message has quoted-printable encoding is present. After pipermail is run, in the .txt file, the encoding information header is no longer present, but the encoding is not decoded. This is annoying as some of many of our mails have urls. The urls fail to resolve because of the encoding. Best wishes, Thomas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641564&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:23:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:23:01 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631569 ] conn.quit() -> SMTPServerDisconnected Message-ID: Bugs item #631569, was opened at 2002-10-31 09:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631569&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 6 Submitted By: Denzel D'aviagio (uplink2sf) Assigned to: Nobody/Anonymous (nobody) Summary: conn.quit() -> SMTPServerDisconnected Initial Comment: well this is driving me insane. had it since 2.1b3 on RedHat 7.2 using python 2.2 (stock rpm install). there's a few lists active but mail gets delivered rarely - seems when sending mail, Mailman/Handlers/SMTPDirect.py fails to conn.quit() thus raising a SMTPServerDisconnected: please run connect() first ...weird! please find attached looots of logfiles that hopefully make sense to you. I have too little knowledge of python (<=0) to investigate more. --- root [tweak] # $(which python2) -v # /usr/lib/python2.2/site.pyc matches /usr/lib/python2.2/site.py import site # precompiled from /usr/lib/python2.2/site.pyc # /usr/lib/python2.2/os.pyc matches /usr/lib/python2.2/os.py import os # precompiled from /usr/lib/python2.2/os.pyc import posix # builtin # /usr/lib/python2.2/posixpath.pyc matches /usr/lib/python2.2/posixpath.py import posixpath # precompiled from /usr/lib/python2.2/posixpath.pyc # /usr/lib/python2.2/stat.pyc matches /usr/lib/python2.2/stat.py import stat # precompiled from /usr/lib/python2.2/stat.pyc # /usr/lib/python2.2/UserDict.pyc matches /usr/lib/python2.2/UserDict.py import UserDict # precompiled from /usr/lib/python2.2/UserDict.pyc Python 2.2 (#1, Apr 12 2002, 15:29:57) [GCC 2.96 20000731 (Red Hat Linux 7.2 2.96-109)] on linux2 Type "help", "copyright", "credits" or "license" for more information. dlopen("/usr/lib/python2.2/lib-dynload/readline.so", 2); import readline # dynamically loaded from /usr/lib/python2.2/lib-dynload/readline.so >>> --- the following logfile mix is obfuscated a bit (email and IP addresses) 08017 >>> 220 companyMail ESMTP 08017 <<< EHLO company.at 08017 >>> 250-mx.company.at Hello fqdn.domain.net [2.3.4.5], pleased to meet you 08017 >>> 250-ENHANCEDSTATUSCODES 08017 >>> 250-PIPELINING 08017 >>> 250-8BITMIME 08017 >>> 250-SIZE 08017 >>> 250-DSN 08017 >>> 250-ETRN 08017 >>> 250-AUTH DIGEST-MD5 CRAM-MD5 08017 >>> 250-STARTTLS 08017 >>> 250-DELIVERBY 08017 >>> 250 HELP 08017 <<< STARTTLS 08017 >>> 220 2.0.0 Ready to start TLS 08018 >>> 220 companyMail ESMTP 08018 <<< HELO company.at 08018 >>> 250 mx.company.at Hello fqdn.domain.net [2.3.4.5], pleased to meet you 08018 <<< MAIL FROM: 08018 >>> 250 2.1.0 ... Sender ok 08018 <<< RCPT TO: 08018 >>> 250 2.1.5 ... Recipient ok 08018 <<< DATA 08018 >>> 354 Enter mail, end with "." on a line by itself 08018 <<< Date: Thu, 31 Oct 2002 15:05:15 +0100 08018 <<< Mime-Version: 1.0 (Apple Message framework v546) 08018 <<< Content-Type: text/plain; charset=US-ASCII; format=flowed 08018 <<< Subject: test 08018 <<< From: SENDER REALNAME 08018 <<< To: apfelsucht@company.at 08018 <<< Content-Transfer-Encoding: 7bit 08018 <<< Message-Id: 08018 <<< X-Mailer: Apple Mail (2.546) 08018 <<< 08018 <<< ENDOFTEST 08018 <<< 08018 <<< . 08018 >>> 250 2.0.0 g9VDs6Nu008018 Message accepted for delivery 08018 <<< QUIT 08018 >>> 221 2.0.0 mx.company.at closing connection 08019 === EXEC smrsh -c /opt/mailman/current/mail/mailman post apfelsucht 08019 >>> From SENDER@DOMAIN.NET Thu Oct 31 14:54:06 2002 08019 >>> Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; Thu, 31 Oct 2002 14:54:06 +0100 08019 >>> Date: Thu, 31 Oct 2002 15:05:15 +0100 08019 >>> Mime-Version: 1.0 (Apple Message framework v546) 08019 >>> Content-Type: text/plain; charset=US-ASCII; format=flowed 08019 >>> Subject: test 08019 >>> From: SENDER REALNAME 08019 >>> To: apfelsucht@company.at 08019 >>> Content-Transfer-Encoding: 7bit 08019 >>> Message-Id: 08019 >>> X-Mailer: Apple Mail (2.546) 08019 >>> 08019 >>> ENDOFTEST 08019 >>> Oct 31 14:54:06 tweak sm-mta[8018]: g9VDs6Nu008018: from=, size=377, class=0, nrcpts=1, msgid=, proto=SMTP, daemon=MTA, relay=fqdn.domain.net [2.3.4.5] 08019 <<< [EOF] Oct 31 14:54:07 tweak sm-mta[8019]: g9VDs6Nu008018: to="|/opt/mailman/current/mail/mailman post apfelsucht", ctladdr= (47/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30568, dsn=2.0.0, stat=Sent connect: ('localhost', 25) connect: ('localhost', 25) reply: '220 companyMail ESMTP\r\n' reply: retcode (220); Msg: companyMail ESMTP connect: companyMail ESMTP send: 'ehlo tweak.company.at\r\n' reply: '250-mx.company.at Hello localhost [127.0.0.1], pleased to meet you\r\n' reply: '250-ENHANCEDSTATUSCODES\r\n' reply: '250-PIPELINING\r\n' reply: '250-8BITMIME\r\n' reply: '250-SIZE\r\n' reply: '250-DSN\r\n' reply: '250-ETRN\r\n' reply: '250-AUTH DIGEST-MD5 CRAM-MD5\r\n' reply: '250-STARTTLS\r\n' reply: '250-DELIVERBY\r\n' reply: '250 HELP\r\n' reply: retcode (250); Msg: mx.company.at Hello localhost [127.0.0.1], pleased to meet you ENHANCEDSTATUSCODES PIPELINING 8BITMIME SIZE DSN ETRN AUTH DIGEST-MD5 CRAM-MD5 STARTTLS DELIVERBY HELP send: 'mail FROM: size=1168\r\n' reply: '250 2.1.0 ... Sender ok\r\n' reply: retcode (250); Msg: 2.1.0 ... Sender ok send: 'rcpt TO:\r\n' reply: '250 2.1.5 ... Recipient ok\r\n' reply: retcode (250); Msg: 2.1.5 ... Recipient ok send: 'data\r\n' reply: '354 Enter mail, end with "." on a line by itself\r\n' reply: retcode (354); Msg: Enter mail, end with "." on a line by itself data: (354, 'Enter mail, end with "." on a line by itself') send: "Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at\r\n\t(company.at/20021013) with SMTP id g9VDs6Nu008018 for ;\r\n\tThu, 31 Oct 2002 14:54:06 +0100\r\nDate: Thu, 31 Oct 2002 15:05:15 +0100\r\nMime-Version: 1.0 (Apple Message framework v546)\r\nContent-Type: text/plain; charset=US-ASCII; format=flowed\r\nFrom: SENDER REALNAME \r\nTo: apfelsucht@company.at\r\nContent-Transfer-Encoding: 7bit\r\nMessage-Id: \r\nX-Mailer: Apple Mail (2.546)\r\nSubject: [Apfelsucht] test\r\nX-BeenThere: apfelsucht@company.at\r\nPrecedence: list\r\nList-Id: Appl'o'holics, MacLovers & Switchers \r\nList-Post: \r\nList-Subscribe: ,\r\n\t\r\nList-Unsubscribe: ,\r\n\t\r\nList-Archive: \r\nList-Help: \r\nSender: apfelsucht-bounces@company.at\r\nErrors-To: apfelsucht-bounces@company.at\r\n\r\nENDOFTEST\r\n\r\n.\r\n" reply: '250 2.0.0 g9VDs9Nu008025 Message accepted for delivery\r\n' reply: retcode (250); Msg: 2.0.0 g9VDs9Nu008025 Message accepted for delivery data: (250, '2.0.0 g9VDs9Nu008025 Message accepted for delivery') send: 'mail FROM: size=1168\r\n' reply: '250 2.1.0 ... Sender ok\r\n' reply: retcode (250); Msg: 2.1.0 ... Sender ok send: 'rcpt TO:\r\n' send: 'quit\r\n' send: 'quit\r\n' Oct 31 14:54:09 2002 (7608) All recipients refused: please run connect() first 08025 >>> 220 companyMail ESMTP 08025 <<< ehlo tweak.company.at 08025 >>> 250-mx.company.at Hello localhost [127.0.0.1], pleased to meet you 08025 >>> 250-ENHANCEDSTATUSCODES 08025 >>> 250-PIPELINING 08025 >>> 250-8BITMIME 08025 >>> 250-SIZE 08025 >>> 250-DSN 08025 >>> 250-ETRN 08025 >>> 250-AUTH DIGEST-MD5 CRAM-MD5 08025 >>> 250-STARTTLS 08025 >>> 250-DELIVERBY 08025 >>> 250 HELP 08025 <<< mail FROM: size=1168 08025 >>> 250 2.1.0 ... Sender ok 08025 <<< rcpt TO: 08025 >>> 250 2.1.5 ... Recipient ok 08025 <<< data 08025 >>> 354 Enter mail, end with "." on a line by itself 08025 <<< Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at 08025 <<< (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; 08025 <<< Thu, 31 Oct 2002 14:54:06 +0100 08025 <<< Date: Thu, 31 Oct 2002 15:05:15 +0100 08025 <<< Mime-Version: 1.0 (Apple Message framework v546) 08025 <<< Content-Type: text/plain; charset=US-ASCII; format=flowed 08025 <<< From: SENDER REALNAME 08025 <<< To: apfelsucht@company.at 08025 <<< Content-Transfer-Encoding: 7bit 08025 <<< Message-Id: 08025 <<< X-Mailer: Apple Mail (2.546) 08025 <<< Subject: [Apfelsucht] test 08025 <<< X-BeenThere: apfelsucht@company.at 08025 <<< Precedence: list 08025 <<< List-Id: Appl'o'holics, MacLovers & Switchers 08025 <<< List-Post: 08025 <<< List-Subscribe: , 08025 <<< 08025 <<< List-Unsubscribe: , 08025 <<< 08025 <<< List-Archive: 08025 <<< List-Help: 08025 <<< Sender: apfelsucht-bounces@company.at 08025 <<< Errors-To: apfelsucht-bounces@company.at 08025 <<< 08025 <<< ENDOFTEST 08025 <<< 08025 <<< . 08025 >>> 250 2.0.0 g9VDs9Nu008025 Message accepted for delivery 08027 === CONNECT localhost 08025 <<< mail FROM: size=1168 08025 >>> 250 2.1.0 ... Sender ok 08025 <<< rcpt TO: 08027 <<< 220 company.at LMTP company 20021003 ready 08027 >>> LHLO mx.company.at Oct 31 14:54:09 tweak sm-mta[8025]: g9VDs9Nu008025: from=, size=1168, class=-30, nrcpts=1, msgid=, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Oct 31 14:54:09 2002 (7608) Uncaught runner exception: please run connect() first Oct 31 14:54:09 2002 (7608) Traceback (most recent call last): File "/opt/mailman/current/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/current/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/current/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/opt/mailman/current/Mailman/Handlers/SMTPDirect.py", line 149, in process conn.quit() File "/opt/mailman/current/Mailman/Handlers/SMTPDirect.py", line 79, in quit self.__conn.quit() File "/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first 08027 <<< 250-company.at 08027 <<< 250-8BITMIME 08027 <<< 250-ENHANCEDSTATUSCODES 08027 <<< 250-PIPELINING 08027 <<< 250-SIZE 08027 <<< 250-AUTH EXTERNAL 08027 <<< 250 IGNOREQUOTA 08027 >>> MAIL From: SIZE=1168 08027 <<< 250 2.1.0 ok 08027 >>> RCPT To: 08027 >>> DATA 08027 <<< 250 2.1.5 ok 08027 <<< 354 go ahead 08027 >>> Return-Path: 08027 >>> Received: from tweak.company.at (localhost [127.0.0.1]) by mx.company.at (company.at/20021013) with ESMTP id g9VDs9Nu008025 for ; Thu, 31 Oct 2002 14:54:09 +0100 08027 >>> Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at 08027 >>> (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; 08027 >>> Thu, 31 Oct 2002 14:54:06 +0100 08027 >>> Date: Thu, 31 Oct 2002 15:05:15 +0100 08027 >>> Mime-Version: 1.0 (Apple Message framework v546) 08027 >>> Content-Type: text/plain; charset=US-ASCII; format=flowed 08027 >>> From: SENDER REALNAME 08027 >>> To: apfelsucht@company.at 08027 >>> Content-Transfer-Encoding: 7bit 08027 >>> Message-Id: 08027 >>> X-Mailer: Apple Mail (2.546) 08027 >>> Subject: [Apfelsucht] test 08027 >>> X-BeenThere: apfelsucht@company.at 08027 >>> Precedence: list 08027 >>> List-Id: Appl'o'holics, MacLovers & Switchers 08027 >>> List-Post: 08027 >>> List-Subscribe: , 08027 >>> 08027 >>> List-Unsubscribe: , 08027 >>> 08027 >>> List-Archive: 08027 >>> List-Help: 08027 >>> Sender: apfelsucht-bounces@company.at 08027 >>> Errors-To: apfelsucht-bounces@company.at 08027 >>> 08027 >>> ENDOFTEST 08027 >>> 08027 >>> . 08027 <<< 250 2.1.5 Ok 08027 >>> QUIT 08027 <<< 221 2.0.0 bye Oct 31 14:54:10 tweak sm-mta[8027]: g9VDs9Nu008025: to=, delay=00:00:01, xdelay=00:00:01, mailer=local,pri=85157, relay=localhost, dsn=2.0.0, stat=Sent --- PLEASE SEND HELP! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:23 Message: Logged In: YES user_id=12800 Can you start by upgrading to Python 2.2.2? We need to eliminate any possibility that this is a problem that's been patched in the latest stable Python release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631569&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:28:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:28:57 -0800 Subject: [Mailman-Developers] [ mailman-Feature Requests-604841 ] simulate bounce Message-ID: Feature Requests item #604841, was opened at 2002-09-04 21:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=604841&group_id=103 >Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Justin (returnthis) Assigned to: Nobody/Anonymous (nobody) Summary: simulate bounce Initial Comment: It would be great to add a "simulate invalid address" to the authorization page. e.g. along with the Defer/Accept/Reject/Discard options. This would simply send an invalid address message back to the sender. Usually used for spam emails with members only posting. Would greatly reduce spam as the invalid address would be removed by most automated spamming systems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=604841&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:40:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:40:04 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message header/body Message-ID: Patches item #644129, was opened at 2002-11-26 14:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Edit held message header/body Initial Comment: Here is my preliminary (brute force) patch to allow full editing of headers and bodies of messages being held for approval in Mailman 2.1 (as of beta 5). I have released versions of this for 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before releasing this one. You must set HOLD_MESSAGES_AS_PICKLES = 0 in your installation's mm_cfg.py for this to work. I may support pickles in a future version. Personally I don't see that much performance difference anyway, not on the held stuff... Also note that if you had HOLD_MESSAGES_AS_PICKLES = 1 (the default) when you created a list, you must recreate it after changing that variable. (Learned the hard way) This patch overrides the ADMINDB_PAGE_TEXT_LIMIT setting, so if you have megabyte messages being held, be ready to wait. Also - this version doesn't change the request database, so if you change the Subject: header you won't see the change reflected in the summary list (but it will be sent out your way when you Approve). Happy mailmanning! ---------------------------------------------------------------------- >Comment By: anser (anser) Date: 2002-11-27 16:40 Message: Logged In: YES user_id=49958 The problem with moving this to 2.2/3.0 is that I actually have no way of knowing whether it will work with 2.2/3.0 - it is based on 2.1. I actually don't expect this feature to ever be folder into "official" Mailman since editing the envelope is apparently considered heresy :) but I want the patch to be available for people who need it. Just so it stops moving so I can post the URL... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 14:04 Message: Logged In: YES user_id=12800 I'm moving this to the 2.2/3.0 group since we're in feature freeze for 2.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 From barry@python.org Wed Nov 27 16:42:22 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 27 Nov 2002 11:42:22 -0500 Subject: [Mailman-Developers] The plan for 2.1 Message-ID: <15844.62958.645219.294861@gargle.gargle.HOWL> I know I've been fairly quiet on these lists lately. More on that later. For now, I've done a bit of triage on the SF bug reports, and I hope to have some free time over the Thanksgiving holiday weekend, so my priority will be to nail as many bugs as possible, and get another beta out asap. It's likely that unless I screw up royally, that that will be the last beta. We need a period of time where the translators can do their final updates before the final release, and time's running short. Here's my self-imposed schedule: beta6: 02-Dec-2002 rc1: 09-Dec-2002 rc2: 16-Dec-2002 (if necessary) final: 23-Dec-2002 This gives me some Xmas slip time if there are critical last minute bugs. My intention is for translators to get their last updates in between rc1 and final (but don't wait if you have stuff ready!). I'll be very reluctant to change any templates or marked strings between rc1 and final. Cheers, and happy holidays, -Barry From noreply@sourceforge.net Wed Nov 27 16:44:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:44:43 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644129 ] Edit held message header/body Message-ID: Patches item #644129, was opened at 2002-11-26 09:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Edit held message header/body Initial Comment: Here is my preliminary (brute force) patch to allow full editing of headers and bodies of messages being held for approval in Mailman 2.1 (as of beta 5). I have released versions of this for 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before releasing this one. You must set HOLD_MESSAGES_AS_PICKLES = 0 in your installation's mm_cfg.py for this to work. I may support pickles in a future version. Personally I don't see that much performance difference anyway, not on the held stuff... Also note that if you had HOLD_MESSAGES_AS_PICKLES = 1 (the default) when you created a list, you must recreate it after changing that variable. (Learned the hard way) This patch overrides the ADMINDB_PAGE_TEXT_LIMIT setting, so if you have megabyte messages being held, be ready to wait. Also - this version doesn't change the request database, so if you change the Subject: header you won't see the change reflected in the summary list (but it will be sent out your way when you Approve). Happy mailmanning! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:44 Message: Logged In: YES user_id=12800 Don't worry, MM2.2/3.0 is currently a figment of my imagination. I just needed to do this for triage purposes, and I doubt any of the code involved will change radically before 2.1 final is out. We can move it back to the 2.1 group when that's done (SF doesn't give me enough classification options here unfortunately). ---------------------------------------------------------------------- Comment By: anser (anser) Date: 2002-11-27 11:40 Message: Logged In: YES user_id=49958 The problem with moving this to 2.2/3.0 is that I actually have no way of knowing whether it will work with 2.2/3.0 - it is based on 2.1. I actually don't expect this feature to ever be folder into "official" Mailman since editing the envelope is apparently considered heresy :) but I want the patch to be available for people who need it. Just so it stops moving so I can post the URL... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 09:04 Message: Logged In: YES user_id=12800 I'm moving this to the 2.2/3.0 group since we're in feature freeze for 2.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:20 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-621689 ] Subscribe requests dropped from admin db Message-ID: Bugs item #621689, was opened at 2002-10-10 23:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Subscribe requests dropped from admin db Initial Comment: Occasionally, subscribe requests (via the web page) to a list that requires moderator approval for subscriptions never make it to the admin db for that list. They are listed in the subscribe log file, but never show up on the admin db page. Log file entries look like this: Oct 10 18:43:43 2002 (31168) eventmasters: pending XXXXXX.swfla.rr.com But the admin db page for the list shows no outstanding issues. I have verified that there was an actual subscription request behind this log entry. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-11-22 01:08 Message: Logged In: YES user_id=598228 Unfortunately, it's still occurring under 2.1b4. I'll check it under 2.1b5 as soon as the patches for htdig integration are released, as I need those to implement. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-22 10:11 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1b4 goes out. I've fixed some related bugs in cvs, so hopefully this will be fixed in the new version. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-10-20 13:14 Message: Logged In: YES user_id=598228 Sorry - I'm running 2.1b3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-20 11:48 Message: Logged In: YES user_id=12800 What version of Mailman are you using. It's import to know the exact version, i.e. 2.1beta3, or if you're running from cvs. A lot of these problems have been fixed in cvs, which will soon be released as 2.1 beta 4. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-10-11 00:29 Message: Logged In: YES user_id=598228 I just verified, by cat'ing pending.pck, that the appropriate changes seem to be in there. But the web interface never picks them up. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:51 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:51 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:29:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:29:19 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:27:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:27:18 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-637494 ] typo in README.SENDMAIL (CVS 2.4) Message-ID: Bugs item #637494, was opened at 2002-11-12 19:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: typo in README.SENDMAIL (CVS 2.4) Initial Comment: The README.SENDMAIL section on INTEGRATION has a typo: ...such that Sendmail will automatically recognize and delivery I presume it must be without the "y" in "delivery". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:52:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:52:08 -0800 Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 11:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery >Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 11:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply@sourceforge.net Wed Nov 27 16:24:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 08:24:28 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro Message-ID: Bugs item #643762, was opened at 2002-11-25 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Duplicate Priority: 6 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:24 Message: Logged In: YES user_id=12800 This is a duplicate of 644294 ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2002-11-25 16:15 Message: Logged In: YES user_id=60479 Argh, please forget the comment about archiving... ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2002-11-25 15:58 Message: Logged In: YES user_id=60479 Uops, I forgot to say that archiving is broken. I do not know if this related to the reported error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_id=103 From Donal.Hunt2@mail.dcu.ie Wed Nov 27 18:44:26 2002 From: Donal.Hunt2@mail.dcu.ie (Donal Hunt) Date: Wed, 27 Nov 2002 18:44:26 +0000 Subject: [Mailman-Developers] possible bug [Digest Topic List] Message-ID: <3DE5128A.1D0C0A52@mail.dcu.ie> This is the layout I'm getting for Mailman-Developers digest at the moment (mailman-2.1b5)... Is it supposed to wrap like that? Regards Donal DCU -------------------------------------------------------------------------- Today's Topics: 1. [ mailman-Patches-644129 ] Edit held message header/body 2. [ mailman-Bugs-621689 ] Subscribe requests dropped from admin db 3. [ mailman-Patches-644810 ] Sendmail mailer in Python 4. [ mailman-Patches-644810 ] Sendmail mailer in Python 5. [ mailman-Bugs-637494 ] typo in README.SENDMAIL (CVS 2.4) 6. [ mailman-Patches-644810 ] Sendmail mailer in Python 7. [ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro From noreply@sourceforge.net Wed Nov 27 21:09:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 27 Nov 2002 13:09:21 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-644950 ] membership pages shows wrong subset Message-ID: Bugs item #644950, was opened at 2002-11-27 21:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644950&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: membership pages shows wrong subset Initial Comment: When first entering the membership admin tab, and the members of the list are displayed letterwise, I see the letter A bold/higlighted, but the member starting with "Z" are displayed. Selecting the subset again by selecting "A" shows the correct meber subset starting with "A". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644950&group_id=103 From sagi@boom.org.il Wed Nov 27 21:24:13 2002 From: sagi@boom.org.il (Sagi Bashari) Date: Wed, 27 Nov 2002 23:24:13 +0200 Subject: [Mailman-Developers] [Fwd: automating daily send to moderated list] In-Reply-To: <3DDB569D.5020604@boom.org.il> References: <3DDB569D.5020604@boom.org.il> <0fd801c2961e$2cf2f360$1e00a8c0@onsnet.org> Message-ID: <3DE537FD.5070902@boom.org.il> On 27/11/2002 16:06, Danny Terweij wrote: >Which version of mailman? > 2.0.13. But I'll upgrade if needed. > >mailman 2.1bx can do it. If i remember somthing with senders filters at the >web GUI interface. >Then you can enter a email adress that can send messages without aproving >it. > >Or just subscribe the email address which started the cronjob. > I can do that, but then - it's possible to fake the From header, no? I rather feed mailman directly without going through the MTA at all. Is that possible? I don't mind doing some hacking if I'll only get some pointers. Sagi > >Danny. > > >----- Original Message ----- >From: "Sagi Bashari" >To: >Sent: Wednesday, November 20, 2002 10:32 AM >Subject: [Mailman-Developers] [Fwd: automating daily send to moderated list] > > > > >>No answer on users list, forwarding to developers. >> >> >> > >Hello, > >I'm trying to set up a large mailing list (~80k subscribers) using mailman. > >It is a moderated list. I would like to automate send of a daily >newsletter to all the subscribers (by script that runs as a cronjob on >the same machine as mailman). However, I don't want to go and approve >the mail manually everyday. > >Is that possible? > >Sagi > > > From noreply@sourceforge.net Thu Nov 28 09:17:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 01:17:42 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-631569 ] conn.quit() -> SMTPServerDisconnected Message-ID: Bugs item #631569, was opened at 2002-10-31 15:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631569&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Denzel D'aviagio (uplink2sf) Assigned to: Nobody/Anonymous (nobody) Summary: conn.quit() -> SMTPServerDisconnected Initial Comment: well this is driving me insane. had it since 2.1b3 on RedHat 7.2 using python 2.2 (stock rpm install). there's a few lists active but mail gets delivered rarely - seems when sending mail, Mailman/Handlers/SMTPDirect.py fails to conn.quit() thus raising a SMTPServerDisconnected: please run connect() first ...weird! please find attached looots of logfiles that hopefully make sense to you. I have too little knowledge of python (<=0) to investigate more. --- root [tweak] # $(which python2) -v # /usr/lib/python2.2/site.pyc matches /usr/lib/python2.2/site.py import site # precompiled from /usr/lib/python2.2/site.pyc # /usr/lib/python2.2/os.pyc matches /usr/lib/python2.2/os.py import os # precompiled from /usr/lib/python2.2/os.pyc import posix # builtin # /usr/lib/python2.2/posixpath.pyc matches /usr/lib/python2.2/posixpath.py import posixpath # precompiled from /usr/lib/python2.2/posixpath.pyc # /usr/lib/python2.2/stat.pyc matches /usr/lib/python2.2/stat.py import stat # precompiled from /usr/lib/python2.2/stat.pyc # /usr/lib/python2.2/UserDict.pyc matches /usr/lib/python2.2/UserDict.py import UserDict # precompiled from /usr/lib/python2.2/UserDict.pyc Python 2.2 (#1, Apr 12 2002, 15:29:57) [GCC 2.96 20000731 (Red Hat Linux 7.2 2.96-109)] on linux2 Type "help", "copyright", "credits" or "license" for more information. dlopen("/usr/lib/python2.2/lib-dynload/readline.so", 2); import readline # dynamically loaded from /usr/lib/python2.2/lib-dynload/readline.so >>> --- the following logfile mix is obfuscated a bit (email and IP addresses) 08017 >>> 220 companyMail ESMTP 08017 <<< EHLO company.at 08017 >>> 250-mx.company.at Hello fqdn.domain.net [2.3.4.5], pleased to meet you 08017 >>> 250-ENHANCEDSTATUSCODES 08017 >>> 250-PIPELINING 08017 >>> 250-8BITMIME 08017 >>> 250-SIZE 08017 >>> 250-DSN 08017 >>> 250-ETRN 08017 >>> 250-AUTH DIGEST-MD5 CRAM-MD5 08017 >>> 250-STARTTLS 08017 >>> 250-DELIVERBY 08017 >>> 250 HELP 08017 <<< STARTTLS 08017 >>> 220 2.0.0 Ready to start TLS 08018 >>> 220 companyMail ESMTP 08018 <<< HELO company.at 08018 >>> 250 mx.company.at Hello fqdn.domain.net [2.3.4.5], pleased to meet you 08018 <<< MAIL FROM: 08018 >>> 250 2.1.0 ... Sender ok 08018 <<< RCPT TO: 08018 >>> 250 2.1.5 ... Recipient ok 08018 <<< DATA 08018 >>> 354 Enter mail, end with "." on a line by itself 08018 <<< Date: Thu, 31 Oct 2002 15:05:15 +0100 08018 <<< Mime-Version: 1.0 (Apple Message framework v546) 08018 <<< Content-Type: text/plain; charset=US-ASCII; format=flowed 08018 <<< Subject: test 08018 <<< From: SENDER REALNAME 08018 <<< To: apfelsucht@company.at 08018 <<< Content-Transfer-Encoding: 7bit 08018 <<< Message-Id: 08018 <<< X-Mailer: Apple Mail (2.546) 08018 <<< 08018 <<< ENDOFTEST 08018 <<< 08018 <<< . 08018 >>> 250 2.0.0 g9VDs6Nu008018 Message accepted for delivery 08018 <<< QUIT 08018 >>> 221 2.0.0 mx.company.at closing connection 08019 === EXEC smrsh -c /opt/mailman/current/mail/mailman post apfelsucht 08019 >>> From SENDER@DOMAIN.NET Thu Oct 31 14:54:06 2002 08019 >>> Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; Thu, 31 Oct 2002 14:54:06 +0100 08019 >>> Date: Thu, 31 Oct 2002 15:05:15 +0100 08019 >>> Mime-Version: 1.0 (Apple Message framework v546) 08019 >>> Content-Type: text/plain; charset=US-ASCII; format=flowed 08019 >>> Subject: test 08019 >>> From: SENDER REALNAME 08019 >>> To: apfelsucht@company.at 08019 >>> Content-Transfer-Encoding: 7bit 08019 >>> Message-Id: 08019 >>> X-Mailer: Apple Mail (2.546) 08019 >>> 08019 >>> ENDOFTEST 08019 >>> Oct 31 14:54:06 tweak sm-mta[8018]: g9VDs6Nu008018: from=, size=377, class=0, nrcpts=1, msgid=, proto=SMTP, daemon=MTA, relay=fqdn.domain.net [2.3.4.5] 08019 <<< [EOF] Oct 31 14:54:07 tweak sm-mta[8019]: g9VDs6Nu008018: to="|/opt/mailman/current/mail/mailman post apfelsucht", ctladdr= (47/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30568, dsn=2.0.0, stat=Sent connect: ('localhost', 25) connect: ('localhost', 25) reply: '220 companyMail ESMTP\r\n' reply: retcode (220); Msg: companyMail ESMTP connect: companyMail ESMTP send: 'ehlo tweak.company.at\r\n' reply: '250-mx.company.at Hello localhost [127.0.0.1], pleased to meet you\r\n' reply: '250-ENHANCEDSTATUSCODES\r\n' reply: '250-PIPELINING\r\n' reply: '250-8BITMIME\r\n' reply: '250-SIZE\r\n' reply: '250-DSN\r\n' reply: '250-ETRN\r\n' reply: '250-AUTH DIGEST-MD5 CRAM-MD5\r\n' reply: '250-STARTTLS\r\n' reply: '250-DELIVERBY\r\n' reply: '250 HELP\r\n' reply: retcode (250); Msg: mx.company.at Hello localhost [127.0.0.1], pleased to meet you ENHANCEDSTATUSCODES PIPELINING 8BITMIME SIZE DSN ETRN AUTH DIGEST-MD5 CRAM-MD5 STARTTLS DELIVERBY HELP send: 'mail FROM: size=1168\r\n' reply: '250 2.1.0 ... Sender ok\r\n' reply: retcode (250); Msg: 2.1.0 ... Sender ok send: 'rcpt TO:\r\n' reply: '250 2.1.5 ... Recipient ok\r\n' reply: retcode (250); Msg: 2.1.5 ... Recipient ok send: 'data\r\n' reply: '354 Enter mail, end with "." on a line by itself\r\n' reply: retcode (354); Msg: Enter mail, end with "." on a line by itself data: (354, 'Enter mail, end with "." on a line by itself') send: "Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at\r\n\t(company.at/20021013) with SMTP id g9VDs6Nu008018 for ;\r\n\tThu, 31 Oct 2002 14:54:06 +0100\r\nDate: Thu, 31 Oct 2002 15:05:15 +0100\r\nMime-Version: 1.0 (Apple Message framework v546)\r\nContent-Type: text/plain; charset=US-ASCII; format=flowed\r\nFrom: SENDER REALNAME \r\nTo: apfelsucht@company.at\r\nContent-Transfer-Encoding: 7bit\r\nMessage-Id: \r\nX-Mailer: Apple Mail (2.546)\r\nSubject: [Apfelsucht] test\r\nX-BeenThere: apfelsucht@company.at\r\nPrecedence: list\r\nList-Id: Appl'o'holics, MacLovers & Switchers \r\nList-Post: \r\nList-Subscribe: ,\r\n\t\r\nList-Unsubscribe: ,\r\n\t\r\nList-Archive: \r\nList-Help: \r\nSender: apfelsucht-bounces@company.at\r\nErrors-To: apfelsucht-bounces@company.at\r\n\r\nENDOFTEST\r\n\r\n.\r\n" reply: '250 2.0.0 g9VDs9Nu008025 Message accepted for delivery\r\n' reply: retcode (250); Msg: 2.0.0 g9VDs9Nu008025 Message accepted for delivery data: (250, '2.0.0 g9VDs9Nu008025 Message accepted for delivery') send: 'mail FROM: size=1168\r\n' reply: '250 2.1.0 ... Sender ok\r\n' reply: retcode (250); Msg: 2.1.0 ... Sender ok send: 'rcpt TO:\r\n' send: 'quit\r\n' send: 'quit\r\n' Oct 31 14:54:09 2002 (7608) All recipients refused: please run connect() first 08025 >>> 220 companyMail ESMTP 08025 <<< ehlo tweak.company.at 08025 >>> 250-mx.company.at Hello localhost [127.0.0.1], pleased to meet you 08025 >>> 250-ENHANCEDSTATUSCODES 08025 >>> 250-PIPELINING 08025 >>> 250-8BITMIME 08025 >>> 250-SIZE 08025 >>> 250-DSN 08025 >>> 250-ETRN 08025 >>> 250-AUTH DIGEST-MD5 CRAM-MD5 08025 >>> 250-STARTTLS 08025 >>> 250-DELIVERBY 08025 >>> 250 HELP 08025 <<< mail FROM: size=1168 08025 >>> 250 2.1.0 ... Sender ok 08025 <<< rcpt TO: 08025 >>> 250 2.1.5 ... Recipient ok 08025 <<< data 08025 >>> 354 Enter mail, end with "." on a line by itself 08025 <<< Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at 08025 <<< (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; 08025 <<< Thu, 31 Oct 2002 14:54:06 +0100 08025 <<< Date: Thu, 31 Oct 2002 15:05:15 +0100 08025 <<< Mime-Version: 1.0 (Apple Message framework v546) 08025 <<< Content-Type: text/plain; charset=US-ASCII; format=flowed 08025 <<< From: SENDER REALNAME 08025 <<< To: apfelsucht@company.at 08025 <<< Content-Transfer-Encoding: 7bit 08025 <<< Message-Id: 08025 <<< X-Mailer: Apple Mail (2.546) 08025 <<< Subject: [Apfelsucht] test 08025 <<< X-BeenThere: apfelsucht@company.at 08025 <<< Precedence: list 08025 <<< List-Id: Appl'o'holics, MacLovers & Switchers 08025 <<< List-Post: 08025 <<< List-Subscribe: , 08025 <<< 08025 <<< List-Unsubscribe: , 08025 <<< 08025 <<< List-Archive: 08025 <<< List-Help: 08025 <<< Sender: apfelsucht-bounces@company.at 08025 <<< Errors-To: apfelsucht-bounces@company.at 08025 <<< 08025 <<< ENDOFTEST 08025 <<< 08025 <<< . 08025 >>> 250 2.0.0 g9VDs9Nu008025 Message accepted for delivery 08027 === CONNECT localhost 08025 <<< mail FROM: size=1168 08025 >>> 250 2.1.0 ... Sender ok 08025 <<< rcpt TO: 08027 <<< 220 company.at LMTP company 20021003 ready 08027 >>> LHLO mx.company.at Oct 31 14:54:09 tweak sm-mta[8025]: g9VDs9Nu008025: from=, size=1168, class=-30, nrcpts=1, msgid=, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Oct 31 14:54:09 2002 (7608) Uncaught runner exception: please run connect() first Oct 31 14:54:09 2002 (7608) Traceback (most recent call last): File "/opt/mailman/current/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/current/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/current/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/opt/mailman/current/Mailman/Handlers/SMTPDirect.py", line 149, in process conn.quit() File "/opt/mailman/current/Mailman/Handlers/SMTPDirect.py", line 79, in quit self.__conn.quit() File "/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first 08027 <<< 250-company.at 08027 <<< 250-8BITMIME 08027 <<< 250-ENHANCEDSTATUSCODES 08027 <<< 250-PIPELINING 08027 <<< 250-SIZE 08027 <<< 250-AUTH EXTERNAL 08027 <<< 250 IGNOREQUOTA 08027 >>> MAIL From: SIZE=1168 08027 <<< 250 2.1.0 ok 08027 >>> RCPT To: 08027 >>> DATA 08027 <<< 250 2.1.5 ok 08027 <<< 354 go ahead 08027 >>> Return-Path: 08027 >>> Received: from tweak.company.at (localhost [127.0.0.1]) by mx.company.at (company.at/20021013) with ESMTP id g9VDs9Nu008025 for ; Thu, 31 Oct 2002 14:54:09 +0100 08027 >>> Received: from company.at (fqdn.domain.net [2.3.4.5]) by mx.company.at 08027 >>> (company.at/20021013) with SMTP id g9VDs6Nu008018 for ; 08027 >>> Thu, 31 Oct 2002 14:54:06 +0100 08027 >>> Date: Thu, 31 Oct 2002 15:05:15 +0100 08027 >>> Mime-Version: 1.0 (Apple Message framework v546) 08027 >>> Content-Type: text/plain; charset=US-ASCII; format=flowed 08027 >>> From: SENDER REALNAME 08027 >>> To: apfelsucht@company.at 08027 >>> Content-Transfer-Encoding: 7bit 08027 >>> Message-Id: 08027 >>> X-Mailer: Apple Mail (2.546) 08027 >>> Subject: [Apfelsucht] test 08027 >>> X-BeenThere: apfelsucht@company.at 08027 >>> Precedence: list 08027 >>> List-Id: Appl'o'holics, MacLovers & Switchers 08027 >>> List-Post: 08027 >>> List-Subscribe: , 08027 >>> 08027 >>> List-Unsubscribe: , 08027 >>> 08027 >>> List-Archive: 08027 >>> List-Help: 08027 >>> Sender: apfelsucht-bounces@company.at 08027 >>> Errors-To: apfelsucht-bounces@company.at 08027 >>> 08027 >>> ENDOFTEST 08027 >>> 08027 >>> . 08027 <<< 250 2.1.5 Ok 08027 >>> QUIT 08027 <<< 221 2.0.0 bye Oct 31 14:54:10 tweak sm-mta[8027]: g9VDs9Nu008025: to=, delay=00:00:01, xdelay=00:00:01, mailer=local,pri=85157, relay=localhost, dsn=2.0.0, stat=Sent --- PLEASE SEND HELP! ---------------------------------------------------------------------- >Comment By: Denzel D'aviagio (uplink2sf) Date: 2002-11-28 10:17 Message: Logged In: YES user_id=639746 Thanks - weird, but doing a clean wipe-old compile-new python 2.2.2 did the trick. without *any* other changes, everything's working like a charme. heads up! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 17:23 Message: Logged In: YES user_id=12800 Can you start by upgrading to Python 2.2.2? We need to eliminate any possibility that this is a problem that's been patched in the latest stable Python release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631569&group_id=103 From noreply@sourceforge.net Thu Nov 28 13:36:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 05:36:50 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-645273 ] SSL bugs 2.1b5 Message-ID: Bugs item #645273, was opened at 2002-11-28 13:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645273&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: SSL bugs 2.1b5 Initial Comment: I'm trying to run 2.1b5 under SSL. Much of mailman appears to work except that links in several places still have "http" instead of "https" and also don't have my special port number that I am using. The broken links appear to be using my DEFAULT_EMAIL_HOST which of course is just 'mydomain.com' rather than DEFAULT_URL_HOST combined with DEFAULT_URL_PATTERN. Some of the links that are broken include: Password section The link to the general options section Membership management section All the alphabetical quick access tab links "Click here for legend to table" link Administrative requests (this page is unusable) First "mailing list" link on page "More detailed instructions" link "View the details" of all held postings link All links to individual held postings "view all messages from ..." link Submit link General list information page Private archive link Go to list archives link My mm_cfg.py file contains: DEFAULT_URL_HOST = 'main.mydomain.com' DEFAULT_EMAIL_HOST = 'mydomain.com' DEFAULT_URL_PATTERN = 'https://% s:1234/mailman/' PUBLIC_ARCHIVE_URL = 'https://%(hostname)s:1234/pipermail/%(listname) s' PRIVATE_ARCHIVE_URL = 'https://%(hostname)s:1234/pipermail/%(listname) s' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) MTA = 'Postfix' IMAGE_LOGOS = '/icons/' DEFAULT_ARCHIVE_PROVATE = 1 SMTP_MAX_RCPTS = 1 SMTP_MAX_SESSIONS_PER_CONNECTION = 0 VERP_PERSONALIZED_DELIVERIES = 1 VERP_DELIVERY_INTERVAL = 1 VERP_PASSWORD_REMINDERS = 1 VERP_CONFIRMATIONS = 1 DEFAULT_ADMIN_MEMBER_CHUNKSIZE = 100 ADMINDB_PAGE_TEXT_LIMIT = 10000 OWNERS_CAN_ENABLE_PERSONALIZATION = 1 DEFAULT_DEFAULT_MEMBER_MODERATION = 1 DEFAULT_GENERIC_NONMEMBER_ACTION = 1 DEFAULT_ADMIN_IMMED_NOTIFY = 0 DEFAULT_SEND_REMINDERS = 0 DEFAULT_SUBSCRIBE_POLICY = 0 ALLOW_OPEN_SUBSCRIBE = 1 DEFAULT_PRIVATE_ROSTER = 2 DEFAULT_BOUNCE_INFO_STALE_AFTER = days(60) DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS = 1 DEFAULT_BOUNCE_UNRECOGNIZED_GOES_TO_LIST_ OWNER = 0 DEFAULT_BOUNCE_NOTIFY_OWNER_ON_DISABLE = 0 DEFAULT_BOUNCE_NOTIFY_OWNER_ON_REMOVAL = 0 DELIVERY_RETRY_PERIOD = days(1) DEFAULT_MAX_NUM_RECIPIENTS = 1000000 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645273&group_id=103 From noreply@sourceforge.net Thu Nov 28 14:38:44 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 06:38:44 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-645273 ] SSL bugs 2.1b5 Message-ID: Bugs item #645273, was opened at 2002-11-28 13:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645273&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed Resolution: None Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: SSL bugs 2.1b5 Initial Comment: I'm trying to run 2.1b5 under SSL. Much of mailman appears to work except that links in several places still have "http" instead of "https" and also don't have my special port number that I am using. The broken links appear to be using my DEFAULT_EMAIL_HOST which of course is just 'mydomain.com' rather than DEFAULT_URL_HOST combined with DEFAULT_URL_PATTERN. Some of the links that are broken include: Password section The link to the general options section Membership management section All the alphabetical quick access tab links "Click here for legend to table" link Administrative requests (this page is unusable) First "mailing list" link on page "More detailed instructions" link "View the details" of all held postings link All links to individual held postings "view all messages from ..." link Submit link General list information page Private archive link Go to list archives link My mm_cfg.py file contains: DEFAULT_URL_HOST = 'main.mydomain.com' DEFAULT_EMAIL_HOST = 'mydomain.com' DEFAULT_URL_PATTERN = 'https://% s:1234/mailman/' PUBLIC_ARCHIVE_URL = 'https://%(hostname)s:1234/pipermail/%(listname) s' PRIVATE_ARCHIVE_URL = 'https://%(hostname)s:1234/pipermail/%(listname) s' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) MTA = 'Postfix' IMAGE_LOGOS = '/icons/' DEFAULT_ARCHIVE_PROVATE = 1 SMTP_MAX_RCPTS = 1 SMTP_MAX_SESSIONS_PER_CONNECTION = 0 VERP_PERSONALIZED_DELIVERIES = 1 VERP_DELIVERY_INTERVAL = 1 VERP_PASSWORD_REMINDERS = 1 VERP_CONFIRMATIONS = 1 DEFAULT_ADMIN_MEMBER_CHUNKSIZE = 100 ADMINDB_PAGE_TEXT_LIMIT = 10000 OWNERS_CAN_ENABLE_PERSONALIZATION = 1 DEFAULT_DEFAULT_MEMBER_MODERATION = 1 DEFAULT_GENERIC_NONMEMBER_ACTION = 1 DEFAULT_ADMIN_IMMED_NOTIFY = 0 DEFAULT_SEND_REMINDERS = 0 DEFAULT_SUBSCRIBE_POLICY = 0 ALLOW_OPEN_SUBSCRIBE = 1 DEFAULT_PRIVATE_ROSTER = 2 DEFAULT_BOUNCE_INFO_STALE_AFTER = days(60) DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS = 1 DEFAULT_BOUNCE_UNRECOGNIZED_GOES_TO_LIST_ OWNER = 0 DEFAULT_BOUNCE_NOTIFY_OWNER_ON_DISABLE = 0 DEFAULT_BOUNCE_NOTIFY_OWNER_ON_REMOVAL = 0 DELIVERY_RETRY_PERIOD = days(1) DEFAULT_MAX_NUM_RECIPIENTS = 1000000 ---------------------------------------------------------------------- >Comment By: John Distler (jd_waverly) Date: 2002-11-28 14:38 Message: Logged In: YES user_id=305936 Minutes after submitting this I noticed the comments in an earlier bug report: bin/withlist -l -r fix_url mailman fixed the issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645273&group_id=103 From noreply@sourceforge.net Thu Nov 28 14:54:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 06:54:37 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645297 ] Add PGP support Message-ID: Patches item #645297, was opened at 2002-11-28 14:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ben Laurie (benl) Assigned to: Nobody/Anonymous (nobody) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 From fil@rezo.net Thu Nov 28 19:39:52 2002 From: fil@rezo.net (Fil) Date: Thu, 28 Nov 2002 20:39:52 +0100 Subject: [Mailman-Developers] a unicode bug Message-ID: <20021128193952.GB28004@rezo.net> My Mailman system is almost up to date with CVS, and I get this daily. ----- Forwarded message from Cron Daemon ----- Date: Thu, 28 Nov 2002 08:00:05 +0100 (CET) From: root@miel.brainstorm.fr (Cron Daemon) To: mailman@miel.brainstorm.fr Subject: Cron /usr/local/bin/python -S /usr/local/mailman/cron/checkdbs Traceback (most recent call last): File "/usr/local/mailman/cron/checkdbs", line 136, in ? main() File "/usr/local/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/usr/local/mailman/cron/checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) ----- End forwarded message ----- -- Fil From lists@konfido.de Thu Nov 28 20:03:38 2002 From: lists@konfido.de (Matthias Juchem) Date: Thu, 28 Nov 2002 21:03:38 +0100 Subject: [Mailman-Developers] Howto submit patches? Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hi. I'm wondering how I should submit a patch. There is a patch manager on sf.net, but apparently without possibily to add a patch, at least for people who are not registered for the project. So is sending them to mailman-developers@python.org the best way? Regards, Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iQEVAwUBPeZ2oGPlwoKwhRFhAQFVWgf+JZgZKFWWBLenEaQiNrdODG0DBBZRBkRu cxKWkWELqeksn9ictsPUMBft0CoWHQHXWlZmokOozByM9nfe1xIPserxdnCaqCTr Zmy0QhzEczS/eFZyMTF45ofPDqSJwss3FIf8owQJOFVo9rMWrnjEmynWr5IgzrEu 57QfBHy/AkRy7pcQYppBjyQPnpbWp03i7XP2lDLGgeh69QYkvFheNO6RLNA6Faw8 o9diXKAWytdr3tKcVQXdy5SQcBoaJd985mxIEpHm9FSBpjyTNZsUpVM2DVMB2GYC pXZuXGOwg71TFz44P3eQORmsvFbeXnttixisLgyZ3pNz7ZqcKpOsuw== =VhJ8 -----END PGP SIGNATURE----- From marc_news@merlins.org Thu Nov 28 20:27:14 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Thu, 28 Nov 2002 12:27:14 -0800 Subject: [Mailman-Developers] Howto submit patches? In-Reply-To: References: Message-ID: <20021128202714.GK26333@merlins.org> On Thu, Nov 28, 2002 at 09:03:38PM +0100, Matthias Juchem wrote: > There is a patch manager on sf.net, but apparently without possibily to add a > patch, at least for people who are not registered for the project. Mmmh, anyone with an account on sf.net can submit patches. I'm not a registered developer of mailman on sf.net, and was able to submit patches nonetheless. However, if you don't have an sf.net account, then yes, you are out of luck, but seriously, it doesn't take long to set one up, and so far, OSDN has been really good at keeping your info private (except if you get your users.sf.net address harvested by some spammer obviously) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From lists@konfido.de Thu Nov 28 20:44:36 2002 From: lists@konfido.de (Matthias Juchem) Date: Thu, 28 Nov 2002 21:44:36 +0100 Subject: [Mailman-Developers] Howto submit patches? In-Reply-To: <20021128202714.GK26333@merlins.org> References: <20021128202714.GK26333@merlins.org> Message-ID: On Thursday, 28. November 2002 21:27, Marc MERLIN wrote: > On Thu, Nov 28, 2002 at 09:03:38PM +0100, Matthias Juchem wrote: > > There is a patch manager on sf.net, but apparently without possibily to > > add a patch, at least for people who are not registered for the project. > > Mmmh, anyone with an account on sf.net can submit patches. > I'm not a registered developer of mailman on sf.net, and was able to > submit patches nonetheless. Well, I do have an account. I had a look at the 'Patches' page, but there where only the two links 'Browse' and 'Admin'; don't know why, maybe some browser problem with cookies. But it seems to work now... Thank you. Matthias From noreply@sourceforge.net Thu Nov 28 20:50:13 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 12:50:13 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645421 ] Remove all Makefiles on make distclean Message-ID: Patches item #645421, was opened at 2002-11-28 21:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645421&group_id=103 Category: configure/install Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Remove all Makefiles on make distclean Initial Comment: mailman/messages/Makefile and mailman/tests/*/Makefile do not get cleaned up when doing a 'make distclean'. This should patch fix it. Tested like this: 'configure --some-options; make distclean'; seems to work ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645421&group_id=103 From noreply@sourceforge.net Thu Nov 28 20:52:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 12:52:55 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645422 ] $prefix hardcoded in qmail-to-mailman.py Message-ID: Patches item #645422, was opened at 2002-11-28 21:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645422&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: $prefix hardcoded in qmail-to-mailman.py Initial Comment: This patch replaces the hardcoded $prefix in contrib/qmail-to-mailman.py with @prefix@, which is replaced with $prefix during configure. Tested, works for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645422&group_id=103 From noreply@sourceforge.net Thu Nov 28 21:20:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 13:20:56 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645431 ] Filter spam on message body Message-ID: Patches item #645431, was opened at 2002-11-28 21:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645431&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Filter spam on message body Initial Comment: This patch adds a matching spam check for body content. It works exactly like the header check, except the message body (after base64/quoted-printable decoding) is scanned. You will need to remove and re-add any lists that you want to use this feature on after installing it. Make sure you get a new Defaults.py as well. The patch is pretty clean. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645431&group_id=103 From noreply@sourceforge.net Thu Nov 28 22:12:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 14:12:36 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-645453 ] Admin msg handoffs lead to error Message-ID: Bugs item #645453, was opened at 2002-11-28 15:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645453&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Joe R. Doupnik (jdoupnik) Assigned to: Nobody/Anonymous (nobody) Summary: Admin msg handoffs lead to error Initial Comment: Mailman 2.1b5 on FreeBSD 4.7-RELEASE. Admin, dealing with held msgs about list unsubscribes and administrativia. Choosing to copy the msg to admin leads to Mailman error in cPickle.load. error log snippet follows: Nov 27 11:38:55 2002 admin(6788): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(6788): [----- Mailman Version: 2.1b5 -----] admin(6788): [----- Traceback ------] admin(6788): Traceback (most recent call last): admin(6788): File "/usr/local/mailman/scripts/driver", line 87, in run_main admin(6788): main() admin(6788): File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 146, in ma in admin(6788): heldmsg_confirm(mlist, doc, cookie) admin(6788): File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 583, in he ldmsg_confirm admin(6788): ign, sender, msgsubject, ign, ign, ign = mlist.GetRecord(id) admin(6788): File "/usr/local/mailman/Mailman/ListAdmin.py", line 164, in GetR ecord admin(6788): type, data = self.__db[id] admin(6788): KeyError: 2 admin(6788): [----- Python Information -----] admin(6788): sys.version = 2.2.1 (#1, Oct 5 2002, 11:19:44) [GCC 2.95.4 20020320 [FreeBSD]] admin(6788): sys.executable = /usr/local/bin/python admin(6788): sys.prefix = /usr/local admin(6788): sys.exec_prefix = /usr/local admin(6788): sys.path = /usr/local admin(6788): sys.platform = freebsd4 admin(6788): [----- Environment Variables -----] admin(6788): PATH_INFO: /testlist admin(6788): CONTENT_LENGTH: 69 admin(6788): CONTENT_TYPE: application/x-www-form-urlencoded admin(6788): HTTP_COOKIE: novell+admin=2802000000699610e53d7328000 blahblah338666363313565643533303331; testli st+admin=280200000blahmoreblah335383730643 362326433343364393663343438643837633163 admin(6788): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/confirm admin(6788): PYTHONPATH: /usr/local/mailman admin(6788): SERVER_SOFTWARE: Apache etc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645453&group_id=103 From noreply@sourceforge.net Fri Nov 29 02:58:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 28 Nov 2002 18:58:29 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler Message-ID: Patches item #645513, was opened at 2002-11-29 15:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 From noreply@sourceforge.net Fri Nov 29 14:27:15 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 29 Nov 2002 06:27:15 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-645712 ] Moderation interface: unpredictable orde Message-ID: Bugs item #645712, was opened at 2002-11-29 09:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645712&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: Moderation interface: unpredictable orde Initial Comment: Messages in the moderation interface are shown in a non-obvious order. Oh wait, I see, it's sorted by the sender's email address. Hmmm. Messages should be shown in the order received (IMHO). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645712&group_id=103 From noreply@sourceforge.net Fri Nov 29 14:38:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 29 Nov 2002 06:38:07 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-645712 ] Moderation interface: unpredictable order Message-ID: Bugs item #645712, was opened at 2002-11-29 09:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645712&group_id=103 Category: Web/CGI Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) >Summary: Moderation interface: unpredictable order Initial Comment: Messages in the moderation interface are shown in a non-obvious order. Oh wait, I see, it's sorted by the sender's email address. Hmmm. Messages should be shown in the order received (IMHO). ---------------------------------------------------------------------- >Comment By: Greg Ward (gward) Date: 2002-11-29 09:38 Message: Logged In: YES user_id=14422 Oops, never mind -- I missed the link to the old MM 2.0 style moderation interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645712&group_id=103 From noreply@sourceforge.net Fri Nov 29 18:21:51 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 29 Nov 2002 10:21:51 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645787 ] loaddb - reverses dumpdb Message-ID: Patches item #645787, was opened at 2002-11-29 18:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645787&group_id=103 Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: loaddb - reverses dumpdb Initial Comment: Here is a new script, 'loaddb', which reverses the effect of dumpdb. Pretty-printed output from dumpdb is read from stdin and written to either a marshal (.db) or pickle (.pck) depending on your choice of filename and switches. i.e. You need two files: the loaddb script itself which goes in 'mailman/bin' - and the loaddb_patch file, which modifies configure.in and bin/Makefile.in to automatically install loaddb with the other scripts. After installing the script and patch, you will need to rerun 'configure' and 'make install.' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645787&group_id=103 From marc_news@merlins.org Fri Nov 29 22:00:56 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Fri, 29 Nov 2002 14:00:56 -0800 Subject: [Mailman-Developers] Uncaught bounce notification Message-ID: <20021129215937.GE3803@merlins.org> So, unless I'm missing something, if you use VERP, you should be able to process any bounce from a subscriber. Is it desirable for mailman to pass on a VERP bounce coming from a held message notification sent to a non subscriber? Would it make sense for mailman if it receives a bounce that is obviously verped and that there is no such member, to just drop it silently (maybe with a log entry)? Marc ----- Forwarded message from mailman-owner-bounces@svlug.org ----- From: mailman-owner-bounces@svlug.org To: web-team-owner@svlug.org X-List-Administrivia: yes Subject: Uncaught bounce notification X-Spam-Status: No, hits=0.4 required=7.0 tests=NO_REAL_NAME,SPAM_PHRASE_05_08 version=2.41 X-Spam-Level: X-SA-Exim-Scanned: Yes The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: http://lists.svlug.org/lists/admin/web-team/bounce X-Failed-Recipients: webmillionaire@yahoo.com From: Mail Delivery System To: web-team-bounces+webmillionaire=yahoo.com@svlug.org Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software (Exim). 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: webmillionaire@yahoo.com SMTP error from remote mailer after end of data: host mx2.mail.yahoo.com [64.157.4.82]: 554 delivery error: dd This user doesn't have a yahoo.com account (webmillionaire@yahoo.com) - mta408.mail.yahoo.com ------ This is a copy of the message, including all the headers. ------ Return-path: Received: from localhost ([127.0.0.1]:47928 helo=svlug.svlug.org) by svlug.org with esmtp (Exim 4.04 #161 (Debian)) id 18Ht44-000496-00 for ; Fri, 29 Nov 2002 13:52:48 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Your message to web-team awaits moderator approval From: web-team-bounces@svlug.org To: webmillionaire@yahoo.com Message-ID: Date: Fri, 29 Nov 2002 13:52:46 -0800 Precedence: bulk X-BeenThere: web-team@lists.svlug.org X-Mailman-Version: 2.1b5+ List-Id: these are the folks that keep our website running X-List-Administrivia: yes Sender: web-team-bounces+webmillionaire=yahoo.com@svlug.org Errors-To: web-team-bounces+webmillionaire=yahoo.com@lists.svlug.org Your mail to 'web-team' with the subject SPAM: 07.50: Heating Oil Is being held until the list moderator can review it for approval. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://lists.svlug.org/lists/confirm/web-team/80bfe91a670188b1f2a66538643b01882b468cfb ----- End forwarded message ----- -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Fri Nov 29 22:25:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 29 Nov 2002 14:25:53 -0800 Subject: [Mailman-Developers] [ mailman-Patches-645875 ] Spam filter test against all headers Message-ID: Patches item #645875, was opened at 2002-11-29 22:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645875&group_id=103 Category: list administration Group: None Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Spam filter test against all headers Initial Comment: Sometimes I need to watch for a particular phrase, email address, or other string in ANY header of a submitted message, not just one or two selected headers. This patch extends the syntax of the bounce_matching_headers field so that saying *: anystring will match 'anystring' in ANY message header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645875&group_id=103 From noreply@sourceforge.net Sat Nov 30 00:52:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 29 Nov 2002 16:52:52 -0800 Subject: [Mailman-Developers] [ mailman-Bugs-645906 ] User supplied HTML with % kills index.ht Message-ID: Bugs item #645906, was opened at 2002-11-29 17:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Joe R. Doupnik (jdoupnik) Assigned to: Nobody/Anonymous (nobody) Summary: User supplied HTML with % kills index.ht Initial Comment: Mailman 2.1b5. Edit archtoc.html or listinfo.html, include table with phrase width=100% and find that the list's archive overall index.html page is unformed (present but the various MM items are left as bare %(foobar)s style). After wasting a whole day on this the problem boils down to that percent sign in user-supplied HTML. It kills the high level index.html file. We don''t know about this until a full list archive operation is performed, because at the end the code creates the new index.html from the template files. Ugh. Likely some parser deep in the system is overreacting to the percent symbol. Needs fixing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_id=103 From danny@terweij.nl Sat Nov 30 01:16:34 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 30 Nov 2002 02:16:34 +0100 Subject: [Mailman-Developers] Uncaught bounce notification References: <20021129215937.GE3803@merlins.org> Message-ID: <01e301c2980e$1fc8e9a0$1e00a8c0@onsnet.org> From: "Marc MERLIN" > So, unless I'm missing something, if you use VERP, you should be able to > process any bounce from a subscriber. > Is it desirable for mailman to pass on a VERP bounce coming from a held > message notification sent to a non subscriber? > Would it make sense for mailman if it receives a bounce that is > obviously verped and that there is no such member, to just drop it > silently (maybe with a log entry)? I did reported it 2 times. Since CVS 2.1b4 this is happening. My listowners are getting also this emails if a destination usermailbox has a qouta exeeded. Very irritating emails :) So indeed stop it and my list owners are happy. Some lists i did put off the bounce checkings. Danny From danny@terweij.nl Sat Nov 30 01:21:11 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 30 Nov 2002 02:21:11 +0100 Subject: [Mailman-Developers] [ mailman-Bugs-645906 ] User supplied HTML with % kills index.ht References: Message-ID: <01ee01c2980e$c4e4faa0$1e00a8c0@onsnet.org> > Submitted By: Joe R. Doupnik (jdoupnik) > Assigned to: Nobody/Anonymous (nobody) > Summary: User supplied HTML with % kills index.ht > > Initial Comment: > Mailman 2.1b5. Edit archtoc.html or listinfo.html, > include table with phrase width=100% and find > that the list's archive overall index.html page is > unformed (present but the various MM items > are left as bare %(foobar)s style). [cut] > Likely some parser deep in the system is > overreacting to the percent symbol. Needs > fixing. I did report this also long time ago. (2.1b1 orso) I did create nice tables but indeed the %(xxx)s showed up instead of the value. I hope it will now be fixed! then i can create nice templates :) Danny From pioppo@ferrara.linux.it Sat Nov 30 14:16:11 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Sat, 30 Nov 2002 15:16:11 +0100 Subject: [Mailman-Developers] [ mailman-Bugs-645906 ] User supplied HTML with % kills index.ht In-Reply-To: <01ee01c2980e$c4e4faa0$1e00a8c0@onsnet.org> References: <01ee01c2980e$c4e4faa0$1e00a8c0@onsnet.org> Message-ID: <20021130141611.GF7523@ferrara.linux.it> On Sat, Nov 30, 2002 at 02:21:11AM +0100, Danny Terweij wrote: > > Mailman 2.1b5. Edit archtoc.html or listinfo.html, > > include table with phrase width=100% and find > > that the list's archive overall index.html page is width=100% is bad html. you should use width="100%", or better put this information on a CSS stylesheet. > > unformed (present but the various MM items are left as bare > > %(foobar)s style). this is bad too, but remember the GIGO rule... -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From Prakash.Subramanian at nsc.com Thu Nov 28 07:49:58 2002 From: Prakash.Subramanian at nsc.com (Prakash Subramanian) Date: Wed, 27 Nov 2002 23:49:58 -0800 Subject: [Mailman-Developers] MHonArc integration Message-ID: <3DE5CAA6.60109@nsc.com> I am trying to use a simple method to include MHonArc archiver enabled with monthly archive functionality. I found your script that does, but I am not sure how to use it. I tried replacing ~mailman/Mailman/Archiver/HyperArch.py with your MHonArc.py but it gives the following error message. ~mailman/bin/arch mylist Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 43, in ? from Mailman.Archiver.HyperArch import HyperArchive, Article ImportError: cannot import name Article The method Article is been used by various script and I am not able to get rid of this . Please advice on how to use your script. Another question, why Many thanks in advance. Prakash