Mailman 3 May 2002 - Mailman-Developers

bin/arch and large mbox
by Jon Parise May 23, 2002

May 23, 2002

I'm in the process of integrating a large set of old ezmlm archives with my existing Mailman archives. After converting the ezmlm archives to mbox format, I've been merging the archives together into a single listname.mbox file and then running bin/arch to rebuild the indexes. Everything has been going well until I hit a large mbox archive (~11MB). bin/arch only gets through the first 200 or so messages before it decides to finish up. This leaves me with only three weeks of archive indexes (from the year 2000, at that). The bin/arch usage text alludes to bin/arch having issues with large mbox'es, and it seems as though I'm experiencing one of them. =) Something like "bin/arch -s 0 -e 500 listname" doesn't seem to help. Any thoughts on how to proceed? -- Jon Parise (jon(a)csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member

1 0

[ mailman-Bugs-558848 ] Upgrade to 2.0.11 breaks admindb page
by noreply＠sourceforge.net May 23, 2002

May 23, 2002

Bugs item #558848, was opened at 2002-05-21 16:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id… Category: configuring/installing Group: 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: nathan hruby (nhruby) Assigned to: Nobody/Anonymous (nobody) Summary: Upgrade to 2.0.11 breaks admindb page Initial Comment: Hey, just upgraded to 2.0.11 from 2.0.5. Upgraded by applying the patches (in correct order :) to go from 2.0.5 to .2.0.22. All patches applied cleanly to the 2.0.5 source with no errors. reran the config.guess and re-ran make install, everything went off without a hitch, after restarting sendmail, httpd and cron after the upgrade procedure and checking the test list the admindb webpage dies with an error. All other pages work fine. Here's the traceback: May 21 16:32:19 2002 admin(9971): @@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ admin(9971): [----- Mailman Version: 2.0.11 -----] admin(9971): [----- Traceback ------] admin(9971): Traceback (innermost last): admin(9971): File "/home/mailman/scripts/driver", line 96, in run_main admin(9971): main() admin(9971): File "/home/mailman/Mailman/Cgi/ admindb.py", line 110, in main admin(9971): if len(cgidata.keys()): admin(9971): NameError: cgidata admin(9971): [----- Python Information -----] admin(9971): sys.version = 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] admin(9971): sys.executable = /usr/bin/python admin(9971): sys.prefix = /usr admin(9971): sys.exec_prefix= /usr admin(9971): sys.path = /usr admin(9971): sys.platform = linux-i386 admin(9971): [----- Environment Variables -----] admin(9971): DOCUMENT_ROOT: /var/www/html admin(9971): SERVER_ADDR: 128.192.51.21 admin(9971): QUERY_STRING: admin(9971): SERVER_PORT: 80 admin(9971): PATH_TRANSLATED: /var/www/html/ testlist admin(9971): REMOTE_ADDR: 128.192.51.220 admin(9971): HTTP_UA_OS: MacOS admin(9971): HTTP_ACCEPT_LANGUAGE: en admin(9971): GATEWAY_INTERFACE: CGI/1.1 admin(9971): SERVER_NAME: nuttybar.drama.uga.edu admin(9971): HTTP_CONNECTION: Keep-Alive admin(9971): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC) admin(9971): HTTP_ACCEPT: */* admin(9971): REQUEST_URI: /mailman/admindb/ testlist admin(9971): HTTP_UA_CPU: PPC admin(9971): HTTP_EXTENSION: Security/Remote- Passphrase admin(9971): SCRIPT_FILENAME: /home/mailman/ cgi-bin/admindb admin(9971): PATH_INFO: /testlist admin(9971): HTTP_HOST: nuttybar.drama.uga.edu admin(9971): REQUEST_METHOD: GET admin(9971): SERVER_SIGNATURE: <ADDRESS> Apache/1.3.14 Server at nuttybar.drama.uga.edu Port 80</ADDRESS> admin(9971): SCRIPT_NAME: /mailman/admindb admin(9971): SERVER_ADMIN: root@localhost admin(9971): SERVER_SOFTWARE: Apache/1.3.14 (Unix) (Red-Hat/Linux) admin(9971): PYTHONPATH: /home/mailman admin(9971): HTTP_COOKIE: testlist:admin= 280200000069c3aeea3c73280000003034623331306 1396165613462396165353062636 633393934393139363738333237323539303864 admin(9971): SERVER_PROTOCOL: HTTP/1.1 admin(9971): REMOTE_PORT: 56839 admin(9971): HTTP_REFERER: http:// nuttybar.drama.uga.edu/mailman/admin/testlist ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-23 11:56 Message: Logged In: YES user_id=12800 I just looked at the 2.0.4 -> 2.0.5 patch and it looks okay to me. That's the patch that should contain the fixed indentation for those lines. Hmm... ---------------------------------------------------------------------- Comment By: nathan hruby (nhruby) Date: 2002-05-21 16:56 Message: Logged In: YES user_id=19736 Damn you're quick :) Fixed by moving the following block of code starting at line 110 in mailman/Cgi/admindb.py over 5 spaces to the left... --- CUT_N_PASTE cgidata = cgi.FieldStorage() try: Auth.authenticate(mlist, cgidata) except Auth.NotLoggedInError, e: Auth.loginpage(mlist, 'admindb', e.message) return -- CUT_N_PASTE perhaps there is something screwy with the patches in the downlaod manager? ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:41 Message: Logged In: YES user_id=12800 Please compare the Mailman/Cgi/admindb.py file against the file at the top of the 2.0 maintainence branch: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/mailman/mailman/M… It sounds like there was a problem with the upgrade or the install after upgrade (I know you didn't get any errors, but still, I can't see why this exception would otherwise happen!) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id…

