From castro@usmatrix.net Thu Apr 1 04:23:33 1999 From: castro@usmatrix.net (Edgard Castro) Date: Wed, 31 Mar 1999 23:23:33 -0500 Subject: [Mailman-Developers] Re: [Mailman-checkins] CVS: mailman/Mailman Deliverer.py In-Reply-To: <199903311923.OAA08292@anthem.cnri.reston.va.us>; from Barry A. Warsaw on Wed, Mar 31, 1999 at 02:23:14PM -0500 References: <199903311923.OAA08292@anthem.cnri.reston.va.us> Message-ID: <19990331232333.A4242@usmatrix.net> On Wed, Mar 31, 1999 at 02:23:14PM -0500, Barry A. Warsaw wrote: > Modified Files: > Deliverer.py > Log Message: > DeliverToList(): Strip off any duplicate Sender: headers, leaving just > the one pointing to the list-admin. The same problems occurs with Errors-To, haven't checked agains other headers. e. -- Edgard Castro | 305-273-5003 -o) Chief Network Engineer - U.S. Matrix Internet, Inc. /\\ Linux Counter User #29078 -- http://counter.li.org _\_V From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Apr 2 20:56:26 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 2 Apr 1999 15:56:26 -0500 (EST) Subject: [Mailman-Developers] Usenet gating and archiving Message-ID: <14085.12026.294121.877453@anthem.cnri.reston.va.us> Is anybody currently gating Usenet to a mailing list, /and/ doing archiving with the default Pipermail? If so, you may not have noticed that the archives are pretty broken; nothing that originates on Usenet will show up in the archive. I believe I understand why this is happening, and although I don't have a fix yet, it shouldn't be too difficult. I should be able to get it into 1.0b11. The problem occurs because Pipermail uses Python's mailbox.UnixMailbox objects which expect "From " separators. Message that originate on Usenet don't have these envelopes. The patch should be to simply synthesize these on messages gated off the newsgroup. However, there's a more severe breakage. You've actually lost information that is hard to reproduce because the flat listname.mbox files don't have the separators in them either. Running bin/arch over the file will give you even more corrupt archives (the incremental archiver just throws the Usenet messages away; bin/arch will tack them onto the last email-originated message). What you could do is to trek through the listname.mbox file looking for Newsgroup: headers (which appear, but I don't think are guaranteed, to be the first header in the message). When you find one, you jam in a synthesized "From " envelope. I would rather not add this hack to Mailman unless a lot of people would benefit from it. For the test lists that I'm running, we're willing to just trash the archives and start over; the lists aren't live anyway. I'd like to know who would be really adversely affected by this problem. Thanks, -Barry From rpyne@kinfolk.org Fri Apr 2 22:53:53 1999 From: rpyne@kinfolk.org (Richard B. Pyne) Date: Fri, 2 Apr 1999 15:53:53 -0700 Subject: [Mailman-Developers] Re: [Mailman-Users] Usenet gating and archiving In-Reply-To: <14085.12026.294121.877453@anthem.cnri.reston.va.us> Message-ID: <199904022253.PAA03119@ns.kinfolk.org> On 2 Apr 99, at 15:56, Barry A. Warsaw wrote: > Is anybody currently gating Usenet to a mailing list, /and/ doing > archiving with the default Pipermail? If so, you may not have noticed > that the archives are pretty broken; nothing that originates on Usenet > will show up in the archive. I have not yet started using the gateway, but it and the automated archives are two of the features that attracted me to mailman. I do plan on using it in the future. > I would rather not add this hack to Mailman unless a lot of people > would benefit from it. For the test lists that I'm running, we're > willing to just trash the archives and start over; the lists aren't > live anyway. I'd like to know who would be really adversely affected > by this problem. What good is an incomplete archive? I feel that it is very important that the archive is a true and complete record of the list activity, including mesages gated in from a newsgroup. ------------------------------ Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2 From Benjamin B. Thomas" > Barry A. Warsaw bwarsaw@cnri.reston.va.us writes: > Is anybody currently gating Usenet to a mailing list, /and/ doing > archiving with the default Pipermail? I am not yet using Mailman to do this, but I am doing the same thing with a hairy custom setup (majordomo + MHonArc + INN + gateway scripts). In about a month or so, I plan to switch our setup over to Mailman since it is *so* much nicer. > I would rather not add this hack to Mailman unless a lot of people > would benefit from it. We have a number of people who choose to interact via our local Usenet groups, and it is important that their contributions are archived. Without the ability to do so, I will need to stay with our current setup (icky as it is from an administrative standpoint, it does what I need) instead of moving to Mailman. Let me just say that Mailman is a wonderful piece of software. I have poked at it a little bit on a test installation, and it is beautifully conceived and implemented. Cheers, benjy 1975 Cahaba Valley Road (205) 988-4268 Indian Springs, AL 35124 benjy@alum.mit.edu From jeffh@streek.com Sat Apr 3 15:08:57 1999 From: jeffh@streek.com (Jeff Hahn) Date: Sat, 3 Apr 1999 09:08:57 -0600 (CST) Subject: [Mailman-Developers] mailpasswds issues with multiple domains In-Reply-To: <14082.20521.113988.624234@anthem.cnri.reston.va.us> Message-ID: I noticed on Wednesday that mailpasswds doesn't handle multiple domains very gracefully. I'm going to try to get it cleaned up where it lists the "default" server in the subject line, listname AND domain in the individual list lines, etc. Is this an issue for other people? In other words, should I make up a set of clean diff's and submit them for inclusion in the distribution? To where? -Jeff From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 15:33:42 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 10:33:42 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] Usenet gating and archiving References: <14085.12026.294121.877453@anthem.cnri.reston.va.us> <199904022253.PAA03119@ns.kinfolk.org> Message-ID: <14086.13526.835019.150195@anthem.cnri.reston.va.us> >>>>> "RBP" == Richard B Pyne writes: RBP> I have not yet started using the gateway, but it and the RBP> automated archives are two of the features that attracted me RBP> to mailman. I do plan on using it in the future. And it will work in 1.0b11. >> I would rather not add this hack to Mailman unless a lot of >> people would benefit from it. For the test lists that I'm >> running, we're willing to just trash the archives and start >> over; the lists aren't live anyway. I'd like to know who would >> be really adversely affected by this problem. RBP> What good is an incomplete archive? I feel that it is very RBP> important that the archive is a true and complete record of RBP> the list activity, including mesages gated in from a RBP> newsgroup. Maybe I phrased the question incorrectly. If you have not yet begun to archive a gated list, but only start doing so after you install 1.0b11 (which will be released sometime this morning), you will be fine. If you are running 1.0b10 or earlier, and have already started archiving a gated group, your archives will be messed up (if you haven't already noticed ;-). Someone would have to write a script to jam in the Unixfrom headers in the .mbox files and then rerun the script. It's probably not hard to write -- I'm just proposing that I don't need to do it, 'cause the number of people affect approaches zero right now. ;-) -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 16:00:46 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 11:00:46 -0500 (EST) Subject: [Mailman-Developers] Usenet gating and archiving References: <199904030918.DAA30599@mail.indiansprings.org> Message-ID: <14086.15150.168254.950818@anthem.cnri.reston.va.us> >>>>> "BBT" == Benjamin B Thomas writes: BBT> We have a number of people who choose to interact via our BBT> local Usenet groups, and it is important that their BBT> contributions are archived. Without the ability to do so, I BBT> will need to stay with our current setup (icky as it is from BBT> an administrative standpoint, it does what I need) instead of BBT> moving to Mailman. Then you'll definitely want to install 1.0b11. It should all work fine in that release (I'm testing it now on some internal lists, and it looks pretty good). I think I was probably not very clear in my message (I was rushed to leave). The problem /only/ affects you if you are running something earlier than 1.0b11 (to be released in a few minutes) and are already archiving a gated list. Any new lists you start gating after installing 1.0b11 will work just fine. BBT> Let me just say that Mailman is a wonderful piece of BBT> software. I have poked at it a little bit on a test BBT> installation, and it is beautifully conceived and BBT> implemented. Thanks very much! -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 16:13:52 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 11:13:52 -0500 (EST) Subject: [Mailman-Developers] mailpasswds issues with multiple domains References: <14082.20521.113988.624234@anthem.cnri.reston.va.us> Message-ID: <14086.15936.364277.751103@anthem.cnri.reston.va.us> >>>>> "JH" == Jeff Hahn writes: JH> I noticed on Wednesday that mailpasswds doesn't handle JH> multiple domains very gracefully. JH> I'm going to try to get it cleaned up where it lists the JH> "default" server in the subject line, listname AND domain in JH> the individual list lines, etc. JH> Is this an issue for other people? In other words, should I JH> make up a set of clean diff's and submit them for inclusion in JH> the distribution? To where? Greg Stein would love you for it! If you could generate diffs against the CVS snapshot, you can send them to mailman-developers and I'll try to add them before the 1.0 release. -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 16:36:33 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 11:36:33 -0500 (EST) Subject: [Mailman-Developers] Release 1.0b11 Message-ID: <14086.17297.485997.392346@anthem.cnri.reston.va.us> Okay folks, 1.0b11 is now available at www.list.org. This is basically a bug fix release addressing problems with case-preserving addresses and archiving of Usenet gated newsgroups. For you hardcore debugging types, there's a new script called bin/withlist which you can run like so: % cd ~mailman % python -i bin/withlist mylist Loading list: mylist (unlocked) >>> m.members {'bwarsaw@cnri.reston.va.us': 0} >>> withlist leaves you with a global variable `m' which is the MailList object you opened. Give withlist and optional second argument if you want the list to be locked. A note about upgrading. I had to bump the DATA_FILE_VERSION number so that the config.db got updated to deal with case-preserving addresses in some situation. I've been running this on python.org for a few days now and it all seems to work, but please keep an eye out for anything strange with your config.db file. Enjoy, -Barry From Gergely Madarasz Sat Apr 3 17:14:18 1999 From: Gergely Madarasz (Gergely Madarasz) Date: Sat, 3 Apr 1999 19:14:18 +0200 (METDST) Subject: [Mailman-Developers] Re: [Mailman-Users] Release 1.0b11 In-Reply-To: <14086.17297.485997.392346@anthem.cnri.reston.va.us> Message-ID: On Sat, 3 Apr 1999, Barry A. Warsaw wrote: > Okay folks, 1.0b11 is now available at www.list.org. This is basically > a bug fix release addressing problems with case-preserving addresses and > archiving of Usenet gated newsgroups. For you hardcore debugging types, I have just tried it, no problems so far. A debian package will be shortly uploaded to the debian master server... I have one suggestion though. The update script should check if the previous version already has the new options.html and not warn about it if it does... -- Madarasz Gergely gorgo@caesar.elte.hu gorgo@linux.rulez.org It's practically impossible to look at a penguin and feel angry. Egy pingvinre gyakorlatilag lehetetlen haragosan nezni. HuLUG: http://mlf.linux.rulez.org/ From bruce@perens.com Sat Apr 3 20:58:53 1999 From: bruce@perens.com (bruce@perens.com) Date: 3 Apr 1999 20:58:53 -0000 Subject: [Mailman-Developers] mailpasswds issues with multiple domains Message-ID: <19990403205853.24211.qmail@perens.com> From: Jeff Hahn > Is this an issue for other people? In other words, should I make up a set > of clean diff's and submit them for inclusion in the distribution? To > where? Yes. I'm running mine in multiple domains, it would be very handy. Thanks Bruce From Jeff Hahn Sun Apr 4 00:17:15 1999 From: Jeff Hahn (Jeff Hahn) Date: Sat, 3 Apr 1999 18:17:15 -0600 (CST) Subject: [Mailman-Developers] oops - hit a bug - 1.0b11 Message-ID: just noticed this in my logs from this afternoon - don't know if it's b11 specific... I am able to reproduce the problem by: 1. go to listinfo page 2. hit link for archive (archive restricted to members) 3. enter aaa@bbb.com for user ( any non member ) 4. enter 12345 (or anything else for password) then I get the "oops" page... I don't recall trying to access a restricted archive as a non-member before this, so it may not be b11 specific. I assume private.py should also be trapping the MMNotAMemberError error... -Jeff Apr 03 18:04:13 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin: [----- Mailman Version: 1.0b11 -----] admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/home/mailman/MM/scripts/driver", line 112, in run_main admin: main() admin: File "/home/mailman/MM/Mailman/Cgi/private.py", line 163, in main admin: if not list_name or not isAuthenticated(list_name): admin: File "/home/mailman/MM/Mailman/Cgi/private.py", line 120, in isAuthenticated admin: listobj.ConfirmUserPassword( username, password) admin: File "/home/mailman/MM/Mailman/SecurityManager.py", line 76, in ConfirmUserPassword admin: raise Errors.MMNotAMemberError admin: MMNotAMemberError From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sun Apr 4 03:07:49 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 21:07:49 -0500 (EST) Subject: [Mailman-Developers] oops - hit a bug - 1.0b11 References: Message-ID: <14086.51573.830624.955454@anthem.cnri.reston.va.us> >>>>> "JH" == Jeff Hahn writes: JH> just noticed this in my logs from this afternoon - don't know JH> if it's b11 specific... JH> I am able to reproduce the problem by: | 1. go to listinfo page | 2. hit link for archive (archive restricted to members) | 3. enter aaa@bbb.com for user ( any non member ) | 4. enter 12345 (or anything else for password) JH> then I get the "oops" page... I don't recall trying to access JH> a restricted archive as a non-member before this, so it may JH> not be b11 specific. I assume private.py should also be JH> trapping the MMNotAMemberError error... Correct. Here's a patch, thanks for the report! -Barry -------------------- snip snip -------------------- Index: private.py =================================================================== RCS file: /projects/cvsroot/mailman/Mailman/Cgi/private.py,v retrieving revision 1.11 retrieving revision 1.12 diff -c -r1.11 -r1.12 *** private.py 1999/03/29 23:53:57 1.11 --- private.py 1999/04/04 02:06:58 1.12 *************** *** 118,124 **** raise SystemExit try: listobj.ConfirmUserPassword( username, password) ! except (Errors.MMBadUserError, Errors.MMBadPasswordError): return 0 token = `hash(list_name)` --- 118,125 ---- raise SystemExit try: listobj.ConfirmUserPassword( username, password) ! except (Errors.MMBadUserError, Errors.MMBadPasswordError, ! Errors.MMNotAMemberError): return 0 token = `hash(list_name)` From jeffh@streek.com Sun Apr 4 16:22:33 1999 From: jeffh@streek.com (Jeff Hahn) Date: Sun, 4 Apr 1999 10:22:33 -0500 (CDT) Subject: [Mailman-Developers] changes to mailpasswd to support multiple domains Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1523646986-1305930720-923239353=:8555 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Attached is a patch to cron/mailpasswds and templates/cronpass.txt to support multiple domains in the monthly password reminder. Patch is against latest CVS sources (1.0b11) WARNING: Apply with care! I'm just getting familiar with Python and Mailman so I could have made some really idiotic mistakes, but it works here... To Apply: cd /usr/src/mailman ("main" source directory) patch -p1 -b Content-Description: ZGlmZiAtYyAtciBNTS5vcmlnL2Nyb24vbWFpbHBhc3N3ZHMgTU0vY3Jvbi9t YWlscGFzc3dkcw0KKioqIE1NLm9yaWcvY3Jvbi9tYWlscGFzc3dkcwlTYXQg QXByICAzIDA5OjE4OjE5IDE5OTkNCi0tLSBNTS9jcm9uL21haWxwYXNzd2Rz CVN1biBBcHIgIDQgMTA6MDA6MjQgMTk5OQ0KKioqKioqKioqKioqKioqDQoq KiogNTEsNzkgKioqKg0KICANCiAgICAgIFRoZSBsaXN0IGNhbiBiZSBhbnkg cmFuZG9tIG9uZSAtIGl0IGlzIG9ubHkgdXNlZCBmb3IgdGhlIG1lc3NhZ2UN CiAgICAgIGRlbGl2ZXJ5IG1lY2hhbmlzbS4iIiINCiEgICAgIHN1YmogPSAn JXMgbWFpbGxpc3QgbWVtYmVyc2hpcHMgcmVtaW5kZXJcbicgJSBsaXN0Lmhv c3RfbmFtZQ0KICAgICAgY291bnQgPSBQQVVTRV9GUkVRVUVOQ1kNCiAgICAg IGZvciB1c2VyLCBkYXRhIGluIHVzZXJzLml0ZW1zKCk6DQohIAl0YWJsZSA9 IFtdDQohIAlmb3IgbCwgcCwgdSBpbiBkYXRhOg0KISAJICAgIGlmIGxlbihs KSA+IDk6DQohIAkJdGFibGUuYXBwZW5kKCIlc1xuICAgICAgICAgICAlLTEw c1xuJXNcbiIgJSAobCwgcCwgdSkpDQohIAkgICAgZWxzZToNCiEgCQl0YWJs ZS5hcHBlbmQoIiUtMTBzICUtMTBzXG4lc1xuIiAlIChsLCBwLCB1KSkNCiEg CWhlYWRlciA9ICgiJS0xMHMgJS0xMHNcbiUtMTBzICUtMTBzIg0KISAJCSAg JSAoIkxpc3QiLCAiUGFzc3dvcmQgLy8gVVJMIiwgIi0tLS0iLCAiLS0tLS0t LS0iKSkNCiAgICAgICAgICB0ZXh0ID0gVXRpbHMubWFrZXRleHQoDQogICAg ICAgICAgICAgICdjcm9ucGFzcy50eHQnLA0KISAgICAgICAgICAgICB7J2hv c3RuYW1lJzogbGlzdC5ob3N0X25hbWUsDQogICAgICAgICAgICAgICAndXNl cicgICAgOiB1c2VyLA0KISAgICAgICAgICAgICAgJ29uZV9saXN0JzogbCwN CiAgICAgICAgICAgICAgIH0pDQogICAgICAgICAgIyBhZGQgdGhpcyB0byB0 aGUgZW5kIHNvIGl0IGRvZXNuJ3QgZ2V0IHdyYXBwZWQvZmlsbGVkDQogICAg ICAgICAgdGV4dCA9IHRleHQgKyBoZWFkZXIgKyAnXG4nICsgc3RyaW5nLmpv aW4odGFibGUsICdcbicpDQohICAgIAlsaXN0LlNlbmRUZXh0VG9Vc2VyKHN1 YmplY3QgPSBzdWJqLA0KISAgICAJCQkgICAgcmVjaXBpZW50ID0gdXNlciwN CiEgICAgCQkJICAgIHRleHQgPSB0ZXh0LA0KISAgCQkJICAgIHNlbmRlciA9 IG1tX2NmZy5NQUlMTUFOX09XTkVSLA0KICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgYWRkX2hlYWRlcnMgPSBbIlgtTm8tQXJjaGl2ZTogeWVzIiwN CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICJQcmVjZWRlbmNlOiBidWxrIl0pDQogICAgICAgICAgY291bnQgPSBjb3Vu dCAtIDENCi0tLSA1MSw4MiAtLS0tDQogIA0KICAgICAgVGhlIGxpc3QgY2Fu IGJlIGFueSByYW5kb20gb25lIC0gaXQgaXMgb25seSB1c2VkIGZvciB0aGUg bWVzc2FnZQ0KICAgICAgZGVsaXZlcnkgbWVjaGFuaXNtLiIiIg0KISAgICAg ZGVmYXVsdF9ob3N0ID0gbW1fY2ZnLkRFRkFVTFRfSE9TVF9OQU1FDQohICAg ICBtYWlsbWFuX293bmVyID0gbW1fY2ZnLk1BSUxNQU5fT1dORVINCiEgICAg IHN1YmogPSAnJXMgbWFpbGxpc3QgbWVtYmVyc2hpcHMgcmVtaW5kZXJcbicg JSBkZWZhdWx0X2hvc3QNCiAgICAgIGNvdW50ID0gUEFVU0VfRlJFUVVFTkNZ DQogICAgICBmb3IgdXNlciwgZGF0YSBpbiB1c2Vycy5pdGVtcygpOg0KISAg ICAgICAgIHRhYmxlID0gW10NCiEgICAgICAgICBmb3IgbCwgciwgcCwgdSBp biBkYXRhOg0KISAgICAgICAgICAgICBpZiBsZW4obCkgPiAzOToNCiEgICAg ICAgICAgICAgICAgIHRhYmxlLmFwcGVuZCgiJXNcbiAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgJS0xMHNcbiVzXG4iICUgKGws IHAsIHUpKQ0KISAgICAgICAgICAgICBlbHNlOg0KISAgICAgICAgICAgICAg ICAgdGFibGUuYXBwZW5kKCIlLTQwcyAlLTEwc1xuJXNcbiIgJSAobCwgcCwg dSkpDQohICAgICAgICAgaGVhZGVyID0gKCIlLTQwcyAlLTEwc1xuJS00MHMg JS0xMHMiDQohICAgICAgICAgICAgICAgICAgICAlICgiTGlzdCIsICJQYXNz d29yZCAvLyBVUkwiLCAiLS0tLSIsICItLS0tLS0tLSIpKQ0KICAgICAgICAg IHRleHQgPSBVdGlscy5tYWtldGV4dCgNCiAgICAgICAgICAgICAgJ2Nyb25w YXNzLnR4dCcsDQohICAgICAgICAgICAgIHsnZGVmX2hvc3QnOiBkZWZhdWx0 X2hvc3QsDQogICAgICAgICAgICAgICAndXNlcicgICAgOiB1c2VyLA0KISAg ICAgICAgICAgICAgJ2V4X3JlcScgIDogciwNCiEgICAgICAgICAgICAgICdt bV9vd25lcic6IG1haWxtYW5fb3duZXIsDQogICAgICAgICAgICAgICB9KQ0K ICAgICAgICAgICMgYWRkIHRoaXMgdG8gdGhlIGVuZCBzbyBpdCBkb2Vzbid0 IGdldCB3cmFwcGVkL2ZpbGxlZA0KICAgICAgICAgIHRleHQgPSB0ZXh0ICsg aGVhZGVyICsgJ1xuJyArIHN0cmluZy5qb2luKHRhYmxlLCAnXG4nKQ0KISAg ICAgICAgIGxpc3QuU2VuZFRleHRUb1VzZXIoc3ViamVjdCA9IHN1YmosDQoh ICAgICAgICAgICAgICAgICAgICAgICAgICAgICByZWNpcGllbnQgPSB1c2Vy LA0KISAgICAgICAgICAgICAgICAgICAgICAgICAgICAgdGV4dCA9IHRleHQs DQohICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzZW5kZXIgPSBtYWls bWFuX293bmVyLA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgYWRk X2hlYWRlcnMgPSBbIlgtTm8tQXJjaGl2ZTogeWVzIiwNCiAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICJQcmVjZWRlbmNl OiBidWxrIl0pDQogICAgICAgICAgY291bnQgPSBjb3VudCAtIDENCioqKioq KioqKioqKioqKg0KKioqIDg3LDExOSAqKioqDQogICAgICB0aGUgdXNlciBh IHNpbmdsZSBtZXNzYWdlIHdpdGggdGhlIGluZm8gZm9yIGFsbCB0aGVpciBs aXN0cyBvbiB0aGlzDQogICAgICBzaXRlLiIiIg0KICAgICAgbGlzdCA9IE5v bmUNCiEgICAgIHVzZXJzID0ge30JCQkJIyB1c2VyOiAobGlzdG5hbWUsIHBh c3N3b3JkLCB1cmwpDQogICAgICAjIENvbnN0cmFpbiB0byBzcGVjaWZpZWQg dXNlcnMsIGlmIGFueS4NCiAgICAgIGNvbmZpbmVkX3RvID0gYXJnc1sxOl0N CiAgICAgIGFfcHVibGljX2xpc3QgPSBOb25lDQogICAgICBmb3IgbmFtZSBp biBVdGlscy5saXN0X25hbWVzKCk6DQohIAlsaXN0ID0gTWFpbExpc3QuTWFp bExpc3QobmFtZSwgbG9jayA9IDApDQogICAgICAgICAgaWYgbm90IGFfcHVi bGljX2xpc3QgYW5kIGxpc3QuYWR2ZXJ0aXNlZDoNCiAgICAgICAgICAgICAg YV9wdWJsaWNfbGlzdCA9IGxpc3QNCiEgCWxpc3RfbmFtZSA9IGxpc3QucmVh bF9uYW1lDQohIAl1bWJyZWxsYV9saXN0ID0gbGlzdC51bWJyZWxsYV9saXN0 DQohIAlpZiBub3QgbGlzdC5zZW5kX3JlbWluZGVyczoNCiEgCSAgICBjb250 aW51ZQ0KISAJZm9yIHVzZXIsIHBhc3N3b3JkIGluIGxpc3QucGFzc3dvcmRz Lml0ZW1zKCk6DQogICAgICAgICAgICAgIGlmIGNvbmZpbmVkX3RvOg0KICAg ICAgICAgICAgICAgICAgaWYgdXNlciBub3QgaW4gY29uZmluZWRfdG86DQog ICAgICAgICAgICAgICAgICAgICAgY29udGludWUNCiAgICAgICAgICAgICAg ICAgIGVsc2U6DQogICAgICAgICAgICAgICAgICAgICAgIyBXZSdyZSBhIGJp dCB2ZXJib3NlIHdoZW4gb3BlcmF0aW5nICJjb25maW5lZF90byI6DQogICAg ICAgICAgICAgICAgICAgICAgcHJpbnQgIiVzIGluICVzIiAlICh1c2VyLCBs aXN0LnJlYWxfbmFtZSkNCiEgCSAgICB1cmwgPSBsaXN0LkdldEFic29sdXRl T3B0aW9uc1VSTCh1c2VyKQ0KICAgICAgICAgICAgICByZWNpcGllbnQgPSBs aXN0LkdldE1lbWJlckFkbWluRW1haWwodXNlcikNCiEgCSAgICBpZiB1c2Vy cy5oYXNfa2V5KHJlY2lwaWVudCk6DQohIAkJdXNlcnNbcmVjaXBpZW50XS5h cHBlbmQobGlzdF9uYW1lLCBwYXNzd29yZCwgdXJsKQ0KISAJICAgIGVsc2U6 DQohIAkJdXNlcnNbcmVjaXBpZW50XSA9IFsobGlzdF9uYW1lLCBwYXNzd29y ZCwgdXJsKV0NCiAgICAgIGlmIGxpc3Q6DQohIAlNYWlsQWxsUGFzc3dvcmRz KGFfcHVibGljX2xpc3Qgb3IgbGlzdCwgdXNlcnMpDQogIA0KICBkZWYgd2Fp dGFsbCgpOg0KICAgICAgIiIiUmV0dXJuIG9ubHkgd2hlbiB0aGVyZSBhcmUg bm8gZm9ya2VkIHN1YnByb2Nlc3NlcyBydW5uaW5nLiIiIg0KLS0tIDkwLDEy NSAtLS0tDQogICAgICB0aGUgdXNlciBhIHNpbmdsZSBtZXNzYWdlIHdpdGgg dGhlIGluZm8gZm9yIGFsbCB0aGVpciBsaXN0cyBvbiB0aGlzDQogICAgICBz aXRlLiIiIg0KICAgICAgbGlzdCA9IE5vbmUNCiEgICAgIHVzZXJzID0ge30J CSMgdXNlcjogKGxpc3QgYWRkcmVzcywgcmVxdWVzdCBhZGRyZXNzLCBwYXNz d29yZCwgdXJsKQ0KICAgICAgIyBDb25zdHJhaW4gdG8gc3BlY2lmaWVkIHVz ZXJzLCBpZiBhbnkuDQogICAgICBjb25maW5lZF90byA9IGFyZ3NbMTpdDQog ICAgICBhX3B1YmxpY19saXN0ID0gTm9uZQ0KICAgICAgZm9yIG5hbWUgaW4g VXRpbHMubGlzdF9uYW1lcygpOg0KISAgICAgICAgIGxpc3QgPSBNYWlsTGlz dC5NYWlsTGlzdChuYW1lLCBsb2NrID0gMCkNCiAgICAgICAgICBpZiBub3Qg YV9wdWJsaWNfbGlzdCBhbmQgbGlzdC5hZHZlcnRpc2VkOg0KICAgICAgICAg ICAgICBhX3B1YmxpY19saXN0ID0gbGlzdA0KISAgICAgICAgIGxpc3RfYWRk cmVzcyA9IGxpc3QuR2V0TGlzdEVtYWlsKCkNCiEgICAgICAgICBsaXN0X3Jl cXVlc3QgPSBsaXN0LkdldFJlcXVlc3RFbWFpbCgpDQohICAgICAgICAgdW1i cmVsbGFfbGlzdCA9IGxpc3QudW1icmVsbGFfbGlzdA0KISAgICAgICAgIGlm IG5vdCBsaXN0LnNlbmRfcmVtaW5kZXJzOg0KISAgICAgICAgICAgICBjb250 aW51ZQ0KISAgICAgICAgIGZvciB1c2VyLCBwYXNzd29yZCBpbiBsaXN0LnBh c3N3b3Jkcy5pdGVtcygpOg0KICAgICAgICAgICAgICBpZiBjb25maW5lZF90 bzoNCiAgICAgICAgICAgICAgICAgIGlmIHVzZXIgbm90IGluIGNvbmZpbmVk X3RvOg0KICAgICAgICAgICAgICAgICAgICAgIGNvbnRpbnVlDQogICAgICAg ICAgICAgICAgICBlbHNlOg0KICAgICAgICAgICAgICAgICAgICAgICMgV2Un cmUgYSBiaXQgdmVyYm9zZSB3aGVuIG9wZXJhdGluZyAiY29uZmluZWRfdG8i Og0KICAgICAgICAgICAgICAgICAgICAgIHByaW50ICIlcyBpbiAlcyIgJSAo dXNlciwgbGlzdC5yZWFsX25hbWUpDQohICAgICAgICAgICAgIHVybCA9IGxp c3QuR2V0QWJzb2x1dGVPcHRpb25zVVJMKHVzZXIpDQogICAgICAgICAgICAg IHJlY2lwaWVudCA9IGxpc3QuR2V0TWVtYmVyQWRtaW5FbWFpbCh1c2VyKQ0K ISAgICAgICAgICAgICBpZiB1c2Vycy5oYXNfa2V5KHJlY2lwaWVudCk6DQoh ICAgICAgICAgICAgICAgICB1c2Vyc1tyZWNpcGllbnRdLmFwcGVuZChsaXN0 X2FkZHJlc3MsIGxpc3RfcmVxdWVzdCwgDQohICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHBhc3N3 b3JkLCB1cmwpDQohICAgICAgICAgICAgIGVsc2U6DQohICAgICAgICAgICAg ICAgICB1c2Vyc1tyZWNpcGllbnRdID0gWyhsaXN0X2FkZHJlc3MsIGxpc3Rf cmVxdWVzdCwgDQohICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgIHBhc3N3b3JkLCB1cmwpXQ0KICAg ICAgaWYgbGlzdDoNCiEgICAgICAgICBNYWlsQWxsUGFzc3dvcmRzKGFfcHVi bGljX2xpc3Qgb3IgbGlzdCwgdXNlcnMpDQogIA0KICBkZWYgd2FpdGFsbCgp Og0KICAgICAgIiIiUmV0dXJuIG9ubHkgd2hlbiB0aGVyZSBhcmUgbm8gZm9y a2VkIHN1YnByb2Nlc3NlcyBydW5uaW5nLiIiIg0KZGlmZiAtYyAtciBNTS5v cmlnL3RlbXBsYXRlcy9jcm9ucGFzcy50eHQgTU0vdGVtcGxhdGVzL2Nyb25w YXNzLnR4dA0KKioqIE1NLm9yaWcvdGVtcGxhdGVzL2Nyb25wYXNzLnR4dAlT YXQgQXByICAzIDA5OjE4OjI4IDE5OTkNCi0tLSBNTS90ZW1wbGF0ZXMvY3Jv bnBhc3MudHh0CVN1biBBcHIgIDQgMDg6MDc6MzggMTk5OQ0KKioqKioqKioq KioqKioqDQoqKiogMSw0ICoqKioNCiEgVGhpcyBpcyBhIHJlbWluZGVyLCBz ZW50IG91dCBvbmNlIGEgbW9udGgsIGFib3V0IHlvdXIgJShob3N0bmFtZSlz DQogIG1haWxpbmcgbGlzdCBtZW1iZXJzaGlwcy4gIEl0IGluY2x1ZGVzIHlv dXIgc3Vic2NyaXB0aW9uIGluZm8gYW5kDQogIGhvdyB0byB1c2UgaXQgdG8g Y2hhbmdlIGl0IG9yIHVuc3Vic2NyaWJlIGZyb20gYSBsaXN0Lg0KICANCi0t LSAxLDQgLS0tLQ0KISBUaGlzIGlzIGEgcmVtaW5kZXIsIHNlbnQgb3V0IG9u Y2UgYSBtb250aCwgYWJvdXQgeW91ciAlKGRlZl9ob3N0KXMNCiAgbWFpbGlu ZyBsaXN0IG1lbWJlcnNoaXBzLiAgSXQgaW5jbHVkZXMgeW91ciBzdWJzY3Jp cHRpb24gaW5mbyBhbmQNCiAgaG93IHRvIHVzZSBpdCB0byBjaGFuZ2UgaXQg b3IgdW5zdWJzY3JpYmUgZnJvbSBhIGxpc3QuDQogIA0KKioqKioqKioqKioq KioqDQoqKiogOCwxOCAqKioqDQogIA0KICBJbiBhZGRpdGlvbiB0byB0aGUg VVJMIGludGVyZmFjZXMsIHlvdSBjYW4gYWxzbyB1c2UgZW1haWwgdG8gbWFr ZSBzdWNoDQogIGNoYW5nZXMuICBGb3IgbW9yZSBpbmZvLCBzZW5kIGEgbWVz c2FnZSB0byB0aGUgJy1yZXF1ZXN0JyBhZGRyZXNzIG9mDQohIHRoZSBsaXN0 IChmb3IgZXhhbXBsZSwgJShvbmVfbGlzdClzLXJlcXVlc3RAJShob3N0bmFt ZSlzKSBjb250YWluaW5nDQogIGp1c3QgdGhlIHdvcmQgJ2hlbHAnIGluIHRo ZSBtZXNzYWdlIGJvZHksIGFuZCBhbiBlbWFpbCBtZXNzYWdlIHdpbGwgYmUN CiAgc2VudCB0byB5b3Ugd2l0aCBpbnN0cnVjdGlvbnMuDQogIA0KICBJZiB5 b3UgaGF2ZSBxdWVzdGlvbnMsIHByb2JsZW1zLCBjb21tZW50cywgZXRjLCBz ZW5kIHRoZW0gdG8NCiEgbWFpbG1hbi1vd25lckAlKGhvc3RuYW1lKXMuICBU aGFua3MhDQogIA0KICBQYXNzd29yZHMgZm9yICUodXNlcilzOg0KLS0tIDgs MTkgLS0tLQ0KICANCiAgSW4gYWRkaXRpb24gdG8gdGhlIFVSTCBpbnRlcmZh Y2VzLCB5b3UgY2FuIGFsc28gdXNlIGVtYWlsIHRvIG1ha2Ugc3VjaA0KICBj aGFuZ2VzLiAgRm9yIG1vcmUgaW5mbywgc2VuZCBhIG1lc3NhZ2UgdG8gdGhl ICctcmVxdWVzdCcgYWRkcmVzcyBvZg0KISB0aGUgbGlzdCAoZm9yIGV4YW1w bGUsICUoZXhfcmVxKXMpIGNvbnRhaW5pbmcNCiAganVzdCB0aGUgd29yZCAn aGVscCcgaW4gdGhlIG1lc3NhZ2UgYm9keSwgYW5kIGFuIGVtYWlsIG1lc3Nh Z2Ugd2lsbCBiZQ0KICBzZW50IHRvIHlvdSB3aXRoIGluc3RydWN0aW9ucy4N CiAgDQogIElmIHlvdSBoYXZlIHF1ZXN0aW9ucywgcHJvYmxlbXMsIGNvbW1l bnRzLCBldGMsIHNlbmQgdGhlbSB0bw0KISAlKG1tX293bmVyKXMuICBUaGFu a3MhDQogIA0KICBQYXNzd29yZHMgZm9yICUodXNlcilzOg0KKyANCg== --1523646986-1305930720-923239353=:8555-- From bryner@uiuc.edu Mon Apr 5 18:14:17 1999 From: bryner@uiuc.edu (Brian Ryner) Date: Mon, 05 Apr 1999 12:14:17 -0500 Subject: [Mailman-Developers] Envelope sender and list-admin address Message-ID: <3708EF69.991A02A@uiuc.edu> Hi- I reported a bug on this but I thought I'd also post here, becuause I might try to correct this myself (and any advice would be appreciated). Basically, when a message is sent to the admin address (i.e. mailman-developers-admin@python.org), the envelope sender is left untouched when the message is resent. I don't think this is a good idea. If an address on the admin list is not on the local host, and the email is not sent from the local host, then you basically have a message from a non-local address to a non-local address, which is a no-no in many anti-spam-relaying setups. It would make much more sense to set the envelope sender to the list-admin address. -- -Brian Ryner bryner@uiuc.edu From Harald.Meland@usit.uio.no Tue Apr 6 15:26:28 1999 From: Harald.Meland@usit.uio.no (Harald Meland) Date: 06 Apr 1999 16:26:28 +0200 Subject: [Mailman-Developers] exim - Failure to exec script- gid question In-Reply-To: nbecker@fred.net's message of "30 Mar 1999 13:37:19 -0500" References: Message-ID: [nbecker@fred.net] > I'm using mailman-1.0b10 + exim-2.10. > > Mar 30 13:10:08 nbeckerpc Mailman mail-wrapper: Failure to exec script. WANTED gid 12, GOT gid 99. (Reconfigure to take 99?) > > I can reconfigure mailman or exim to set the gid, but why is it needed > at all? Since wrapper is sgid, why does it care what gid was used to > invoke it? Just additional security check? Yes, it's "merely" a sanity check :) -- Harald From dan@feld.cvut.cz Mon Apr 12 16:45:19 1999 From: dan@feld.cvut.cz (Dan Ohnesorg) Date: Mon, 12 Apr 1999 17:45:19 +0200 (CEST) Subject: [Mailman-Developers] Hypermail Message-ID: I have troubles with hypermail archiver. On some ocasions it makes bad references between index page and articles, as you can see on http://poli.feld.cvut.cz/archives/public/kecy/1999-March/date.html 3-9 artiles from end are under one link. It is the most bad fall, but on other archives ot makes also too. It is version 1.0b10. BTW I will made templates for archives instead of static strings. Has it someone made alredy? cheers dan From claw@kanga.nu Mon Apr 12 17:35:18 1999 From: claw@kanga.nu (claw@kanga.nu) Date: Mon, 12 Apr 1999 09:35:18 -0700 Subject: [Mailman-Developers] Hypermail In-Reply-To: Message from Dan Ohnesorg of "Mon, 12 Apr 1999 17:45:19 +0200." Message-ID: On Mon, 12 Apr 1999 17:45:19 +0200 (CEST) Dan Ohnesorg wrote: > I have troubles with hypermail archiver. I strongly suggest you look at MHonArc (http://www.oac.uci.edu/indiv/ehood/mhonarc.doc.html). It has far better MIME support, is significantly more configurable, etc etc etc yada yada. -- J C Lawrence Internet: claw@kanga.nu ----------(*) Internet: coder@kanga.nu ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith... From dan@feld.cvut.cz Mon Apr 12 17:43:37 1999 From: dan@feld.cvut.cz (Dan Ohnesorg) Date: Mon, 12 Apr 1999 18:43:37 +0200 (CEST) Subject: [Mailman-Developers] Hypermail In-Reply-To: Message-ID: On Mon, 12 Apr 1999 claw@kanga.nu wrote: > On Mon, 12 Apr 1999 17:45:19 +0200 (CEST) > Dan Ohnesorg wrote: > > > I have troubles with hypermail archiver. > > I strongly suggest you look at MHonArc > (http://www.oac.uci.edu/indiv/ehood/mhonarc.doc.html). It has far > better MIME support, is significantly more configurable, etc etc > etc yada yada. Yes, I know, but it is nice on hypermail that it can be trigered directly from mailman. When I will use another archiving tool, it must be runed from crontab. Is is from my point of view bad, becouse on not loaded lists is archiving tool runned too often and system overhead is big, or too only sometimes and the archive is out of sync with list. What would developers say to method in mailman like start archiving? It is probably not good idea. Or to make generic inteface like os.exec(archiver,message is on stdin) ???? cheers dan From troy@akropolys.com Mon Apr 12 18:07:51 1999 From: troy@akropolys.com (Troy Morrison) Date: Mon, 12 Apr 1999 10:07:51 -0700 (PDT) Subject: [Mailman-Developers] Hypermail In-Reply-To: Message-ID: | Yes, I know, but it is nice on hypermail that it can be trigered directly | from mailman. When I will use another archiving tool, it must be runed | from crontab. Is is from my point of view bad, becouse on not loaded lists | is archiving tool runned too often and system overhead is big, or too only | sometimes and the archive is out of sync with list. I could be wrong (I downloaded mhonarc, but haven't really set it up to run with mailman), but doesn't mhonarc use "-add" to add a single message to the archives? Could you trigger that directly from mailman? Troy From lindsey@ncsa.uiuc.edu Mon Apr 12 18:16:58 1999 From: lindsey@ncsa.uiuc.edu (Christopher Lindsey) Date: Mon, 12 Apr 1999 12:16:58 -0500 (CDT) Subject: [Mailman-Developers] Hypermail In-Reply-To: from "Troy Morrison" at Apr 12, 99 10:07:51 am Message-ID: <199904121716.MAA25202@ferret.ncsa.uiuc.edu> > I could be wrong (I downloaded mhonarc, but haven't really set it up to > run with mailman), but doesn't mhonarc use "-add" to add a single message > to the archives? > > Could you trigger that directly from mailman? What I've done is subscribe a "user" to my mailman lists. That user then has a procmailrc file that calls mailman with a -add flag to auto-update the MHonArc archives. Incidentally, I believe the original question was miscommunicated. Even though they said hypermail archives, the site is most definitely using mailman's builtin pipermail. Chris From dan@feld.cvut.cz Mon Apr 12 18:19:08 1999 From: dan@feld.cvut.cz (Dan Ohnesorg) Date: Mon, 12 Apr 1999 19:19:08 +0200 (CEST) Subject: [Mailman-Developers] Hypermail In-Reply-To: Message-ID: On Mon, 12 Apr 1999, Troy Morrison wrote: > > | Yes, I know, but it is nice on hypermail that it can be trigered directly > | from mailman. When I will use another archiving tool, it must be runed > | from crontab. Is is from my point of view bad, becouse on not loaded lists > | is archiving tool runned too often and system overhead is big, or too only > | sometimes and the archive is out of sync with list. > > I could be wrong (I downloaded mhonarc, but haven't really set it up to > run with mailman), but doesn't mhonarc use "-add" to add a single message > to the archives? > > Could you trigger that directly from mailman? > > Troy Yes, the problem is, i can atach archiver on alias like list: |archiver, |listserv So can be attached any archiver to any list and is trigered only with incoming message. Problem is, that some messages are not send by listserv, becouse they are from spamming domain, contaist only commands for listserv etc. So the archive doesn't containts that what was send by listserv. Second is make archiver a listmember. Not bad, but message can spend many hours in mailqueue. It is not a online archiving. Third, my favourite is to call archiver inside listserv. And this can be by mailman complicated. But i will look on it to find some solution. cheers dan From claw@varesearch.com Mon Apr 12 22:15:09 1999 From: claw@varesearch.com (J C Lawrence) Date: Mon, 12 Apr 1999 14:15:09 -0700 Subject: [Mailman-Developers] Hypermail In-Reply-To: Message from Dan Ohnesorg of "Mon, 12 Apr 1999 18:43:37 +0200." Message-ID: On Mon, 12 Apr 1999 18:43:37 +0200 (CEST) Dan Ohnesorg wrote: > On Mon, 12 Apr 1999 claw@kanga.nu wrote: >> I strongly suggest you look at MHonArc >> (http://www.oac.uci.edu/indiv/ehood/mhonarc.doc.html). It has >> far better MIME support, is significantly more configurable, etc >> etc etc yada yada. > Yes, I know, but it is nice on hypermail that it can be trigered > directly from mailman. When I will use another archiving tool, it > must be runed from crontab. MHonArc can archive a single message piped to sdtin. See the docs for the -add (IIRC) command line option. -- J C Lawrence Internet: claw@kanga.nu ---------(*) Internet: claw@varesearch.com ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith... From grin@tolna.net Fri Apr 16 13:55:11 1999 From: grin@tolna.net (Peter Gervai) Date: Fri, 16 Apr 1999 14:55:11 +0200 Subject: [Mailman-Developers] jitterbug and #12 Message-ID: <19990416145511.C30613@mail.tolna.net> Hello, Out of my curiousity I submitted a bug into the bug database. It got resolved really fast. I only have two problems. First: Maybe it's just me but I don't really see WHO did close the bug. Second: The bug (actually rather a cosmetic problem than a real bug) still exists, and the resolving was unsatisfactory (huh :)) for me, but there is no way to reply to the bug resolver, either because I do not know who he was or because I'm "logged in as a guest user". And about the #12: as the original text told the install overwrites the $BASE/templates directory without warning. Since I localized the templates to be able to create localized lists with newlist I wasn't REALLY happy to learn that all of them got overwritten. Of course lists//templates don't get overwritten, but that's another matter I did not complain about... regards, grin From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Apr 16 15:44:49 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 16 Apr 1999 10:44:49 -0400 (EDT) Subject: [Mailman-Developers] jitterbug and #12 References: <19990416145511.C30613@mail.tolna.net> Message-ID: <14103.19681.690937.619719@anthem.cnri.reston.va.us> >>>>> "PG" == Peter Gervai writes: PG> Out of my curiousity I submitted a bug into the bug database. PG> It got resolved really fast. I only have two problems. PG> First: Maybe it's just me but I don't really see WHO did close PG> the bug. It was me, but apparently Jitterbug doesn't record that information. I'm very new to Jitterbug so maybe I've done something wrong. At this point you can pretty much assume that if something gets resolved, I did it. PG> Second: The bug (actually rather a cosmetic problem than a PG> real bug) still exists, and the resolving was unsatisfactory PG> (huh :)) for me, but there is no way to reply to the bug PG> resolver, either because I do not know who he was or because PG> I'm "logged in as a guest user". Hmm, another Jitterbug deficiency (feature? bug?). I would think guests should be able to continue the conversation about a bug via the database. Since you can't, you've done the right thing by emailing MMDev. PG> And about the #12: as the original text told the install PG> overwrites the $BASE/templates directory without PG> warning. Since I localized the templates to be able to create PG> localized lists with newlist I wasn't REALLY happy to learn PG> that all of them got overwritten. Of course PG> lists//templates don't get overwritten, but that's PG> another matter I did not complain about... Ah, I completely misunderstood your bug report. I've moved this back to incoming so I'll remember to deal with it. I'm not 100% sure what the solution should be though. -Barry From grin@tolna.net Fri Apr 16 15:52:40 1999 From: grin@tolna.net (Peter Gervai) Date: Fri, 16 Apr 1999 16:52:40 +0200 Subject: [Mailman-Developers] jitterbug and #12 In-Reply-To: <14103.19681.690937.619719@anthem.cnri.reston.va.us>; from Barry A. Warsaw on Fri, Apr 16, 1999 at 10:44:49AM -0400 References: <19990416145511.C30613@mail.tolna.net> <14103.19681.690937.619719@anthem.cnri.reston.va.us> Message-ID: <19990416165240.G30613@mail.tolna.net> On Fri, Apr 16, 1999 at 10:44:49AM -0400, Barry A. Warsaw wrote: > PG> Out of my curiousity I submitted a bug into the bug database. > PG> It got resolved really fast. I only have two problems. > > PG> First: Maybe it's just me but I don't really see WHO did close > PG> the bug. > > It was me, It's hard to keep secret that I suspected that. :-)) > PG> And about the #12: as the original text told the install > PG> overwrites the $BASE/templates directory without > PG> warning. Since I localized the templates to be able to create > PG> localized lists with newlist I wasn't REALLY happy to learn > PG> that all of them got overwritten. Of course > PG> lists//templates don't get overwritten, but that's > PG> another matter I did not complain about... > > Ah, I completely misunderstood your bug report. No problem, that's why I tried to reply. > I've moved this back > to incoming so I'll remember to deal with it. I'm not 100% sure what > the solution should be though. Possibility#1: create a backup file/directory when overwriting Possibility#2: keep MD5/CRC/whatever of the 'original' file thus be able to detect whether it was modified or not cya, grin From gonter@maestria.wu-wien.ac.at Sat Apr 17 18:59:18 1999 From: gonter@maestria.wu-wien.ac.at (Gerhard Gonter) Date: Sat, 17 Apr 1999 19:59:18 +0200 (MES) Subject: [Mailman-Developers] Re: [Mailman-Users] Moving Listproc lists In-Reply-To: <4.1.19990417094443.00b43370@pop.nekodojo.org> from Greg Connor at "Apr 17, 99 09:55:40 am" Message-ID: <199904171759.TAA24566@maestria.wu-wien.ac.at> According to Greg Connor: > I did it all by hand on my system... here are the commands I used to > transfer users, as closely as I can remember... Thanks a lot, in the meantime I moved the subscribers of the first few lists (100 more to go :) using a modified add_members: ./add_members --lp6 lists/LIST1/.subscribers list1 Only one file, add_members, had to be modified. This maps ACK, NOACK -> normal subscriptions DIGEST -> digest subscriptions and keeps the original password. Addresses are converted to lower case. I will offer this version to the developers, maybe it will show up in the next version. Right now, POSTPONE'd entries are dropped and the CONCEAL flag is ignored, keeping this information requires modifications in other parts of Mailman. I'm not sure if I'll try that, maybe not... > Also, I had problems subbing more than 20 people at a time; all would get > subbed, but only 20 or so would get welcome messages (containing their new > random password). If you think you might have this problem too, use > something like this instead.. Hmm... Thanks for the hint. The sendmail logs tell me that everyone in a list with 167 members should have received their welcome messages by now, so this might be a bug in other versions. The bug archive didn't mention anything about that. (I'm using 1.0b8, the original add_members was pulled out of CVS yesterday.) +gg -- Gerhard.Gonter@wu-wien.ac.at Fax: +43/1/31336/702 g.gonter@ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria From gonter@maestria.wu-wien.ac.at Tue Apr 20 19:21:54 1999 From: gonter@maestria.wu-wien.ac.at (Gerhard Gonter) Date: Tue, 20 Apr 1999 20:21:54 +0200 (MES) Subject: [Mailman-Developers] automatically generated password too complicated? Message-ID: <199904201821.UAA20318@maestria.wu-wien.ac.at> Some of our users complained about the automatically generated passwords that are sent out when a list is imported or if an admin subscribes someone. Especially the ` and ^ characters are major problem because these may be treated as parts of composite characters in some enviroments (` followed by a might be displayed as the same character as à in HTML) and so on. Also, upper case characters impose an extra mental burden ;) Anyway, I modified our Mailman which now has a function (method?) Utils.GetRandomPassword(length) which generates passwords of the given length with a restricted alphabet, namely: a-x, 2-9, excluding characters o and l as well as digits 0 and 1 which may be confused and y, z (german keyboards swap these, in the past, this cause trouble too ;) I would like to offer this patch unless there are good reasons why this should be avoided. The main concern is certainly a higher risk to crack such passwords (only 30 possibilities instead of 64) but this could easly be matched by using 5 character passwords: possibilities strength --------------------------- 64^4 = 16777216 1 30^4 = 810000 0.05 30^5 = 24300000 1.45 As far as I have seen, this patch involves replacing certain calls to GetRandomSeed in a few places such as: bin/add_members, Mailman/Cgi/admin.py, Mailman/MailCommandHandler.py Any comment? +gg -- Gerhard.Gonter@wu-wien.ac.at Fax: +43/1/31336/702 g.gonter@ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria From gonter@maestria.wu-wien.ac.at Wed Apr 21 18:53:59 1999 From: gonter@maestria.wu-wien.ac.at (Gerhard Gonter) Date: Wed, 21 Apr 1999 19:53:59 +0200 (MES) Subject: [Mailman-Developers] dots in list name -> archive not accessible? Message-ID: <199904211753.TAA23396@maestria.wu-wien.ac.at> Once upon a time, one group of users decided that they need a list called Assistent/Inn/En@wu-wien.ac.at and it took me a while to convince them, that the / would not work so they accepted Assistent.Inn.En@wu-wien.ac.at which worked quite well on Listproc... Today I moved the list, everything went fine except that the archives were not accessible from the list overview page. I tracked this problem down to Mailman/Cgi/private.py where this function is defined, which strips an extension from the directory name: | def getListName(path): | component = string.split(path, os.sep)[1] | root, ext = os.path.splitext(component) | return root If component is returned instead of root, everything seems to be working fine for this list and the other lists without dots in their name. Why should an extension be stripped? Is this a bug, a feature, or something that was left over from VMS times? P.S.: Yesterday I mailed an message about the problems our users have with automatically generated passwords. Neither my collegue nor I seem to have received the article, also, no flames appeared either ;) The article has been archived as http://www.python.org/pipermail/mailman-developers/1999-April/001040.html Did something go wrong with that? +gg -- Gerhard.Gonter@wu-wien.ac.at Fax: +43/1/31336/702 g.gonter@ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria From klm@digicool.com Thu Apr 22 00:52:40 1999 From: klm@digicool.com (Ken Manheimer) Date: Wed, 21 Apr 1999 19:52:40 -0400 Subject: [Mailman-Developers] FW: [Mailman-Users] Still need code info for privacy option Message-ID: <613145F79272D211914B0020AFF640190BEE83@gandalf.digicool.com> I'm sorry i can't help more with this, no time - but mailman-developers is a more appropriate venue for the question, maybe you'll get some other attention there. Context for mailman-developers - setting the "hide the message sender" privacy option doesn't seem to be working, and the code (in MailList.MailList.Post()) doesn't seem to be right - the reply-to is deleted, but the code is setting the address to the list admin, not the list proper. And it's not working anyway - as james d mentions below, wiring it to set the from to something else is not working... Ken Manheimer klm@digicool.com -----Original Message----- From: Nicholson James D [mailto:James.Nicholson@amedd.army.mil] Sent: Tuesday, April 20, 1999 5:17 PM To: Ken Manheimer Cc: mailman-users@python.org Subject: RE: [Mailman-Users] Still need code info for privacy option [Nicholson James D] I found the problem with the list not remailing anonymously. In routine Post(), it deletes the sender and reply-to fields and then sets the from field. However, it set the From field to self.GetAdminEmail. What I needed it to do (and what I believe it should be doing) is setting the From field to self.GetListEmail, which will return the list address. However, I can't get the damned thing to change the From field for anything. I've even done a msg.setheader( 'From', 'listname@machine' ). That's hardwired in the Post() routine just for testing, and it isn't bloody changing the header... at all. I altered the MailList.py file, moved the MailList.pyc to oldMailList.pyc, and it still does the same damned thing. It sets the From field to whoever sent the message. Was I supposed to recompile the package or something to get my changes to take effect? I just don't know python or mailman well enough to know even this. Sorry. -Jim From g.sandrucci@agora.it Thu Apr 22 14:18:19 1999 From: g.sandrucci@agora.it (Gianni Sandrucci) Date: Thu, 22 Apr 1999 15:18:19 +0200 Subject: [Mailman-Developers] Mailman on NT Message-ID: <371F219B.68A236AA@agora.it> I have read some messages about future Mailman NT release. Since I have appreciated Mailman on a IBM AIX system I tried a porting test on NT with following steps: - installed Cygwin 2.0 (www.cygnus.com) - installed Python for Windows with all Windows specific extension - installed Mailman 1.0 b11 - made some minor changes in Mailmal files configure and src/Makefile.in - after some fighting with permissions (I was forced to comment tests on these matters in configuration script and C source code) succeded to ./configure --with-cgi-ext=.exe make install (no errors reported) - configured IIS to create a virtual site on /home/mailman named mailman - called: http://localhost/mailman/cgi-bin/admin.exe Got an error (reported below). It seems Python is not able to locate Mailman modules in /home/mailman/Mailman. However modules are there (in py and pyc format). I tried to go up in erorrs chain but every time the 'driver' script try to import something from Mailman I got the same error. Since I know very little about Python I wonder if anybody can help me. Thanks. ------------------------------------------- Bug in Mailman version 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 (innermost last): File "/home/mailman/scripts/driver", line 135, in print_traceback from Mailman.mm_cfg import VERSION ImportError: No module named Mailman.mm_cfg -------------------------------------------------------------------------------- Environment variables: Variable Value USERPROFILE C:\WINNT\Profiles\Default User HTTP_ACCEPT_ENCODING gzip, deflate REMOTE_HOST 127.0.0.1 HTTPS off OS2LIBPATH C:\WINNT\system32\os2\dll; SERVER_PORT_SECURE 0 SERVER_PORT 80 PATH_TRANSLATED C:\Inetpub\wwwroot PROCESSOR_LEVEL 6 GATEWAY_INTERFACE CGI/1.1 INSTANCE_ID 1 NUMBER_OF_PROCESSORS 1 HTTP_ACCEPT_LANGUAGE en-us PATH c:\agora\servletmanager\jrun\bin;c:\agora\servletmanager\jrun\jre\115\bin;C:\WINNT\system32;C:\WINNT;C:\Program Files\Mts SYSTEMDRIVE C: PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.JS SERVER_NAME localhost HTTP_CONNECTION Keep-Alive PROCESSOR_ARCHITECTURE x86 TERM cygwin WINDIR C:\WINNT HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* COMPUTERNAME SVIL4 INCLUDE C:\Program Files\Mts\Include SYSTEMROOT C:\WINNT SERVER_PROTOCOL HTTP/1.1 PROCESSOR_REVISION 0502 CONTENT_LENGTH 0 HTTP_HOST localhost REQUEST_METHOD GET PROCESSOR_IDENTIFIER x86 Family 6 Model 5 Stepping 2, GenuineIntel PYTHONPATH /home/mailman LOCAL_ADDR 127.0.0.1 SCRIPT_NAME /mailman/cgi-bin/admin.exe SERVER_SOFTWARE Microsoft-IIS/4.0 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 4.01; Windows NT) OS Windows_NT LIB C:\Program Files\Mts\Lib COMSPEC C:\WINNT\system32\cmd.exe REMOTE_ADDR 127.0.0.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [----- Mailman Version: -----] [----- Traceback ------] Traceback (innermost last): File "/home/mailman/scripts/driver", line 135, in print_traceback from Mailman.mm_cfg import VERSION ImportError: No module named Mailman.mm_cfg [----- Environment Variables -----] USERPROFILE: C:\WINNT\Profiles\Default User HTTP_ACCEPT_ENCODING: gzip, deflate REMOTE_HOST: 127.0.0.1 HTTPS: off OS2LIBPATH: C:\WINNT\system32\os2\dll; SERVER_PORT_SECURE: 0 SERVER_PORT: 80 PATH_TRANSLATED: C:\Inetpub\wwwroot PROCESSOR_LEVEL: 6 GATEWAY_INTERFACE: CGI/1.1 INSTANCE_ID: 1 NUMBER_OF_PROCESSORS: 1 HTTP_ACCEPT_LANGUAGE: en-us PATH: c:\agora\servletmanager\jrun\bin;c:\agora\servletmanager\jrun\jre\115\bin;C:\WINNT\system32;C:\WINNT;C:\Program Files\Mts SYSTEMDRIVE: C: PATHEXT: .COM;.EXE;.BAT;.CMD;.VBS;.JS SERVER_NAME: localhost HTTP_CONNECTION: Keep-Alive PROCESSOR_ARCHITECTURE: x86 TERM: cygwin WINDIR: C:\WINNT HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* COMPUTERNAME: SVIL4 INCLUDE: C:\Program Files\Mts\Include SYSTEMROOT: C:\WINNT SERVER_PROTOCOL: HTTP/1.1 PROCESSOR_REVISION: 0502 CONTENT_LENGTH: 0 HTTP_HOST: localhost REQUEST_METHOD: GET PROCESSOR_IDENTIFIER: x86 Family 6 Model 5 Stepping 2, GenuineIntel PYTHONPATH: /home/mailman LOCAL_ADDR: 127.0.0.1 SCRIPT_NAME: /mailman/cgi-bin/admin.exe SERVER_SOFTWARE: Microsoft-IIS/4.0 HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT) OS: Windows_NT LIB: C:\Program Files\Mts\Lib COMSPEC: C:\WINNT\system32\cmd.exe REMOTE_ADDR: 127.0.0.1 From gorgo@caesar.elte.hu Sun Apr 25 21:16:51 1999 From: gorgo@caesar.elte.hu (Gergely Madarasz) Date: Sun, 25 Apr 1999 22:16:51 +0200 (METDST) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 Message-ID: Hello! Mailman does not work with exim and python 1.5.2, probably because of the esmtp support in python 1.5.2's smtplib. Following is a trace from exim. Note that exim gets an ehlo and later a helo which resets it into smtp from esmtp. Please forward this to the appropriate python forums :) set_process_info: 15805 2.11 handling incoming connection from localhost [127.0.0.1] ready for new message smtp_setup_msg entered SMTP<< ehlo darmol.elte.hu sender_fullhost = localhost (darmol.elte.hu) [127.0.0.1] sender_rcvhost = localhost ([127.0.0.1] helo=darmol.elte.hu) set_process_info: 15805 2.11 handling incoming connection from localhost (darmol.elte.hu) [127.0.0.1] 250-darmol.elte.hu Hello localhost [127.0.0.1] 250-SIZE 2000000 250-PIPELINING 250 HELP SMTP<< helo darmol.elte.hu sender_fullhost = localhost (darmol.elte.hu) [127.0.0.1] sender_rcvhost = localhost ([127.0.0.1] helo=darmol.elte.hu) set_process_info: 15805 2.11 handling incoming connection from localhost (darmol.elte.hu) [127.0.0.1] 250 darmol.elte.hu Hello localhost [127.0.0.1] SMTP<< mail FROM: size=1335 LOG: 4 MAIN SMTP syntax error in "mail FROM: size=1335" H=localhost (darmol.elte.hu) [127.0.0.1]: malformed address: size=1335 may not follow 501 size=1335: malformed address: size=1335 may not follow SMTP<< rset 250 Reset OK 421 darmol.elte.hu lost input connection LOG: 4 MAIN SMTP connection from localhost (darmol.elte.hu) [127.0.0.1] lost child 15805 ended -- Madarasz Gergely gorgo@caesar.elte.hu gorgo@linux.rulez.org It's practically impossible to look at a penguin and feel angry. Egy pingvinre gyakorlatilag lehetetlen haragosan nezni. HuLUG: http://mlf.linux.rulez.org/ From dragondm@integral.org Mon Apr 26 17:02:26 1999 From: dragondm@integral.org (The Dragon De Monsyne) Date: Mon, 26 Apr 1999 11:02:26 -0500 (CDT) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 In-Reply-To: Message-ID: On Sun, 25 Apr 1999, Gergely Madarasz wrote: > Hello! > > Mailman does not work with exim and python 1.5.2, probably because of the > esmtp support in python 1.5.2's smtplib. Following is a trace from exim. > Note that exim gets an ehlo and later a helo which resets it into smtp > from esmtp. Please forward this to the appropriate python forums :) Erf, yes,I should have thrown a warning your folx's way (I'm the maintainer of python's smtplib) In 1.5.2 some of the return values of methods have been changed. Before, some of the methods returned integrer codes, some string descriptions, and some (code,desc) tuples. Now they _all_ return tuples (and the exception objects have more meaningful info, too). I'm in the middle of moving now, so I don't have access to a news server that carries c.l.p ATM, and half my equipment is packed. the patch should be simple In Mailman.Utils.TrySMTPDelivery() there is a few lines like: conn = smtplib.SMTP(mm_cfg.SMTPHOST) # Do the EHLO/HELO manually so we can check for DSN support if conn.ehlo() >= 400: conn.helo() change it to: conn = smtplib.SMTP(mm_cfg.SMTPHOST) # Do the EHLO/HELO manually so we can check for DSN support if conn.ehlo()[0] >= 400: conn.helo() (This change was considered resonable, as only code using ESMTP would likely need to call the SMTP command methods, most other code just uses the sendmail() method, and 1.5.1's smtplib didn't support ESMTP, so 1.5.2 was the 'last chance' to regularize the return values ) -The Dragon De Monsyne From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Apr 27 22:35:21 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 27 Apr 1999 17:35:21 -0400 (EDT) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 References: Message-ID: <14118.11673.876035.650537@anthem.cnri.reston.va.us> >>>>> "Dragon" == The Dragon De Monsyne writes: | conn = smtplib.SMTP(mm_cfg.SMTPHOST) | # Do the EHLO/HELO manually so we can check for DSN support | if conn.ehlo() >= 400: | conn.helo() Dragon> change it to: | conn = smtplib.SMTP(mm_cfg.SMTPHOST) | # Do the EHLO/HELO manually so we can check for DSN support | if conn.ehlo()[0] >= 400: | conn.helo() Thanks for the patch Dragon. I'm going to also copy Python 1.5.2's final smtplib.py file into Mailman/pythonlib and keep the module test hack in TrySMTPDelivery. What this means is that Mailman will probably be broken for Python 1.5.2 beta, but I don't think that's a huge loss. Comments? -Barry From James.Nicholson@amedd.army.mil Tue Apr 27 22:36:09 1999 From: James.Nicholson@amedd.army.mil (Nicholson James D) Date: Tue, 27 Apr 1999 17:36:09 -0400 Subject: [Mailman-Developers] Having kittens with the code Message-ID: I have been trying to fix the mailman code for some time now, and I would really appreciate any help. The basic problem is that the anonymous_list is broken on my machine, I don't know why, but, I can't even debug. My Problem: I turn on the anonymous_list option so that all mail appears to the recipient as if it emanates from the listname@machine. However, it doesn't work. Everything sent out to the test list still appears to come from an individual user. My Attempt at a solution: Someone told me that the anonymizing of the list is done in the Post() routine in MailList.py. So, I go in there and hardwire a change to the 'From' and 'To' fields, with no luck. So, if you find the code: del msg['reply-to'] del msg['sender'] I then add the following code: msg.SetHeader('From', 'listname@machinename') msg.SetHeader('To', 'listname@machinename') and comment out the following code beginning with 'if self.anonymous_list:' And what happens is nothing. Nothing I do here seems to affect the header of reflected mail. Is this the wrong place to make these changes or is the mail being postprocessed somewhere else that undoes my changes? So, now I really want to debug. So, I use the handy self.LogMsg() function. But, I get nothing in the logs. Here's the code I added right after the hardwired changes above: subj = msg.getheader('from') self.LogMsg("error", "initially from %s ", subj ) NADA for output. Can someone please send me a clue here? I've been working on it for weeks and can't get anywhere. If I can't solve the problem, I just won't have a mailing list. -Jim From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Apr 27 22:38:03 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 27 Apr 1999 17:38:03 -0400 (EDT) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 References: Message-ID: <14118.11835.729973.250910@anthem.cnri.reston.va.us> Oh dang. I just remembered that smtplib.py has a patch by Per Cederqvist post Python 1.5.2. I'm going to copy that version to Mailman/pythonlib and use it unconditionally. Dragon, how's that sound? -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Apr 27 23:53:10 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 27 Apr 1999 18:53:10 -0400 (EDT) Subject: [Mailman-Developers] Having kittens with the code References: Message-ID: <14118.16342.614948.711654@anthem.cnri.reston.va.us> >>>>> "NJD" == Nicholson James D writes: NJD> I have been trying to fix the mailman code for some time now, NJD> and I would really appreciate any help. The basic problem is NJD> that the anonymous_list is broken on my machine, I don't know NJD> why, but, I can't even debug. James, here's another situation that I can't reproduce. If I set "Hide the sender" to yes, I get the expected header. Note that sendmail gets partly in the way here (and this may be your problem?). For me, sendmail munges the From header to not include my host name. This sucks because our mailhost knows nothing about my list. Oh well, sendmail's evil anyway. :-) BTW, on your previous message on the subject, I think From: should still come from the GetAdminEmail(), however I think maybe Reply-To: for anonymous lists should be set to GetListEmail(). And note further that turning on anonymous_list is probably a false comfort. Lots of other headers get through that /could/ be used to identify the user (e.g. my X-Face header gets through). We'd probably want to do a lot more stripping of headers to have a really effective anonymizer. NJD> So, if you find the code: | del msg['reply-to'] | del msg['sender'] NJD> I then add the following code: | msg.SetHeader('From', 'listname@machinename') | msg.SetHeader('To', 'listname@machinename') NJD> and comment out the following code beginning with 'if NJD> self.anonymous_list:' And what happens is nothing. Nothing I NJD> do here seems to affect the header of reflected mail. Is NJD> this the wrong place to make these changes or is the mail NJD> being postprocessed somewhere else that undoes my changes? Okay, apologies for the following "did-you-plug-it-in" suggestion. You're sure that you're either making the change to the installed version of the files, or that you're doing a make install after making the changes. In other words, you're absolutely positive that Mailman's running your modified version? Try also blowing away the .pyc files and see if they get regenerated. Finally, you can just do something like: fp = open('/tmp/rawlog.txt', 'w') fp.write('I know you are in there!\n') fp.close() right at the point in question. If that file doesn't show up with the message in it, you've got deeper problems. If that works, but LogMsg() still doesn't, it /could/ be a permission problem, but I don't think so. You might just want to use your rawlog.txt file to do your logging directly. -Barry From bryner@uiuc.edu Fri Apr 30 17:52:19 1999 From: bryner@uiuc.edu (Brian Ryner) Date: Fri, 30 Apr 1999 11:52:19 -0500 Subject: [Mailman-Developers] Error/crash in admindb - 1.0b11 Message-ID: <3729DFC3.C3CF4F6E@uiuc.edu> This is a multi-part message in MIME format. --------------329FBC73D35B7EE45A42B7CB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi- This crash happened when going to http://host/mailman/admindb. I have not been able to reproduce it since then. The error log is attached. The system is running Slackware 3.5, with Python 1.5.1. Any suggestions or patches? Also, is there a way that I can turn off the extraneous debugging information sent to the WWW client, and have it just be put in the log? The fact that it dumps so much information about the system could be seen as a security risk. Thanks. -Brian Ryner bryner@uiuc.edu --------------329FBC73D35B7EE45A42B7CB Content-Type: text/plain; charset=us-ascii; name="error" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="error" Apr 29 22:33:41 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin: [----- Mailman Version: 1.0b11 -----] admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/admin/mailman/scripts/driver", line 112, in run_main admin: main() admin: File "/admin/mailman/Mailman/Cgi/admindb.py", line 77, in main admin: doc.AddItem(eader(2, "Invalid options to CGI script.")) admin: NameError: eader admin: [----- Environment Variables -----] admin: DOCUMENT_ROOT: /files/admin/httpd/htdocs admin: HTTP_ACCEPT_ENCODING: gzip, deflate admin: SERVER_PORT: 80 admin: PATH_TRANSLATED: /files/admin/httpd/htdocs/ admin: URL_COUNT: 6 admin: GATEWAY_INTERFACE: CGI/1.1 admin: HTTP_ACCEPT_LANGUAGE: en-us admin: HTTP_PROXY_CONNECTION: Keep-Alive admin: REMOTE_ADDR: xxx.yyy.zzz.xxx admin: SERVER_NAME: www.xxxxxxx.org admin: URL_COUNT_DB: /files/admin/httpd/logs/counters/ALL admin: HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 4.01; Windows 95) admin: HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* admin: REQUEST_URI: /mailman/admindb/ admin: PATH: /usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin admin: QUERY_STRING: admin: SCRIPT_FILENAME: /files/admin/mailman/cgi-bin/admindb admin: PATH_INFO: / admin: HTTP_HOST: www.xxxxxxx.org admin: REQUEST_METHOD: GET admin: SERVER_SIGNATURE: admin: URL_COUNT_RESET: Thursday, 29-Apr-99 00:19:13 CDT admin: SCRIPT_NAME: /mailman/admindb admin: SERVER_ADMIN: admin@xxxxxx.org admin: SERVER_SOFTWARE: Apache/1.3.4 (Unix) admin: PYTHONPATH: /admin/mailman admin: SERVER_PROTOCOL: HTTP/1.0 admin: REMOTE_PORT: 6208 --------------329FBC73D35B7EE45A42B7CB-- From bryner@uiuc.edu Fri Apr 30 18:55:15 1999 From: bryner@uiuc.edu (Brian Ryner) Date: Fri, 30 Apr 1999 12:55:15 -0500 Subject: [Mailman-Developers] Re: [Mailman-Users] Error/crash in admindb - 1.0b11 Message-ID: <3729EE83.5DA4F401@uiuc.edu> Is that line (admindb.py, line 77) supposed to say Header instead of eader ? > Apr 29 22:33:41 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > admin: [----- Mailman Version: 1.0b11 -----] > admin: [----- Traceback ------] > admin: Traceback (innermost last): > admin: File "/admin/mailman/scripts/driver", line 112, in run_main > admin: main() > admin: File "/admin/mailman/Mailman/Cgi/admindb.py", line 77, in main > admin: doc.AddItem(eader(2, "Invalid options to CGI script.")) > admin: NameError: eader From castro@usmatrix.net Thu Apr 1 04:23:33 1999 From: castro@usmatrix.net (Edgard Castro) Date: Wed, 31 Mar 1999 23:23:33 -0500 Subject: [Mailman-Developers] Re: [Mailman-checkins] CVS: mailman/Mailman Deliverer.py In-Reply-To: <199903311923.OAA08292@anthem.cnri.reston.va.us>; from Barry A. Warsaw on Wed, Mar 31, 1999 at 02:23:14PM -0500 References: <199903311923.OAA08292@anthem.cnri.reston.va.us> Message-ID: <19990331232333.A4242@usmatrix.net> On Wed, Mar 31, 1999 at 02:23:14PM -0500, Barry A. Warsaw wrote: > Modified Files: > Deliverer.py > Log Message: > DeliverToList(): Strip off any duplicate Sender: headers, leaving just > the one pointing to the list-admin. The same problems occurs with Errors-To, haven't checked agains other headers. e. -- Edgard Castro | 305-273-5003 -o) Chief Network Engineer - U.S. Matrix Internet, Inc. /\\ Linux Counter User #29078 -- http://counter.li.org _\_V From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Apr 2 20:56:26 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 2 Apr 1999 15:56:26 -0500 (EST) Subject: [Mailman-Developers] Usenet gating and archiving Message-ID: <14085.12026.294121.877453@anthem.cnri.reston.va.us> Is anybody currently gating Usenet to a mailing list, /and/ doing archiving with the default Pipermail? If so, you may not have noticed that the archives are pretty broken; nothing that originates on Usenet will show up in the archive. I believe I understand why this is happening, and although I don't have a fix yet, it shouldn't be too difficult. I should be able to get it into 1.0b11. The problem occurs because Pipermail uses Python's mailbox.UnixMailbox objects which expect "From " separators. Message that originate on Usenet don't have these envelopes. The patch should be to simply synthesize these on messages gated off the newsgroup. However, there's a more severe breakage. You've actually lost information that is hard to reproduce because the flat listname.mbox files don't have the separators in them either. Running bin/arch over the file will give you even more corrupt archives (the incremental archiver just throws the Usenet messages away; bin/arch will tack them onto the last email-originated message). What you could do is to trek through the listname.mbox file looking for Newsgroup: headers (which appear, but I don't think are guaranteed, to be the first header in the message). When you find one, you jam in a synthesized "From " envelope. I would rather not add this hack to Mailman unless a lot of people would benefit from it. For the test lists that I'm running, we're willing to just trash the archives and start over; the lists aren't live anyway. I'd like to know who would be really adversely affected by this problem. Thanks, -Barry From rpyne@kinfolk.org Fri Apr 2 22:53:53 1999 From: rpyne@kinfolk.org (Richard B. Pyne) Date: Fri, 2 Apr 1999 15:53:53 -0700 Subject: [Mailman-Developers] Re: [Mailman-Users] Usenet gating and archiving In-Reply-To: <14085.12026.294121.877453@anthem.cnri.reston.va.us> Message-ID: <199904022253.PAA03119@ns.kinfolk.org> On 2 Apr 99, at 15:56, Barry A. Warsaw wrote: > Is anybody currently gating Usenet to a mailing list, /and/ doing > archiving with the default Pipermail? If so, you may not have noticed > that the archives are pretty broken; nothing that originates on Usenet > will show up in the archive. I have not yet started using the gateway, but it and the automated archives are two of the features that attracted me to mailman. I do plan on using it in the future. > I would rather not add this hack to Mailman unless a lot of people > would benefit from it. For the test lists that I'm running, we're > willing to just trash the archives and start over; the lists aren't > live anyway. I'd like to know who would be really adversely affected > by this problem. What good is an incomplete archive? I feel that it is very important that the archive is a true and complete record of the list activity, including mesages gated in from a newsgroup. ------------------------------ Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2 From Benjamin B. Thomas" > Barry A. Warsaw bwarsaw@cnri.reston.va.us writes: > Is anybody currently gating Usenet to a mailing list, /and/ doing > archiving with the default Pipermail? I am not yet using Mailman to do this, but I am doing the same thing with a hairy custom setup (majordomo + MHonArc + INN + gateway scripts). In about a month or so, I plan to switch our setup over to Mailman since it is *so* much nicer. > I would rather not add this hack to Mailman unless a lot of people > would benefit from it. We have a number of people who choose to interact via our local Usenet groups, and it is important that their contributions are archived. Without the ability to do so, I will need to stay with our current setup (icky as it is from an administrative standpoint, it does what I need) instead of moving to Mailman. Let me just say that Mailman is a wonderful piece of software. I have poked at it a little bit on a test installation, and it is beautifully conceived and implemented. Cheers, benjy 1975 Cahaba Valley Road (205) 988-4268 Indian Springs, AL 35124 benjy@alum.mit.edu From jeffh@streek.com Sat Apr 3 15:08:57 1999 From: jeffh@streek.com (Jeff Hahn) Date: Sat, 3 Apr 1999 09:08:57 -0600 (CST) Subject: [Mailman-Developers] mailpasswds issues with multiple domains In-Reply-To: <14082.20521.113988.624234@anthem.cnri.reston.va.us> Message-ID: I noticed on Wednesday that mailpasswds doesn't handle multiple domains very gracefully. I'm going to try to get it cleaned up where it lists the "default" server in the subject line, listname AND domain in the individual list lines, etc. Is this an issue for other people? In other words, should I make up a set of clean diff's and submit them for inclusion in the distribution? To where? -Jeff From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 15:33:42 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 10:33:42 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] Usenet gating and archiving References: <14085.12026.294121.877453@anthem.cnri.reston.va.us> <199904022253.PAA03119@ns.kinfolk.org> Message-ID: <14086.13526.835019.150195@anthem.cnri.reston.va.us> >>>>> "RBP" == Richard B Pyne writes: RBP> I have not yet started using the gateway, but it and the RBP> automated archives are two of the features that attracted me RBP> to mailman. I do plan on using it in the future. And it will work in 1.0b11. >> I would rather not add this hack to Mailman unless a lot of >> people would benefit from it. For the test lists that I'm >> running, we're willing to just trash the archives and start >> over; the lists aren't live anyway. I'd like to know who would >> be really adversely affected by this problem. RBP> What good is an incomplete archive? I feel that it is very RBP> important that the archive is a true and complete record of RBP> the list activity, including mesages gated in from a RBP> newsgroup. Maybe I phrased the question incorrectly. If you have not yet begun to archive a gated list, but only start doing so after you install 1.0b11 (which will be released sometime this morning), you will be fine. If you are running 1.0b10 or earlier, and have already started archiving a gated group, your archives will be messed up (if you haven't already noticed ;-). Someone would have to write a script to jam in the Unixfrom headers in the .mbox files and then rerun the script. It's probably not hard to write -- I'm just proposing that I don't need to do it, 'cause the number of people affect approaches zero right now. ;-) -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 16:00:46 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 11:00:46 -0500 (EST) Subject: [Mailman-Developers] Usenet gating and archiving References: <199904030918.DAA30599@mail.indiansprings.org> Message-ID: <14086.15150.168254.950818@anthem.cnri.reston.va.us> >>>>> "BBT" == Benjamin B Thomas writes: BBT> We have a number of people who choose to interact via our BBT> local Usenet groups, and it is important that their BBT> contributions are archived. Without the ability to do so, I BBT> will need to stay with our current setup (icky as it is from BBT> an administrative standpoint, it does what I need) instead of BBT> moving to Mailman. Then you'll definitely want to install 1.0b11. It should all work fine in that release (I'm testing it now on some internal lists, and it looks pretty good). I think I was probably not very clear in my message (I was rushed to leave). The problem /only/ affects you if you are running something earlier than 1.0b11 (to be released in a few minutes) and are already archiving a gated list. Any new lists you start gating after installing 1.0b11 will work just fine. BBT> Let me just say that Mailman is a wonderful piece of BBT> software. I have poked at it a little bit on a test BBT> installation, and it is beautifully conceived and BBT> implemented. Thanks very much! -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 16:13:52 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 11:13:52 -0500 (EST) Subject: [Mailman-Developers] mailpasswds issues with multiple domains References: <14082.20521.113988.624234@anthem.cnri.reston.va.us> Message-ID: <14086.15936.364277.751103@anthem.cnri.reston.va.us> >>>>> "JH" == Jeff Hahn writes: JH> I noticed on Wednesday that mailpasswds doesn't handle JH> multiple domains very gracefully. JH> I'm going to try to get it cleaned up where it lists the JH> "default" server in the subject line, listname AND domain in JH> the individual list lines, etc. JH> Is this an issue for other people? In other words, should I JH> make up a set of clean diff's and submit them for inclusion in JH> the distribution? To where? Greg Stein would love you for it! If you could generate diffs against the CVS snapshot, you can send them to mailman-developers and I'll try to add them before the 1.0 release. -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Apr 3 16:36:33 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 11:36:33 -0500 (EST) Subject: [Mailman-Developers] Release 1.0b11 Message-ID: <14086.17297.485997.392346@anthem.cnri.reston.va.us> Okay folks, 1.0b11 is now available at www.list.org. This is basically a bug fix release addressing problems with case-preserving addresses and archiving of Usenet gated newsgroups. For you hardcore debugging types, there's a new script called bin/withlist which you can run like so: % cd ~mailman % python -i bin/withlist mylist Loading list: mylist (unlocked) >>> m.members {'bwarsaw@cnri.reston.va.us': 0} >>> withlist leaves you with a global variable `m' which is the MailList object you opened. Give withlist and optional second argument if you want the list to be locked. A note about upgrading. I had to bump the DATA_FILE_VERSION number so that the config.db got updated to deal with case-preserving addresses in some situation. I've been running this on python.org for a few days now and it all seems to work, but please keep an eye out for anything strange with your config.db file. Enjoy, -Barry From Gergely Madarasz Sat Apr 3 17:14:18 1999 From: Gergely Madarasz (Gergely Madarasz) Date: Sat, 3 Apr 1999 19:14:18 +0200 (METDST) Subject: [Mailman-Developers] Re: [Mailman-Users] Release 1.0b11 In-Reply-To: <14086.17297.485997.392346@anthem.cnri.reston.va.us> Message-ID: On Sat, 3 Apr 1999, Barry A. Warsaw wrote: > Okay folks, 1.0b11 is now available at www.list.org. This is basically > a bug fix release addressing problems with case-preserving addresses and > archiving of Usenet gated newsgroups. For you hardcore debugging types, I have just tried it, no problems so far. A debian package will be shortly uploaded to the debian master server... I have one suggestion though. The update script should check if the previous version already has the new options.html and not warn about it if it does... -- Madarasz Gergely gorgo@caesar.elte.hu gorgo@linux.rulez.org It's practically impossible to look at a penguin and feel angry. Egy pingvinre gyakorlatilag lehetetlen haragosan nezni. HuLUG: http://mlf.linux.rulez.org/ From bruce@perens.com Sat Apr 3 20:58:53 1999 From: bruce@perens.com (bruce@perens.com) Date: 3 Apr 1999 20:58:53 -0000 Subject: [Mailman-Developers] mailpasswds issues with multiple domains Message-ID: <19990403205853.24211.qmail@perens.com> From: Jeff Hahn > Is this an issue for other people? In other words, should I make up a set > of clean diff's and submit them for inclusion in the distribution? To > where? Yes. I'm running mine in multiple domains, it would be very handy. Thanks Bruce From Jeff Hahn Sun Apr 4 00:17:15 1999 From: Jeff Hahn (Jeff Hahn) Date: Sat, 3 Apr 1999 18:17:15 -0600 (CST) Subject: [Mailman-Developers] oops - hit a bug - 1.0b11 Message-ID: just noticed this in my logs from this afternoon - don't know if it's b11 specific... I am able to reproduce the problem by: 1. go to listinfo page 2. hit link for archive (archive restricted to members) 3. enter aaa@bbb.com for user ( any non member ) 4. enter 12345 (or anything else for password) then I get the "oops" page... I don't recall trying to access a restricted archive as a non-member before this, so it may not be b11 specific. I assume private.py should also be trapping the MMNotAMemberError error... -Jeff Apr 03 18:04:13 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin: [----- Mailman Version: 1.0b11 -----] admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/home/mailman/MM/scripts/driver", line 112, in run_main admin: main() admin: File "/home/mailman/MM/Mailman/Cgi/private.py", line 163, in main admin: if not list_name or not isAuthenticated(list_name): admin: File "/home/mailman/MM/Mailman/Cgi/private.py", line 120, in isAuthenticated admin: listobj.ConfirmUserPassword( username, password) admin: File "/home/mailman/MM/Mailman/SecurityManager.py", line 76, in ConfirmUserPassword admin: raise Errors.MMNotAMemberError admin: MMNotAMemberError From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sun Apr 4 03:07:49 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 3 Apr 1999 21:07:49 -0500 (EST) Subject: [Mailman-Developers] oops - hit a bug - 1.0b11 References: Message-ID: <14086.51573.830624.955454@anthem.cnri.reston.va.us> >>>>> "JH" == Jeff Hahn writes: JH> just noticed this in my logs from this afternoon - don't know JH> if it's b11 specific... JH> I am able to reproduce the problem by: | 1. go to listinfo page | 2. hit link for archive (archive restricted to members) | 3. enter aaa@bbb.com for user ( any non member ) | 4. enter 12345 (or anything else for password) JH> then I get the "oops" page... I don't recall trying to access JH> a restricted archive as a non-member before this, so it may JH> not be b11 specific. I assume private.py should also be JH> trapping the MMNotAMemberError error... Correct. Here's a patch, thanks for the report! -Barry -------------------- snip snip -------------------- Index: private.py =================================================================== RCS file: /projects/cvsroot/mailman/Mailman/Cgi/private.py,v retrieving revision 1.11 retrieving revision 1.12 diff -c -r1.11 -r1.12 *** private.py 1999/03/29 23:53:57 1.11 --- private.py 1999/04/04 02:06:58 1.12 *************** *** 118,124 **** raise SystemExit try: listobj.ConfirmUserPassword( username, password) ! except (Errors.MMBadUserError, Errors.MMBadPasswordError): return 0 token = `hash(list_name)` --- 118,125 ---- raise SystemExit try: listobj.ConfirmUserPassword( username, password) ! except (Errors.MMBadUserError, Errors.MMBadPasswordError, ! Errors.MMNotAMemberError): return 0 token = `hash(list_name)` From jeffh@streek.com Sun Apr 4 16:22:33 1999 From: jeffh@streek.com (Jeff Hahn) Date: Sun, 4 Apr 1999 10:22:33 -0500 (CDT) Subject: [Mailman-Developers] changes to mailpasswd to support multiple domains Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1523646986-1305930720-923239353=:8555 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Attached is a patch to cron/mailpasswds and templates/cronpass.txt to support multiple domains in the monthly password reminder. Patch is against latest CVS sources (1.0b11) WARNING: Apply with care! I'm just getting familiar with Python and Mailman so I could have made some really idiotic mistakes, but it works here... To Apply: cd /usr/src/mailman ("main" source directory) patch -p1 -b Content-Description: ZGlmZiAtYyAtciBNTS5vcmlnL2Nyb24vbWFpbHBhc3N3ZHMgTU0vY3Jvbi9t YWlscGFzc3dkcw0KKioqIE1NLm9yaWcvY3Jvbi9tYWlscGFzc3dkcwlTYXQg QXByICAzIDA5OjE4OjE5IDE5OTkNCi0tLSBNTS9jcm9uL21haWxwYXNzd2Rz CVN1biBBcHIgIDQgMTA6MDA6MjQgMTk5OQ0KKioqKioqKioqKioqKioqDQoq KiogNTEsNzkgKioqKg0KICANCiAgICAgIFRoZSBsaXN0IGNhbiBiZSBhbnkg cmFuZG9tIG9uZSAtIGl0IGlzIG9ubHkgdXNlZCBmb3IgdGhlIG1lc3NhZ2UN CiAgICAgIGRlbGl2ZXJ5IG1lY2hhbmlzbS4iIiINCiEgICAgIHN1YmogPSAn JXMgbWFpbGxpc3QgbWVtYmVyc2hpcHMgcmVtaW5kZXJcbicgJSBsaXN0Lmhv c3RfbmFtZQ0KICAgICAgY291bnQgPSBQQVVTRV9GUkVRVUVOQ1kNCiAgICAg IGZvciB1c2VyLCBkYXRhIGluIHVzZXJzLml0ZW1zKCk6DQohIAl0YWJsZSA9 IFtdDQohIAlmb3IgbCwgcCwgdSBpbiBkYXRhOg0KISAJICAgIGlmIGxlbihs KSA+IDk6DQohIAkJdGFibGUuYXBwZW5kKCIlc1xuICAgICAgICAgICAlLTEw c1xuJXNcbiIgJSAobCwgcCwgdSkpDQohIAkgICAgZWxzZToNCiEgCQl0YWJs ZS5hcHBlbmQoIiUtMTBzICUtMTBzXG4lc1xuIiAlIChsLCBwLCB1KSkNCiEg CWhlYWRlciA9ICgiJS0xMHMgJS0xMHNcbiUtMTBzICUtMTBzIg0KISAJCSAg JSAoIkxpc3QiLCAiUGFzc3dvcmQgLy8gVVJMIiwgIi0tLS0iLCAiLS0tLS0t LS0iKSkNCiAgICAgICAgICB0ZXh0ID0gVXRpbHMubWFrZXRleHQoDQogICAg ICAgICAgICAgICdjcm9ucGFzcy50eHQnLA0KISAgICAgICAgICAgICB7J2hv c3RuYW1lJzogbGlzdC5ob3N0X25hbWUsDQogICAgICAgICAgICAgICAndXNl cicgICAgOiB1c2VyLA0KISAgICAgICAgICAgICAgJ29uZV9saXN0JzogbCwN CiAgICAgICAgICAgICAgIH0pDQogICAgICAgICAgIyBhZGQgdGhpcyB0byB0 aGUgZW5kIHNvIGl0IGRvZXNuJ3QgZ2V0IHdyYXBwZWQvZmlsbGVkDQogICAg ICAgICAgdGV4dCA9IHRleHQgKyBoZWFkZXIgKyAnXG4nICsgc3RyaW5nLmpv aW4odGFibGUsICdcbicpDQohICAgIAlsaXN0LlNlbmRUZXh0VG9Vc2VyKHN1 YmplY3QgPSBzdWJqLA0KISAgICAJCQkgICAgcmVjaXBpZW50ID0gdXNlciwN CiEgICAgCQkJICAgIHRleHQgPSB0ZXh0LA0KISAgCQkJICAgIHNlbmRlciA9 IG1tX2NmZy5NQUlMTUFOX09XTkVSLA0KICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgYWRkX2hlYWRlcnMgPSBbIlgtTm8tQXJjaGl2ZTogeWVzIiwN CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICJQcmVjZWRlbmNlOiBidWxrIl0pDQogICAgICAgICAgY291bnQgPSBjb3Vu dCAtIDENCi0tLSA1MSw4MiAtLS0tDQogIA0KICAgICAgVGhlIGxpc3QgY2Fu IGJlIGFueSByYW5kb20gb25lIC0gaXQgaXMgb25seSB1c2VkIGZvciB0aGUg bWVzc2FnZQ0KICAgICAgZGVsaXZlcnkgbWVjaGFuaXNtLiIiIg0KISAgICAg ZGVmYXVsdF9ob3N0ID0gbW1fY2ZnLkRFRkFVTFRfSE9TVF9OQU1FDQohICAg ICBtYWlsbWFuX293bmVyID0gbW1fY2ZnLk1BSUxNQU5fT1dORVINCiEgICAg IHN1YmogPSAnJXMgbWFpbGxpc3QgbWVtYmVyc2hpcHMgcmVtaW5kZXJcbicg JSBkZWZhdWx0X2hvc3QNCiAgICAgIGNvdW50ID0gUEFVU0VfRlJFUVVFTkNZ DQogICAgICBmb3IgdXNlciwgZGF0YSBpbiB1c2Vycy5pdGVtcygpOg0KISAg ICAgICAgIHRhYmxlID0gW10NCiEgICAgICAgICBmb3IgbCwgciwgcCwgdSBp biBkYXRhOg0KISAgICAgICAgICAgICBpZiBsZW4obCkgPiAzOToNCiEgICAg ICAgICAgICAgICAgIHRhYmxlLmFwcGVuZCgiJXNcbiAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgJS0xMHNcbiVzXG4iICUgKGws IHAsIHUpKQ0KISAgICAgICAgICAgICBlbHNlOg0KISAgICAgICAgICAgICAg ICAgdGFibGUuYXBwZW5kKCIlLTQwcyAlLTEwc1xuJXNcbiIgJSAobCwgcCwg dSkpDQohICAgICAgICAgaGVhZGVyID0gKCIlLTQwcyAlLTEwc1xuJS00MHMg JS0xMHMiDQohICAgICAgICAgICAgICAgICAgICAlICgiTGlzdCIsICJQYXNz d29yZCAvLyBVUkwiLCAiLS0tLSIsICItLS0tLS0tLSIpKQ0KICAgICAgICAg IHRleHQgPSBVdGlscy5tYWtldGV4dCgNCiAgICAgICAgICAgICAgJ2Nyb25w YXNzLnR4dCcsDQohICAgICAgICAgICAgIHsnZGVmX2hvc3QnOiBkZWZhdWx0 X2hvc3QsDQogICAgICAgICAgICAgICAndXNlcicgICAgOiB1c2VyLA0KISAg ICAgICAgICAgICAgJ2V4X3JlcScgIDogciwNCiEgICAgICAgICAgICAgICdt bV9vd25lcic6IG1haWxtYW5fb3duZXIsDQogICAgICAgICAgICAgICB9KQ0K ICAgICAgICAgICMgYWRkIHRoaXMgdG8gdGhlIGVuZCBzbyBpdCBkb2Vzbid0 IGdldCB3cmFwcGVkL2ZpbGxlZA0KICAgICAgICAgIHRleHQgPSB0ZXh0ICsg aGVhZGVyICsgJ1xuJyArIHN0cmluZy5qb2luKHRhYmxlLCAnXG4nKQ0KISAg ICAgICAgIGxpc3QuU2VuZFRleHRUb1VzZXIoc3ViamVjdCA9IHN1YmosDQoh ICAgICAgICAgICAgICAgICAgICAgICAgICAgICByZWNpcGllbnQgPSB1c2Vy LA0KISAgICAgICAgICAgICAgICAgICAgICAgICAgICAgdGV4dCA9IHRleHQs DQohICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzZW5kZXIgPSBtYWls bWFuX293bmVyLA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgYWRk X2hlYWRlcnMgPSBbIlgtTm8tQXJjaGl2ZTogeWVzIiwNCiAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICJQcmVjZWRlbmNl OiBidWxrIl0pDQogICAgICAgICAgY291bnQgPSBjb3VudCAtIDENCioqKioq KioqKioqKioqKg0KKioqIDg3LDExOSAqKioqDQogICAgICB0aGUgdXNlciBh IHNpbmdsZSBtZXNzYWdlIHdpdGggdGhlIGluZm8gZm9yIGFsbCB0aGVpciBs aXN0cyBvbiB0aGlzDQogICAgICBzaXRlLiIiIg0KICAgICAgbGlzdCA9IE5v bmUNCiEgICAgIHVzZXJzID0ge30JCQkJIyB1c2VyOiAobGlzdG5hbWUsIHBh c3N3b3JkLCB1cmwpDQogICAgICAjIENvbnN0cmFpbiB0byBzcGVjaWZpZWQg dXNlcnMsIGlmIGFueS4NCiAgICAgIGNvbmZpbmVkX3RvID0gYXJnc1sxOl0N CiAgICAgIGFfcHVibGljX2xpc3QgPSBOb25lDQogICAgICBmb3IgbmFtZSBp biBVdGlscy5saXN0X25hbWVzKCk6DQohIAlsaXN0ID0gTWFpbExpc3QuTWFp bExpc3QobmFtZSwgbG9jayA9IDApDQogICAgICAgICAgaWYgbm90IGFfcHVi bGljX2xpc3QgYW5kIGxpc3QuYWR2ZXJ0aXNlZDoNCiAgICAgICAgICAgICAg YV9wdWJsaWNfbGlzdCA9IGxpc3QNCiEgCWxpc3RfbmFtZSA9IGxpc3QucmVh bF9uYW1lDQohIAl1bWJyZWxsYV9saXN0ID0gbGlzdC51bWJyZWxsYV9saXN0 DQohIAlpZiBub3QgbGlzdC5zZW5kX3JlbWluZGVyczoNCiEgCSAgICBjb250 aW51ZQ0KISAJZm9yIHVzZXIsIHBhc3N3b3JkIGluIGxpc3QucGFzc3dvcmRz Lml0ZW1zKCk6DQogICAgICAgICAgICAgIGlmIGNvbmZpbmVkX3RvOg0KICAg ICAgICAgICAgICAgICAgaWYgdXNlciBub3QgaW4gY29uZmluZWRfdG86DQog ICAgICAgICAgICAgICAgICAgICAgY29udGludWUNCiAgICAgICAgICAgICAg ICAgIGVsc2U6DQogICAgICAgICAgICAgICAgICAgICAgIyBXZSdyZSBhIGJp dCB2ZXJib3NlIHdoZW4gb3BlcmF0aW5nICJjb25maW5lZF90byI6DQogICAg ICAgICAgICAgICAgICAgICAgcHJpbnQgIiVzIGluICVzIiAlICh1c2VyLCBs aXN0LnJlYWxfbmFtZSkNCiEgCSAgICB1cmwgPSBsaXN0LkdldEFic29sdXRl T3B0aW9uc1VSTCh1c2VyKQ0KICAgICAgICAgICAgICByZWNpcGllbnQgPSBs aXN0LkdldE1lbWJlckFkbWluRW1haWwodXNlcikNCiEgCSAgICBpZiB1c2Vy cy5oYXNfa2V5KHJlY2lwaWVudCk6DQohIAkJdXNlcnNbcmVjaXBpZW50XS5h cHBlbmQobGlzdF9uYW1lLCBwYXNzd29yZCwgdXJsKQ0KISAJICAgIGVsc2U6 DQohIAkJdXNlcnNbcmVjaXBpZW50XSA9IFsobGlzdF9uYW1lLCBwYXNzd29y ZCwgdXJsKV0NCiAgICAgIGlmIGxpc3Q6DQohIAlNYWlsQWxsUGFzc3dvcmRz KGFfcHVibGljX2xpc3Qgb3IgbGlzdCwgdXNlcnMpDQogIA0KICBkZWYgd2Fp dGFsbCgpOg0KICAgICAgIiIiUmV0dXJuIG9ubHkgd2hlbiB0aGVyZSBhcmUg bm8gZm9ya2VkIHN1YnByb2Nlc3NlcyBydW5uaW5nLiIiIg0KLS0tIDkwLDEy NSAtLS0tDQogICAgICB0aGUgdXNlciBhIHNpbmdsZSBtZXNzYWdlIHdpdGgg dGhlIGluZm8gZm9yIGFsbCB0aGVpciBsaXN0cyBvbiB0aGlzDQogICAgICBz aXRlLiIiIg0KICAgICAgbGlzdCA9IE5vbmUNCiEgICAgIHVzZXJzID0ge30J CSMgdXNlcjogKGxpc3QgYWRkcmVzcywgcmVxdWVzdCBhZGRyZXNzLCBwYXNz d29yZCwgdXJsKQ0KICAgICAgIyBDb25zdHJhaW4gdG8gc3BlY2lmaWVkIHVz ZXJzLCBpZiBhbnkuDQogICAgICBjb25maW5lZF90byA9IGFyZ3NbMTpdDQog ICAgICBhX3B1YmxpY19saXN0ID0gTm9uZQ0KICAgICAgZm9yIG5hbWUgaW4g VXRpbHMubGlzdF9uYW1lcygpOg0KISAgICAgICAgIGxpc3QgPSBNYWlsTGlz dC5NYWlsTGlzdChuYW1lLCBsb2NrID0gMCkNCiAgICAgICAgICBpZiBub3Qg YV9wdWJsaWNfbGlzdCBhbmQgbGlzdC5hZHZlcnRpc2VkOg0KICAgICAgICAg ICAgICBhX3B1YmxpY19saXN0ID0gbGlzdA0KISAgICAgICAgIGxpc3RfYWRk cmVzcyA9IGxpc3QuR2V0TGlzdEVtYWlsKCkNCiEgICAgICAgICBsaXN0X3Jl cXVlc3QgPSBsaXN0LkdldFJlcXVlc3RFbWFpbCgpDQohICAgICAgICAgdW1i cmVsbGFfbGlzdCA9IGxpc3QudW1icmVsbGFfbGlzdA0KISAgICAgICAgIGlm IG5vdCBsaXN0LnNlbmRfcmVtaW5kZXJzOg0KISAgICAgICAgICAgICBjb250 aW51ZQ0KISAgICAgICAgIGZvciB1c2VyLCBwYXNzd29yZCBpbiBsaXN0LnBh c3N3b3Jkcy5pdGVtcygpOg0KICAgICAgICAgICAgICBpZiBjb25maW5lZF90 bzoNCiAgICAgICAgICAgICAgICAgIGlmIHVzZXIgbm90IGluIGNvbmZpbmVk X3RvOg0KICAgICAgICAgICAgICAgICAgICAgIGNvbnRpbnVlDQogICAgICAg ICAgICAgICAgICBlbHNlOg0KICAgICAgICAgICAgICAgICAgICAgICMgV2Un cmUgYSBiaXQgdmVyYm9zZSB3aGVuIG9wZXJhdGluZyAiY29uZmluZWRfdG8i Og0KICAgICAgICAgICAgICAgICAgICAgIHByaW50ICIlcyBpbiAlcyIgJSAo dXNlciwgbGlzdC5yZWFsX25hbWUpDQohICAgICAgICAgICAgIHVybCA9IGxp c3QuR2V0QWJzb2x1dGVPcHRpb25zVVJMKHVzZXIpDQogICAgICAgICAgICAg IHJlY2lwaWVudCA9IGxpc3QuR2V0TWVtYmVyQWRtaW5FbWFpbCh1c2VyKQ0K ISAgICAgICAgICAgICBpZiB1c2Vycy5oYXNfa2V5KHJlY2lwaWVudCk6DQoh ICAgICAgICAgICAgICAgICB1c2Vyc1tyZWNpcGllbnRdLmFwcGVuZChsaXN0 X2FkZHJlc3MsIGxpc3RfcmVxdWVzdCwgDQohICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHBhc3N3 b3JkLCB1cmwpDQohICAgICAgICAgICAgIGVsc2U6DQohICAgICAgICAgICAg ICAgICB1c2Vyc1tyZWNpcGllbnRdID0gWyhsaXN0X2FkZHJlc3MsIGxpc3Rf cmVxdWVzdCwgDQohICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgIHBhc3N3b3JkLCB1cmwpXQ0KICAg ICAgaWYgbGlzdDoNCiEgICAgICAgICBNYWlsQWxsUGFzc3dvcmRzKGFfcHVi bGljX2xpc3Qgb3IgbGlzdCwgdXNlcnMpDQogIA0KICBkZWYgd2FpdGFsbCgp Og0KICAgICAgIiIiUmV0dXJuIG9ubHkgd2hlbiB0aGVyZSBhcmUgbm8gZm9y a2VkIHN1YnByb2Nlc3NlcyBydW5uaW5nLiIiIg0KZGlmZiAtYyAtciBNTS5v cmlnL3RlbXBsYXRlcy9jcm9ucGFzcy50eHQgTU0vdGVtcGxhdGVzL2Nyb25w YXNzLnR4dA0KKioqIE1NLm9yaWcvdGVtcGxhdGVzL2Nyb25wYXNzLnR4dAlT YXQgQXByICAzIDA5OjE4OjI4IDE5OTkNCi0tLSBNTS90ZW1wbGF0ZXMvY3Jv bnBhc3MudHh0CVN1biBBcHIgIDQgMDg6MDc6MzggMTk5OQ0KKioqKioqKioq KioqKioqDQoqKiogMSw0ICoqKioNCiEgVGhpcyBpcyBhIHJlbWluZGVyLCBz ZW50IG91dCBvbmNlIGEgbW9udGgsIGFib3V0IHlvdXIgJShob3N0bmFtZSlz DQogIG1haWxpbmcgbGlzdCBtZW1iZXJzaGlwcy4gIEl0IGluY2x1ZGVzIHlv dXIgc3Vic2NyaXB0aW9uIGluZm8gYW5kDQogIGhvdyB0byB1c2UgaXQgdG8g Y2hhbmdlIGl0IG9yIHVuc3Vic2NyaWJlIGZyb20gYSBsaXN0Lg0KICANCi0t LSAxLDQgLS0tLQ0KISBUaGlzIGlzIGEgcmVtaW5kZXIsIHNlbnQgb3V0IG9u Y2UgYSBtb250aCwgYWJvdXQgeW91ciAlKGRlZl9ob3N0KXMNCiAgbWFpbGlu ZyBsaXN0IG1lbWJlcnNoaXBzLiAgSXQgaW5jbHVkZXMgeW91ciBzdWJzY3Jp cHRpb24gaW5mbyBhbmQNCiAgaG93IHRvIHVzZSBpdCB0byBjaGFuZ2UgaXQg b3IgdW5zdWJzY3JpYmUgZnJvbSBhIGxpc3QuDQogIA0KKioqKioqKioqKioq KioqDQoqKiogOCwxOCAqKioqDQogIA0KICBJbiBhZGRpdGlvbiB0byB0aGUg VVJMIGludGVyZmFjZXMsIHlvdSBjYW4gYWxzbyB1c2UgZW1haWwgdG8gbWFr ZSBzdWNoDQogIGNoYW5nZXMuICBGb3IgbW9yZSBpbmZvLCBzZW5kIGEgbWVz c2FnZSB0byB0aGUgJy1yZXF1ZXN0JyBhZGRyZXNzIG9mDQohIHRoZSBsaXN0 IChmb3IgZXhhbXBsZSwgJShvbmVfbGlzdClzLXJlcXVlc3RAJShob3N0bmFt ZSlzKSBjb250YWluaW5nDQogIGp1c3QgdGhlIHdvcmQgJ2hlbHAnIGluIHRo ZSBtZXNzYWdlIGJvZHksIGFuZCBhbiBlbWFpbCBtZXNzYWdlIHdpbGwgYmUN CiAgc2VudCB0byB5b3Ugd2l0aCBpbnN0cnVjdGlvbnMuDQogIA0KICBJZiB5 b3UgaGF2ZSBxdWVzdGlvbnMsIHByb2JsZW1zLCBjb21tZW50cywgZXRjLCBz ZW5kIHRoZW0gdG8NCiEgbWFpbG1hbi1vd25lckAlKGhvc3RuYW1lKXMuICBU aGFua3MhDQogIA0KICBQYXNzd29yZHMgZm9yICUodXNlcilzOg0KLS0tIDgs MTkgLS0tLQ0KICANCiAgSW4gYWRkaXRpb24gdG8gdGhlIFVSTCBpbnRlcmZh Y2VzLCB5b3UgY2FuIGFsc28gdXNlIGVtYWlsIHRvIG1ha2Ugc3VjaA0KICBj aGFuZ2VzLiAgRm9yIG1vcmUgaW5mbywgc2VuZCBhIG1lc3NhZ2UgdG8gdGhl ICctcmVxdWVzdCcgYWRkcmVzcyBvZg0KISB0aGUgbGlzdCAoZm9yIGV4YW1w bGUsICUoZXhfcmVxKXMpIGNvbnRhaW5pbmcNCiAganVzdCB0aGUgd29yZCAn aGVscCcgaW4gdGhlIG1lc3NhZ2UgYm9keSwgYW5kIGFuIGVtYWlsIG1lc3Nh Z2Ugd2lsbCBiZQ0KICBzZW50IHRvIHlvdSB3aXRoIGluc3RydWN0aW9ucy4N CiAgDQogIElmIHlvdSBoYXZlIHF1ZXN0aW9ucywgcHJvYmxlbXMsIGNvbW1l bnRzLCBldGMsIHNlbmQgdGhlbSB0bw0KISAlKG1tX293bmVyKXMuICBUaGFu a3MhDQogIA0KICBQYXNzd29yZHMgZm9yICUodXNlcilzOg0KKyANCg== --1523646986-1305930720-923239353=:8555-- From bryner@uiuc.edu Mon Apr 5 18:14:17 1999 From: bryner@uiuc.edu (Brian Ryner) Date: Mon, 05 Apr 1999 12:14:17 -0500 Subject: [Mailman-Developers] Envelope sender and list-admin address Message-ID: <3708EF69.991A02A@uiuc.edu> Hi- I reported a bug on this but I thought I'd also post here, becuause I might try to correct this myself (and any advice would be appreciated). Basically, when a message is sent to the admin address (i.e. mailman-developers-admin@python.org), the envelope sender is left untouched when the message is resent. I don't think this is a good idea. If an address on the admin list is not on the local host, and the email is not sent from the local host, then you basically have a message from a non-local address to a non-local address, which is a no-no in many anti-spam-relaying setups. It would make much more sense to set the envelope sender to the list-admin address. -- -Brian Ryner bryner@uiuc.edu From Harald.Meland@usit.uio.no Tue Apr 6 15:26:28 1999 From: Harald.Meland@usit.uio.no (Harald Meland) Date: 06 Apr 1999 16:26:28 +0200 Subject: [Mailman-Developers] exim - Failure to exec script- gid question In-Reply-To: nbecker@fred.net's message of "30 Mar 1999 13:37:19 -0500" References: Message-ID: [nbecker@fred.net] > I'm using mailman-1.0b10 + exim-2.10. > > Mar 30 13:10:08 nbeckerpc Mailman mail-wrapper: Failure to exec script. WANTED gid 12, GOT gid 99. (Reconfigure to take 99?) > > I can reconfigure mailman or exim to set the gid, but why is it needed > at all? Since wrapper is sgid, why does it care what gid was used to > invoke it? Just additional security check? Yes, it's "merely" a sanity check :) -- Harald From dan@feld.cvut.cz Mon Apr 12 16:45:19 1999 From: dan@feld.cvut.cz (Dan Ohnesorg) Date: Mon, 12 Apr 1999 17:45:19 +0200 (CEST) Subject: [Mailman-Developers] Hypermail Message-ID: I have troubles with hypermail archiver. On some ocasions it makes bad references between index page and articles, as you can see on http://poli.feld.cvut.cz/archives/public/kecy/1999-March/date.html 3-9 artiles from end are under one link. It is the most bad fall, but on other archives ot makes also too. It is version 1.0b10. BTW I will made templates for archives instead of static strings. Has it someone made alredy? cheers dan From claw@kanga.nu Mon Apr 12 17:35:18 1999 From: claw@kanga.nu (claw@kanga.nu) Date: Mon, 12 Apr 1999 09:35:18 -0700 Subject: [Mailman-Developers] Hypermail In-Reply-To: Message from Dan Ohnesorg of "Mon, 12 Apr 1999 17:45:19 +0200." Message-ID: On Mon, 12 Apr 1999 17:45:19 +0200 (CEST) Dan Ohnesorg wrote: > I have troubles with hypermail archiver. I strongly suggest you look at MHonArc (http://www.oac.uci.edu/indiv/ehood/mhonarc.doc.html). It has far better MIME support, is significantly more configurable, etc etc etc yada yada. -- J C Lawrence Internet: claw@kanga.nu ----------(*) Internet: coder@kanga.nu ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith... From dan@feld.cvut.cz Mon Apr 12 17:43:37 1999 From: dan@feld.cvut.cz (Dan Ohnesorg) Date: Mon, 12 Apr 1999 18:43:37 +0200 (CEST) Subject: [Mailman-Developers] Hypermail In-Reply-To: Message-ID: On Mon, 12 Apr 1999 claw@kanga.nu wrote: > On Mon, 12 Apr 1999 17:45:19 +0200 (CEST) > Dan Ohnesorg wrote: > > > I have troubles with hypermail archiver. > > I strongly suggest you look at MHonArc > (http://www.oac.uci.edu/indiv/ehood/mhonarc.doc.html). It has far > better MIME support, is significantly more configurable, etc etc > etc yada yada. Yes, I know, but it is nice on hypermail that it can be trigered directly from mailman. When I will use another archiving tool, it must be runed from crontab. Is is from my point of view bad, becouse on not loaded lists is archiving tool runned too often and system overhead is big, or too only sometimes and the archive is out of sync with list. What would developers say to method in mailman like start archiving? It is probably not good idea. Or to make generic inteface like os.exec(archiver,message is on stdin) ???? cheers dan From troy@akropolys.com Mon Apr 12 18:07:51 1999 From: troy@akropolys.com (Troy Morrison) Date: Mon, 12 Apr 1999 10:07:51 -0700 (PDT) Subject: [Mailman-Developers] Hypermail In-Reply-To: Message-ID: | Yes, I know, but it is nice on hypermail that it can be trigered directly | from mailman. When I will use another archiving tool, it must be runed | from crontab. Is is from my point of view bad, becouse on not loaded lists | is archiving tool runned too often and system overhead is big, or too only | sometimes and the archive is out of sync with list. I could be wrong (I downloaded mhonarc, but haven't really set it up to run with mailman), but doesn't mhonarc use "-add" to add a single message to the archives? Could you trigger that directly from mailman? Troy From lindsey@ncsa.uiuc.edu Mon Apr 12 18:16:58 1999 From: lindsey@ncsa.uiuc.edu (Christopher Lindsey) Date: Mon, 12 Apr 1999 12:16:58 -0500 (CDT) Subject: [Mailman-Developers] Hypermail In-Reply-To: from "Troy Morrison" at Apr 12, 99 10:07:51 am Message-ID: <199904121716.MAA25202@ferret.ncsa.uiuc.edu> > I could be wrong (I downloaded mhonarc, but haven't really set it up to > run with mailman), but doesn't mhonarc use "-add" to add a single message > to the archives? > > Could you trigger that directly from mailman? What I've done is subscribe a "user" to my mailman lists. That user then has a procmailrc file that calls mailman with a -add flag to auto-update the MHonArc archives. Incidentally, I believe the original question was miscommunicated. Even though they said hypermail archives, the site is most definitely using mailman's builtin pipermail. Chris From dan@feld.cvut.cz Mon Apr 12 18:19:08 1999 From: dan@feld.cvut.cz (Dan Ohnesorg) Date: Mon, 12 Apr 1999 19:19:08 +0200 (CEST) Subject: [Mailman-Developers] Hypermail In-Reply-To: Message-ID: On Mon, 12 Apr 1999, Troy Morrison wrote: > > | Yes, I know, but it is nice on hypermail that it can be trigered directly > | from mailman. When I will use another archiving tool, it must be runed > | from crontab. Is is from my point of view bad, becouse on not loaded lists > | is archiving tool runned too often and system overhead is big, or too only > | sometimes and the archive is out of sync with list. > > I could be wrong (I downloaded mhonarc, but haven't really set it up to > run with mailman), but doesn't mhonarc use "-add" to add a single message > to the archives? > > Could you trigger that directly from mailman? > > Troy Yes, the problem is, i can atach archiver on alias like list: |archiver, |listserv So can be attached any archiver to any list and is trigered only with incoming message. Problem is, that some messages are not send by listserv, becouse they are from spamming domain, contaist only commands for listserv etc. So the archive doesn't containts that what was send by listserv. Second is make archiver a listmember. Not bad, but message can spend many hours in mailqueue. It is not a online archiving. Third, my favourite is to call archiver inside listserv. And this can be by mailman complicated. But i will look on it to find some solution. cheers dan From claw@varesearch.com Mon Apr 12 22:15:09 1999 From: claw@varesearch.com (J C Lawrence) Date: Mon, 12 Apr 1999 14:15:09 -0700 Subject: [Mailman-Developers] Hypermail In-Reply-To: Message from Dan Ohnesorg of "Mon, 12 Apr 1999 18:43:37 +0200." Message-ID: On Mon, 12 Apr 1999 18:43:37 +0200 (CEST) Dan Ohnesorg wrote: > On Mon, 12 Apr 1999 claw@kanga.nu wrote: >> I strongly suggest you look at MHonArc >> (http://www.oac.uci.edu/indiv/ehood/mhonarc.doc.html). It has >> far better MIME support, is significantly more configurable, etc >> etc etc yada yada. > Yes, I know, but it is nice on hypermail that it can be trigered > directly from mailman. When I will use another archiving tool, it > must be runed from crontab. MHonArc can archive a single message piped to sdtin. See the docs for the -add (IIRC) command line option. -- J C Lawrence Internet: claw@kanga.nu ---------(*) Internet: claw@varesearch.com ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith... From grin@tolna.net Fri Apr 16 13:55:11 1999 From: grin@tolna.net (Peter Gervai) Date: Fri, 16 Apr 1999 14:55:11 +0200 Subject: [Mailman-Developers] jitterbug and #12 Message-ID: <19990416145511.C30613@mail.tolna.net> Hello, Out of my curiousity I submitted a bug into the bug database. It got resolved really fast. I only have two problems. First: Maybe it's just me but I don't really see WHO did close the bug. Second: The bug (actually rather a cosmetic problem than a real bug) still exists, and the resolving was unsatisfactory (huh :)) for me, but there is no way to reply to the bug resolver, either because I do not know who he was or because I'm "logged in as a guest user". And about the #12: as the original text told the install overwrites the $BASE/templates directory without warning. Since I localized the templates to be able to create localized lists with newlist I wasn't REALLY happy to learn that all of them got overwritten. Of course lists//templates don't get overwritten, but that's another matter I did not complain about... regards, grin From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Apr 16 15:44:49 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 16 Apr 1999 10:44:49 -0400 (EDT) Subject: [Mailman-Developers] jitterbug and #12 References: <19990416145511.C30613@mail.tolna.net> Message-ID: <14103.19681.690937.619719@anthem.cnri.reston.va.us> >>>>> "PG" == Peter Gervai writes: PG> Out of my curiousity I submitted a bug into the bug database. PG> It got resolved really fast. I only have two problems. PG> First: Maybe it's just me but I don't really see WHO did close PG> the bug. It was me, but apparently Jitterbug doesn't record that information. I'm very new to Jitterbug so maybe I've done something wrong. At this point you can pretty much assume that if something gets resolved, I did it. PG> Second: The bug (actually rather a cosmetic problem than a PG> real bug) still exists, and the resolving was unsatisfactory PG> (huh :)) for me, but there is no way to reply to the bug PG> resolver, either because I do not know who he was or because PG> I'm "logged in as a guest user". Hmm, another Jitterbug deficiency (feature? bug?). I would think guests should be able to continue the conversation about a bug via the database. Since you can't, you've done the right thing by emailing MMDev. PG> And about the #12: as the original text told the install PG> overwrites the $BASE/templates directory without PG> warning. Since I localized the templates to be able to create PG> localized lists with newlist I wasn't REALLY happy to learn PG> that all of them got overwritten. Of course PG> lists//templates don't get overwritten, but that's PG> another matter I did not complain about... Ah, I completely misunderstood your bug report. I've moved this back to incoming so I'll remember to deal with it. I'm not 100% sure what the solution should be though. -Barry From grin@tolna.net Fri Apr 16 15:52:40 1999 From: grin@tolna.net (Peter Gervai) Date: Fri, 16 Apr 1999 16:52:40 +0200 Subject: [Mailman-Developers] jitterbug and #12 In-Reply-To: <14103.19681.690937.619719@anthem.cnri.reston.va.us>; from Barry A. Warsaw on Fri, Apr 16, 1999 at 10:44:49AM -0400 References: <19990416145511.C30613@mail.tolna.net> <14103.19681.690937.619719@anthem.cnri.reston.va.us> Message-ID: <19990416165240.G30613@mail.tolna.net> On Fri, Apr 16, 1999 at 10:44:49AM -0400, Barry A. Warsaw wrote: > PG> Out of my curiousity I submitted a bug into the bug database. > PG> It got resolved really fast. I only have two problems. > > PG> First: Maybe it's just me but I don't really see WHO did close > PG> the bug. > > It was me, It's hard to keep secret that I suspected that. :-)) > PG> And about the #12: as the original text told the install > PG> overwrites the $BASE/templates directory without > PG> warning. Since I localized the templates to be able to create > PG> localized lists with newlist I wasn't REALLY happy to learn > PG> that all of them got overwritten. Of course > PG> lists//templates don't get overwritten, but that's > PG> another matter I did not complain about... > > Ah, I completely misunderstood your bug report. No problem, that's why I tried to reply. > I've moved this back > to incoming so I'll remember to deal with it. I'm not 100% sure what > the solution should be though. Possibility#1: create a backup file/directory when overwriting Possibility#2: keep MD5/CRC/whatever of the 'original' file thus be able to detect whether it was modified or not cya, grin From gonter@maestria.wu-wien.ac.at Sat Apr 17 18:59:18 1999 From: gonter@maestria.wu-wien.ac.at (Gerhard Gonter) Date: Sat, 17 Apr 1999 19:59:18 +0200 (MES) Subject: [Mailman-Developers] Re: [Mailman-Users] Moving Listproc lists In-Reply-To: <4.1.19990417094443.00b43370@pop.nekodojo.org> from Greg Connor at "Apr 17, 99 09:55:40 am" Message-ID: <199904171759.TAA24566@maestria.wu-wien.ac.at> According to Greg Connor: > I did it all by hand on my system... here are the commands I used to > transfer users, as closely as I can remember... Thanks a lot, in the meantime I moved the subscribers of the first few lists (100 more to go :) using a modified add_members: ./add_members --lp6 lists/LIST1/.subscribers list1 Only one file, add_members, had to be modified. This maps ACK, NOACK -> normal subscriptions DIGEST -> digest subscriptions and keeps the original password. Addresses are converted to lower case. I will offer this version to the developers, maybe it will show up in the next version. Right now, POSTPONE'd entries are dropped and the CONCEAL flag is ignored, keeping this information requires modifications in other parts of Mailman. I'm not sure if I'll try that, maybe not... > Also, I had problems subbing more than 20 people at a time; all would get > subbed, but only 20 or so would get welcome messages (containing their new > random password). If you think you might have this problem too, use > something like this instead.. Hmm... Thanks for the hint. The sendmail logs tell me that everyone in a list with 167 members should have received their welcome messages by now, so this might be a bug in other versions. The bug archive didn't mention anything about that. (I'm using 1.0b8, the original add_members was pulled out of CVS yesterday.) +gg -- Gerhard.Gonter@wu-wien.ac.at Fax: +43/1/31336/702 g.gonter@ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria From gonter@maestria.wu-wien.ac.at Tue Apr 20 19:21:54 1999 From: gonter@maestria.wu-wien.ac.at (Gerhard Gonter) Date: Tue, 20 Apr 1999 20:21:54 +0200 (MES) Subject: [Mailman-Developers] automatically generated password too complicated? Message-ID: <199904201821.UAA20318@maestria.wu-wien.ac.at> Some of our users complained about the automatically generated passwords that are sent out when a list is imported or if an admin subscribes someone. Especially the ` and ^ characters are major problem because these may be treated as parts of composite characters in some enviroments (` followed by a might be displayed as the same character as à in HTML) and so on. Also, upper case characters impose an extra mental burden ;) Anyway, I modified our Mailman which now has a function (method?) Utils.GetRandomPassword(length) which generates passwords of the given length with a restricted alphabet, namely: a-x, 2-9, excluding characters o and l as well as digits 0 and 1 which may be confused and y, z (german keyboards swap these, in the past, this cause trouble too ;) I would like to offer this patch unless there are good reasons why this should be avoided. The main concern is certainly a higher risk to crack such passwords (only 30 possibilities instead of 64) but this could easly be matched by using 5 character passwords: possibilities strength --------------------------- 64^4 = 16777216 1 30^4 = 810000 0.05 30^5 = 24300000 1.45 As far as I have seen, this patch involves replacing certain calls to GetRandomSeed in a few places such as: bin/add_members, Mailman/Cgi/admin.py, Mailman/MailCommandHandler.py Any comment? +gg -- Gerhard.Gonter@wu-wien.ac.at Fax: +43/1/31336/702 g.gonter@ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria From gonter@maestria.wu-wien.ac.at Wed Apr 21 18:53:59 1999 From: gonter@maestria.wu-wien.ac.at (Gerhard Gonter) Date: Wed, 21 Apr 1999 19:53:59 +0200 (MES) Subject: [Mailman-Developers] dots in list name -> archive not accessible? Message-ID: <199904211753.TAA23396@maestria.wu-wien.ac.at> Once upon a time, one group of users decided that they need a list called Assistent/Inn/En@wu-wien.ac.at and it took me a while to convince them, that the / would not work so they accepted Assistent.Inn.En@wu-wien.ac.at which worked quite well on Listproc... Today I moved the list, everything went fine except that the archives were not accessible from the list overview page. I tracked this problem down to Mailman/Cgi/private.py where this function is defined, which strips an extension from the directory name: | def getListName(path): | component = string.split(path, os.sep)[1] | root, ext = os.path.splitext(component) | return root If component is returned instead of root, everything seems to be working fine for this list and the other lists without dots in their name. Why should an extension be stripped? Is this a bug, a feature, or something that was left over from VMS times? P.S.: Yesterday I mailed an message about the problems our users have with automatically generated passwords. Neither my collegue nor I seem to have received the article, also, no flames appeared either ;) The article has been archived as http://www.python.org/pipermail/mailman-developers/1999-April/001040.html Did something go wrong with that? +gg -- Gerhard.Gonter@wu-wien.ac.at Fax: +43/1/31336/702 g.gonter@ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria From klm@digicool.com Thu Apr 22 00:52:40 1999 From: klm@digicool.com (Ken Manheimer) Date: Wed, 21 Apr 1999 19:52:40 -0400 Subject: [Mailman-Developers] FW: [Mailman-Users] Still need code info for privacy option Message-ID: <613145F79272D211914B0020AFF640190BEE83@gandalf.digicool.com> I'm sorry i can't help more with this, no time - but mailman-developers is a more appropriate venue for the question, maybe you'll get some other attention there. Context for mailman-developers - setting the "hide the message sender" privacy option doesn't seem to be working, and the code (in MailList.MailList.Post()) doesn't seem to be right - the reply-to is deleted, but the code is setting the address to the list admin, not the list proper. And it's not working anyway - as james d mentions below, wiring it to set the from to something else is not working... Ken Manheimer klm@digicool.com -----Original Message----- From: Nicholson James D [mailto:James.Nicholson@amedd.army.mil] Sent: Tuesday, April 20, 1999 5:17 PM To: Ken Manheimer Cc: mailman-users@python.org Subject: RE: [Mailman-Users] Still need code info for privacy option [Nicholson James D] I found the problem with the list not remailing anonymously. In routine Post(), it deletes the sender and reply-to fields and then sets the from field. However, it set the From field to self.GetAdminEmail. What I needed it to do (and what I believe it should be doing) is setting the From field to self.GetListEmail, which will return the list address. However, I can't get the damned thing to change the From field for anything. I've even done a msg.setheader( 'From', 'listname@machine' ). That's hardwired in the Post() routine just for testing, and it isn't bloody changing the header... at all. I altered the MailList.py file, moved the MailList.pyc to oldMailList.pyc, and it still does the same damned thing. It sets the From field to whoever sent the message. Was I supposed to recompile the package or something to get my changes to take effect? I just don't know python or mailman well enough to know even this. Sorry. -Jim From g.sandrucci@agora.it Thu Apr 22 14:18:19 1999 From: g.sandrucci@agora.it (Gianni Sandrucci) Date: Thu, 22 Apr 1999 15:18:19 +0200 Subject: [Mailman-Developers] Mailman on NT Message-ID: <371F219B.68A236AA@agora.it> I have read some messages about future Mailman NT release. Since I have appreciated Mailman on a IBM AIX system I tried a porting test on NT with following steps: - installed Cygwin 2.0 (www.cygnus.com) - installed Python for Windows with all Windows specific extension - installed Mailman 1.0 b11 - made some minor changes in Mailmal files configure and src/Makefile.in - after some fighting with permissions (I was forced to comment tests on these matters in configuration script and C source code) succeded to ./configure --with-cgi-ext=.exe make install (no errors reported) - configured IIS to create a virtual site on /home/mailman named mailman - called: http://localhost/mailman/cgi-bin/admin.exe Got an error (reported below). It seems Python is not able to locate Mailman modules in /home/mailman/Mailman. However modules are there (in py and pyc format). I tried to go up in erorrs chain but every time the 'driver' script try to import something from Mailman I got the same error. Since I know very little about Python I wonder if anybody can help me. Thanks. ------------------------------------------- Bug in Mailman version 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 (innermost last): File "/home/mailman/scripts/driver", line 135, in print_traceback from Mailman.mm_cfg import VERSION ImportError: No module named Mailman.mm_cfg -------------------------------------------------------------------------------- Environment variables: Variable Value USERPROFILE C:\WINNT\Profiles\Default User HTTP_ACCEPT_ENCODING gzip, deflate REMOTE_HOST 127.0.0.1 HTTPS off OS2LIBPATH C:\WINNT\system32\os2\dll; SERVER_PORT_SECURE 0 SERVER_PORT 80 PATH_TRANSLATED C:\Inetpub\wwwroot PROCESSOR_LEVEL 6 GATEWAY_INTERFACE CGI/1.1 INSTANCE_ID 1 NUMBER_OF_PROCESSORS 1 HTTP_ACCEPT_LANGUAGE en-us PATH c:\agora\servletmanager\jrun\bin;c:\agora\servletmanager\jrun\jre\115\bin;C:\WINNT\system32;C:\WINNT;C:\Program Files\Mts SYSTEMDRIVE C: PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.JS SERVER_NAME localhost HTTP_CONNECTION Keep-Alive PROCESSOR_ARCHITECTURE x86 TERM cygwin WINDIR C:\WINNT HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* COMPUTERNAME SVIL4 INCLUDE C:\Program Files\Mts\Include SYSTEMROOT C:\WINNT SERVER_PROTOCOL HTTP/1.1 PROCESSOR_REVISION 0502 CONTENT_LENGTH 0 HTTP_HOST localhost REQUEST_METHOD GET PROCESSOR_IDENTIFIER x86 Family 6 Model 5 Stepping 2, GenuineIntel PYTHONPATH /home/mailman LOCAL_ADDR 127.0.0.1 SCRIPT_NAME /mailman/cgi-bin/admin.exe SERVER_SOFTWARE Microsoft-IIS/4.0 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 4.01; Windows NT) OS Windows_NT LIB C:\Program Files\Mts\Lib COMSPEC C:\WINNT\system32\cmd.exe REMOTE_ADDR 127.0.0.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [----- Mailman Version: -----] [----- Traceback ------] Traceback (innermost last): File "/home/mailman/scripts/driver", line 135, in print_traceback from Mailman.mm_cfg import VERSION ImportError: No module named Mailman.mm_cfg [----- Environment Variables -----] USERPROFILE: C:\WINNT\Profiles\Default User HTTP_ACCEPT_ENCODING: gzip, deflate REMOTE_HOST: 127.0.0.1 HTTPS: off OS2LIBPATH: C:\WINNT\system32\os2\dll; SERVER_PORT_SECURE: 0 SERVER_PORT: 80 PATH_TRANSLATED: C:\Inetpub\wwwroot PROCESSOR_LEVEL: 6 GATEWAY_INTERFACE: CGI/1.1 INSTANCE_ID: 1 NUMBER_OF_PROCESSORS: 1 HTTP_ACCEPT_LANGUAGE: en-us PATH: c:\agora\servletmanager\jrun\bin;c:\agora\servletmanager\jrun\jre\115\bin;C:\WINNT\system32;C:\WINNT;C:\Program Files\Mts SYSTEMDRIVE: C: PATHEXT: .COM;.EXE;.BAT;.CMD;.VBS;.JS SERVER_NAME: localhost HTTP_CONNECTION: Keep-Alive PROCESSOR_ARCHITECTURE: x86 TERM: cygwin WINDIR: C:\WINNT HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* COMPUTERNAME: SVIL4 INCLUDE: C:\Program Files\Mts\Include SYSTEMROOT: C:\WINNT SERVER_PROTOCOL: HTTP/1.1 PROCESSOR_REVISION: 0502 CONTENT_LENGTH: 0 HTTP_HOST: localhost REQUEST_METHOD: GET PROCESSOR_IDENTIFIER: x86 Family 6 Model 5 Stepping 2, GenuineIntel PYTHONPATH: /home/mailman LOCAL_ADDR: 127.0.0.1 SCRIPT_NAME: /mailman/cgi-bin/admin.exe SERVER_SOFTWARE: Microsoft-IIS/4.0 HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT) OS: Windows_NT LIB: C:\Program Files\Mts\Lib COMSPEC: C:\WINNT\system32\cmd.exe REMOTE_ADDR: 127.0.0.1 From gorgo@caesar.elte.hu Sun Apr 25 21:16:51 1999 From: gorgo@caesar.elte.hu (Gergely Madarasz) Date: Sun, 25 Apr 1999 22:16:51 +0200 (METDST) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 Message-ID: Hello! Mailman does not work with exim and python 1.5.2, probably because of the esmtp support in python 1.5.2's smtplib. Following is a trace from exim. Note that exim gets an ehlo and later a helo which resets it into smtp from esmtp. Please forward this to the appropriate python forums :) set_process_info: 15805 2.11 handling incoming connection from localhost [127.0.0.1] ready for new message smtp_setup_msg entered SMTP<< ehlo darmol.elte.hu sender_fullhost = localhost (darmol.elte.hu) [127.0.0.1] sender_rcvhost = localhost ([127.0.0.1] helo=darmol.elte.hu) set_process_info: 15805 2.11 handling incoming connection from localhost (darmol.elte.hu) [127.0.0.1] 250-darmol.elte.hu Hello localhost [127.0.0.1] 250-SIZE 2000000 250-PIPELINING 250 HELP SMTP<< helo darmol.elte.hu sender_fullhost = localhost (darmol.elte.hu) [127.0.0.1] sender_rcvhost = localhost ([127.0.0.1] helo=darmol.elte.hu) set_process_info: 15805 2.11 handling incoming connection from localhost (darmol.elte.hu) [127.0.0.1] 250 darmol.elte.hu Hello localhost [127.0.0.1] SMTP<< mail FROM: size=1335 LOG: 4 MAIN SMTP syntax error in "mail FROM: size=1335" H=localhost (darmol.elte.hu) [127.0.0.1]: malformed address: size=1335 may not follow 501 size=1335: malformed address: size=1335 may not follow SMTP<< rset 250 Reset OK 421 darmol.elte.hu lost input connection LOG: 4 MAIN SMTP connection from localhost (darmol.elte.hu) [127.0.0.1] lost child 15805 ended -- Madarasz Gergely gorgo@caesar.elte.hu gorgo@linux.rulez.org It's practically impossible to look at a penguin and feel angry. Egy pingvinre gyakorlatilag lehetetlen haragosan nezni. HuLUG: http://mlf.linux.rulez.org/ From dragondm@integral.org Mon Apr 26 17:02:26 1999 From: dragondm@integral.org (The Dragon De Monsyne) Date: Mon, 26 Apr 1999 11:02:26 -0500 (CDT) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 In-Reply-To: Message-ID: On Sun, 25 Apr 1999, Gergely Madarasz wrote: > Hello! > > Mailman does not work with exim and python 1.5.2, probably because of the > esmtp support in python 1.5.2's smtplib. Following is a trace from exim. > Note that exim gets an ehlo and later a helo which resets it into smtp > from esmtp. Please forward this to the appropriate python forums :) Erf, yes,I should have thrown a warning your folx's way (I'm the maintainer of python's smtplib) In 1.5.2 some of the return values of methods have been changed. Before, some of the methods returned integrer codes, some string descriptions, and some (code,desc) tuples. Now they _all_ return tuples (and the exception objects have more meaningful info, too). I'm in the middle of moving now, so I don't have access to a news server that carries c.l.p ATM, and half my equipment is packed. the patch should be simple In Mailman.Utils.TrySMTPDelivery() there is a few lines like: conn = smtplib.SMTP(mm_cfg.SMTPHOST) # Do the EHLO/HELO manually so we can check for DSN support if conn.ehlo() >= 400: conn.helo() change it to: conn = smtplib.SMTP(mm_cfg.SMTPHOST) # Do the EHLO/HELO manually so we can check for DSN support if conn.ehlo()[0] >= 400: conn.helo() (This change was considered resonable, as only code using ESMTP would likely need to call the SMTP command methods, most other code just uses the sendmail() method, and 1.5.1's smtplib didn't support ESMTP, so 1.5.2 was the 'last chance' to regularize the return values ) -The Dragon De Monsyne From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Apr 27 22:35:21 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 27 Apr 1999 17:35:21 -0400 (EDT) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 References: Message-ID: <14118.11673.876035.650537@anthem.cnri.reston.va.us> >>>>> "Dragon" == The Dragon De Monsyne writes: | conn = smtplib.SMTP(mm_cfg.SMTPHOST) | # Do the EHLO/HELO manually so we can check for DSN support | if conn.ehlo() >= 400: | conn.helo() Dragon> change it to: | conn = smtplib.SMTP(mm_cfg.SMTPHOST) | # Do the EHLO/HELO manually so we can check for DSN support | if conn.ehlo()[0] >= 400: | conn.helo() Thanks for the patch Dragon. I'm going to also copy Python 1.5.2's final smtplib.py file into Mailman/pythonlib and keep the module test hack in TrySMTPDelivery. What this means is that Mailman will probably be broken for Python 1.5.2 beta, but I don't think that's a huge loss. Comments? -Barry From James.Nicholson@amedd.army.mil Tue Apr 27 22:36:09 1999 From: James.Nicholson@amedd.army.mil (Nicholson James D) Date: Tue, 27 Apr 1999 17:36:09 -0400 Subject: [Mailman-Developers] Having kittens with the code Message-ID: I have been trying to fix the mailman code for some time now, and I would really appreciate any help. The basic problem is that the anonymous_list is broken on my machine, I don't know why, but, I can't even debug. My Problem: I turn on the anonymous_list option so that all mail appears to the recipient as if it emanates from the listname@machine. However, it doesn't work. Everything sent out to the test list still appears to come from an individual user. My Attempt at a solution: Someone told me that the anonymizing of the list is done in the Post() routine in MailList.py. So, I go in there and hardwire a change to the 'From' and 'To' fields, with no luck. So, if you find the code: del msg['reply-to'] del msg['sender'] I then add the following code: msg.SetHeader('From', 'listname@machinename') msg.SetHeader('To', 'listname@machinename') and comment out the following code beginning with 'if self.anonymous_list:' And what happens is nothing. Nothing I do here seems to affect the header of reflected mail. Is this the wrong place to make these changes or is the mail being postprocessed somewhere else that undoes my changes? So, now I really want to debug. So, I use the handy self.LogMsg() function. But, I get nothing in the logs. Here's the code I added right after the hardwired changes above: subj = msg.getheader('from') self.LogMsg("error", "initially from %s ", subj ) NADA for output. Can someone please send me a clue here? I've been working on it for weeks and can't get anywhere. If I can't solve the problem, I just won't have a mailing list. -Jim From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Apr 27 22:38:03 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 27 Apr 1999 17:38:03 -0400 (EDT) Subject: [Mailman-Developers] mailman does not work with exim and python 1.5.2 References: Message-ID: <14118.11835.729973.250910@anthem.cnri.reston.va.us> Oh dang. I just remembered that smtplib.py has a patch by Per Cederqvist post Python 1.5.2. I'm going to copy that version to Mailman/pythonlib and use it unconditionally. Dragon, how's that sound? -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Apr 27 23:53:10 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 27 Apr 1999 18:53:10 -0400 (EDT) Subject: [Mailman-Developers] Having kittens with the code References: Message-ID: <14118.16342.614948.711654@anthem.cnri.reston.va.us> >>>>> "NJD" == Nicholson James D writes: NJD> I have been trying to fix the mailman code for some time now, NJD> and I would really appreciate any help. The basic problem is NJD> that the anonymous_list is broken on my machine, I don't know NJD> why, but, I can't even debug. James, here's another situation that I can't reproduce. If I set "Hide the sender" to yes, I get the expected header. Note that sendmail gets partly in the way here (and this may be your problem?). For me, sendmail munges the From header to not include my host name. This sucks because our mailhost knows nothing about my list. Oh well, sendmail's evil anyway. :-) BTW, on your previous message on the subject, I think From: should still come from the GetAdminEmail(), however I think maybe Reply-To: for anonymous lists should be set to GetListEmail(). And note further that turning on anonymous_list is probably a false comfort. Lots of other headers get through that /could/ be used to identify the user (e.g. my X-Face header gets through). We'd probably want to do a lot more stripping of headers to have a really effective anonymizer. NJD> So, if you find the code: | del msg['reply-to'] | del msg['sender'] NJD> I then add the following code: | msg.SetHeader('From', 'listname@machinename') | msg.SetHeader('To', 'listname@machinename') NJD> and comment out the following code beginning with 'if NJD> self.anonymous_list:' And what happens is nothing. Nothing I NJD> do here seems to affect the header of reflected mail. Is NJD> this the wrong place to make these changes or is the mail NJD> being postprocessed somewhere else that undoes my changes? Okay, apologies for the following "did-you-plug-it-in" suggestion. You're sure that you're either making the change to the installed version of the files, or that you're doing a make install after making the changes. In other words, you're absolutely positive that Mailman's running your modified version? Try also blowing away the .pyc files and see if they get regenerated. Finally, you can just do something like: fp = open('/tmp/rawlog.txt', 'w') fp.write('I know you are in there!\n') fp.close() right at the point in question. If that file doesn't show up with the message in it, you've got deeper problems. If that works, but LogMsg() still doesn't, it /could/ be a permission problem, but I don't think so. You might just want to use your rawlog.txt file to do your logging directly. -Barry From bryner@uiuc.edu Fri Apr 30 17:52:19 1999 From: bryner@uiuc.edu (Brian Ryner) Date: Fri, 30 Apr 1999 11:52:19 -0500 Subject: [Mailman-Developers] Error/crash in admindb - 1.0b11 Message-ID: <3729DFC3.C3CF4F6E@uiuc.edu> This is a multi-part message in MIME format. --------------329FBC73D35B7EE45A42B7CB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi- This crash happened when going to http://host/mailman/admindb. I have not been able to reproduce it since then. The error log is attached. The system is running Slackware 3.5, with Python 1.5.1. Any suggestions or patches? Also, is there a way that I can turn off the extraneous debugging information sent to the WWW client, and have it just be put in the log? The fact that it dumps so much information about the system could be seen as a security risk. Thanks. -Brian Ryner bryner@uiuc.edu --------------329FBC73D35B7EE45A42B7CB Content-Type: text/plain; charset=us-ascii; name="error" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="error" Apr 29 22:33:41 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin: [----- Mailman Version: 1.0b11 -----] admin: [----- Traceback ------] admin: Traceback (innermost last): admin: File "/admin/mailman/scripts/driver", line 112, in run_main admin: main() admin: File "/admin/mailman/Mailman/Cgi/admindb.py", line 77, in main admin: doc.AddItem(eader(2, "Invalid options to CGI script.")) admin: NameError: eader admin: [----- Environment Variables -----] admin: DOCUMENT_ROOT: /files/admin/httpd/htdocs admin: HTTP_ACCEPT_ENCODING: gzip, deflate admin: SERVER_PORT: 80 admin: PATH_TRANSLATED: /files/admin/httpd/htdocs/ admin: URL_COUNT: 6 admin: GATEWAY_INTERFACE: CGI/1.1 admin: HTTP_ACCEPT_LANGUAGE: en-us admin: HTTP_PROXY_CONNECTION: Keep-Alive admin: REMOTE_ADDR: xxx.yyy.zzz.xxx admin: SERVER_NAME: www.xxxxxxx.org admin: URL_COUNT_DB: /files/admin/httpd/logs/counters/ALL admin: HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 4.01; Windows 95) admin: HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* admin: REQUEST_URI: /mailman/admindb/ admin: PATH: /usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin admin: QUERY_STRING: admin: SCRIPT_FILENAME: /files/admin/mailman/cgi-bin/admindb admin: PATH_INFO: / admin: HTTP_HOST: www.xxxxxxx.org admin: REQUEST_METHOD: GET admin: SERVER_SIGNATURE: admin: URL_COUNT_RESET: Thursday, 29-Apr-99 00:19:13 CDT admin: SCRIPT_NAME: /mailman/admindb admin: SERVER_ADMIN: admin@xxxxxx.org admin: SERVER_SOFTWARE: Apache/1.3.4 (Unix) admin: PYTHONPATH: /admin/mailman admin: SERVER_PROTOCOL: HTTP/1.0 admin: REMOTE_PORT: 6208 --------------329FBC73D35B7EE45A42B7CB-- From bryner@uiuc.edu Fri Apr 30 18:55:15 1999 From: bryner@uiuc.edu (Brian Ryner) Date: Fri, 30 Apr 1999 12:55:15 -0500 Subject: [Mailman-Developers] Re: [Mailman-Users] Error/crash in admindb - 1.0b11 Message-ID: <3729EE83.5DA4F401@uiuc.edu> Is that line (admindb.py, line 77) supposed to say Header instead of eader ? > Apr 29 22:33:41 1999 admin: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > admin: [----- Mailman Version: 1.0b11 -----] > admin: [----- Traceback ------] > admin: Traceback (innermost last): > admin: File "/admin/mailman/scripts/driver", line 112, in run_main > admin: main() > admin: File "/admin/mailman/Mailman/Cgi/admindb.py", line 77, in main > admin: doc.AddItem(eader(2, "Invalid options to CGI script.")) > admin: NameError: eader