Mailman 3 October 2002 - Mailman-Developers

[ mailman-Bugs-631200 ] qrunner in loop, keeps eating memory
by noreply＠sourceforge.net 30 Oct '02

30 Oct '02

Bugs item #631200, was opened at 2002-10-30 17:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631200&group_i… Category: command line scripts Group: 2.0.x Status: Open Resolution: None Priority: 5 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 "<string>", 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_i…

1 0

[ mailman-Bugs-631186 ] Postfix msg.type
by noreply＠sourceforge.net 30 Oct '02

30 Oct '02

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_i… Category: bounce detection Group: 2.0.x Status: Open Resolution: None Priority: 5 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_i…

1 0

Problem with checkdbs script in Beta 4
by Miller Brett 30 Oct '02

30 Oct '02

Hello, I just upgraded to Mailman beta 4 from beta 3 and I am receiving this error when a mailman cron job runs. Has anyone seen this error and does anyone know how to fix it. This checkdbs script seemed to work fine in beta 3 but not beta 4. Could someone tell me what this function does? Thank you for your time. Traceback (most recent call last): File "/usr/local/mailman/cron/checkdbs", line 26, in ? from email.Charset import Charset ImportError: No module named email.Charset Brett Miller Booz | Allen | Hamilton

2 1

No archive updates b4+
by Danny Terweij 30 Oct '02

30 Oct '02

Hi, b4+ does not update the archives with new messages (pipermail). My /qfiles/archives directory is filled with a lot of messages. Looks like that the Archrunner is not working. Danny Terweij

2 3

Re: [Mailman-Developers] No archive updates b4+
by Daniel Buchmann 30 Oct '02

30 Oct '02

It can't be a general b4+ problem, because my 2.1b4+ installation doesn't have this problem, neither does python.org... (look at the mailman-developers archive.. your latest messages are in it... ;) Danny wrote: > Hi, > > b4+ does not update the archives with new messages (pipermail). > > My /qfiles/archives directory is filled with a lot of messages. > > Looks like that the Archrunner is not working. > > Danny Terweij -Daniel, norwegian translator

2 1

strange things
by Danny Terweij 30 Oct '02

30 Oct '02

Still the bounce messages are not solved in latest cvs version. Oct 30 13:40:59 2002 (18497) forwarding unrecognized, message-id: <0a72d5740121ea2NET014S(a)hetnet.nl> Oct 30 13:43:34 2002 (18497) foreverfriends: miss.aqua(a)uku.co.uk already scored a bounce for today Oct 30 14:31:37 2002 (18497) foreverfriends: miss.aqua(a)uku.co.uk already scored a bounce for today Oct 30 14:33:56 2002 (18497) bounce message with non-members of psp-club-plaatjes-enzo: tm485569(a)mint.xo.nl Oct 30 14:33:57 2002 (18497) forwarding unrecognized, message-id: <20021030133219.E8C5754CA(a)mint.nl.gxn.net> Oct 30 14:36:08 2002 (18497) bounce message with non-members of psp-club-plaatjes-enzo: tm485569(a)mint.xo.nl Oct 30 14:36:09 2002 (18497) forwarding unrecognized, message-id: <20021030133439.2FFD1531B(a)mint.nl.gxn.net> Oct 30 14:36:11 2002 (18497) bounce message with non-members of psp-club-plaatjes-enzo: tm485569(a)mint.xo.nl Oct 30 14:36:11 2002 (18497) forwarding unrecognized, message-id: <20021030133446.6F3A553FD(a)mint.nl.gxn.net> Oct 30 14:37:42 2002 (18497) bounce message with non-members of psp-club: jahens(a)hetnet.nl And i have al lot of : Oct 30 15:26:34 2002 (1604) psp-club: couldn't get list lock And many of these : Oct 30 12:38:27 2002 (18499) 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 _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 57, in process prefix_subject(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 235, in prefix_subject s = unicode(s, codec, 'replace') LookupError: unknown encoding Oct 30 14:44:56 2002 (18496) Uncaught runner exception: <LockFile 137086212: /usr/local/mailman/locks/foreverfri ends.lock [unlocked: 18000sec] pid=18496>: None Oct 30 14:45:00 2002 (18496) 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/ArchRunner.py", line 74, in _dispose mlist.Save() File "/usr/local/mailman/Mailman/MailList.py", line 508, in Save self.__lock.refresh() File "/usr/local/mailman/Mailman/LockFile.py", line 223, in refresh raise NotLockedError, '%s: %s' % (repr(self), self.__read()) NotLockedError: <LockFile 137086212: /usr/local/mailman/locks/foreverfriends.lock [unlocked: 18000sec] pid=18496 >: None Take a look at it please, my users are getting angry :) ( i do not mind they know it is a beta version hehe) Danny Terweij

1 0

[ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
by noreply＠sourceforge.net 30 Oct '02

30 Oct '02

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_i… Category: None Group: None Status: Open Resolution: None Priority: 7 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 <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> ---------------------------------------------------------------------- >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_i…

1 0

[ mailman-Patches-444879 ] Archive indexer control to improve index
by noreply＠sourceforge.net 30 Oct '02

30 Oct '02

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_i… Category: None Group: None Status: Open Resolution: None Priority: 7 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 <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> 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 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_i…

1 0

[ mailman-Patches-444879 ] Archive indexer control to improve index
by noreply＠sourceforge.net 30 Oct '02

30 Oct '02

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_i… Category: None Group: None Status: Open Resolution: None Priority: 7 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 <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> 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 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_i…

1 0

B4 changed the To: line?
by Danny Terweij 30 Oct '02

30 Oct '02

Hi all, I do not know if this is the same as discussed now on the users list about "List Id". But all my users from all lists are complaining since i upgraded to B4/B4+ . The Short list description is placed at every outgoing mail at the TO: field. If the short list desciption is: "Welcome at this fine list" (You can see this at the /listinfo/ web page) Then all mail looks like this: >From : Danny Terweij To: Welcome at this fine list How to stop this or how to get back what it was before B4 version? Danny Terweij.

1 0