1 0

Python and Mailman problem
by Kory Wheatley May 23, 2002

May 23, 2002

Critical trying to run Python 2.1 on my production mailman 2.0.11 Univeristy Mailing Lists. I had to revert back to Python1.5.2 Does Python 2.1 work with Mailman 2.0.11. Details & and error messages below. Does anyone know the solution of this problem below? I've install mailman 2.0.11 on Red Hat 7.2 and it was working fine until I upgrade to Python 2.1. Once I upgraded to this version everything seemed fine for 5 hours. I was able to receive messages from my mailing lists at our University. The Web Interface administrator options for the lists all worked fine. Then messages started piling in "qfiles" and it would not send anymore messages out. I moved them out of the queue and started moving them back in one at a time and then again the messages seemed to be sent properly, but then they started piling back up in the qfiles directory again . Here is the errors I received in the "error" logfile. I'm not totally efficient on Python yet, so I would like some help I would appreciate it. (Quite a few messages on CORRUPTED ARCHIVES and module regex not found) ERROR LOG FILE May 21 10:20:01 2002 (31161) CORRUPT ARCHIVE FOR LIST: libstaff May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: relief May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: ultimate May 21 10:22:01 2002 qrunner(31203): Traceback (most recent call last): May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:22:01 2002 qrunner(31203): import HyperArch May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:22:01 2002 qrunner(31203): from Mailman import EncWord May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:22:01 2002 qrunner(31203): import base64 May 21 10:22:01 2002 qrunner(31203): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:22:01 2002 qrunner(31203): import binascii May 21 10:22:01 2002 qrunner(31203): ImportError: No module named binascii May 21 10:22:01 2002 (31203) CORRUPT ARCHIVE FOR LIST: korymail May 21 10:28:01 2002 qrunner(31258): Traceback (most recent call last): May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:28:01 2002 qrunner(31258): import HyperArch May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:28:01 2002 qrunner(31258): from Mailman import EncWord May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:28:01 2002 qrunner(31258): import base64 May 21 10:28:01 2002 qrunner(31258): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:28:01 2002 qrunner(31258): import binascii May 21 10:28:01 2002 qrunner(31258): ImportError: No module named binascii 3:26:01 2002 qrunner(32122): Traceback (most recent call last): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 283, in ? May 21 13:26:01 2002 qrunner(32122): kids = main(lock) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 253, in main May 21 13:26:01 2002 qrunner(32122): keepqueued = dispose_message(mlist, msg, msgdata) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 121, in dispose_message May 21 13:26:01 2002 qrunner(32122): if BouncerAPI.ScanMessages(mlist, mimemsg): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 57, in ScanMessages May 21 13:26:01 2002 qrunner(32122): mod = __import__('Mailman.Bouncers.'+modname) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/Catchall.py", line 34, in ? May 21 13:26:01 2002 qrunner(32122): import regsub May 21 13:26:01 2002 qrunner(32122): File "/usr/lib/python2.1/regsub.py", line 20, in ? May 21 13:26:01 2002 qrunner(32122): import regex May 21 13:26:01 2002 qrunner(32122): ImportError : No module named regex Kory Wheatley Idaho State University

2 1

[ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo
by noreply＠sourceforge.net May 23, 2002

May 23, 2002

Bugs item #558633, was opened at 2002-05-21 08:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:47 Message: Logged In: YES user_id=12800 Heh, I think this is a general problem when you get two email robots talking to each other! In MM2.1cvs the robot will refuse to respond to a message marked Precedence: bulk|junk|list -- but it looks like that wouldn't have even helped in this case (since the Majordomo server isnt' setting that header ;/ ) The only other solution I can think of is to add a config variable which is a blacklist of known addresses (regexps) that Mailman should not respond too. You'd still get into the robot infloop the first time, but at least you'd have a hope of avoiding subsequent replybot storms for the same address. ---------------------------------------------------------------------- Comment By: Nigel Metheringham (nigel) Date: 2002-05-21 08:03 Message: Logged In: YES user_id=31288 and other file ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id…

5 11

[ mailman-Bugs-559558 ] can't make moderated list unmoderated
by noreply＠sourceforge.net May 23, 2002

May 23, 2002

Bugs item #559558, was opened at 2002-05-23 10:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id… Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Geer (beroul) Assigned to: Nobody/Anonymous (nobody) Summary: can't make moderated list unmoderated Initial Comment: With Mailman 2.0.8, I made a list moderated (by setting "Must posts be approved by an administrator?" in Privacy Options) to "Yes". A few weeks later, I changed my mind and set this to "No". However, whenever someone tries to post to the list, I still receive a message from Mailman, saying that the posting requires approval (the subject line says "Posting to a restricted list by sender requires approval"). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id…

1 0

[ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
by noreply＠sourceforge.net May 23, 2002

May 23, 2002

Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) 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-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: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id…

1 0

[ mailman-Patches-444879 ] Archive indexer control to improve index
by noreply＠sourceforge.net May 23, 2002

May 23, 2002

Patches item #444879, was opened at 2001-07-26 18:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) 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-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: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id…

1 0

[ mailman-Bugs-559417 ] "arch" utility spews output
by noreply＠sourceforge.net May 22, 2002

May 22, 2002

Bugs item #559417, was opened at 2002-05-22 16:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559417&group_id… Category: Pipermail Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Ian Clarke (sanity) Assigned to: Nobody/Anonymous (nobody) Summary: "arch" utility spews output Initial Comment: When I run the "arch" utility to rebuild my archives, it prints out loads of "figuring article archives", which is somewhat confusing to the new user. Would it be possible to have a more sensible status report so that people aren't confused when they rebuild a large archive? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559417&group_id…

1 0

[ mailman-Bugs-558909 ] Auto-responsder doesn't send response.
by noreply＠sourceforge.net May 22, 2002

May 22, 2002

Bugs item #558909, was opened at 2002-05-21 18:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id… Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Donal Hunt (redgiant) Assigned to: Nobody/Anonymous (nobody) Summary: Auto-responsder doesn't send response. Initial Comment: Auto-response mail never gets sent on -admin and -owner addresses. Set the autorespond_admin and autorespond_admin_text properties on the auto-responder page of the admin page for the list. Sending mail to either <listname>-admin@host or <listname>-owner@host results in the admin receiving the email but no auto-response is sent to the sender. Found on Mailman CVS (May 9th). Up to my eyes at present so haven't got a chance to dig deeper yet. Will do so middle of next week if needed. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-22 19:51 Message: Logged In: YES user_id=12800 Fixed in cvs. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id…

1 0

Re: [Mailman-Developers] Another stupid question
by J C Lawrence May 22, 2002

May 22, 2002

On Wed, 22 May 2002 15:02:31 -0400 Jay R Ashworth <jra(a)baylink.com> wrote: > On Wed, May 22, 2002 at 11:11:39AM -0700, J C Lawrence wrote: >> On Wed, 22 May 2002 13:22:53 -0400 Jay R Ashworth <jra(a)baylink.com> >> wrote: > It would appear not. Sending mail from the Mailman machine using mutt > sends messages with the headers just as they might be expected to be. Which demonstrates nothing except that you have mutt well configured. Do the tests I outlined and it will reveal how your MTA handles unqualified and fully qualified From: headers. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0