Mailman-Developers May 2002

mailman-developers@python.org

56 participants
229 discussions

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

28 May '02

Bugs item #559558, was opened at 2002-05-23 06:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id… Category: security/privacy Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Benjamin Geer (beroul) Assigned to: Nobody/Anonymous (nobody) Summary: can't make moderated list unmoderated Initial Comment: With Mailman 2.0.8, I made a list moderated (by setting "Must posts be approved by an administrator?" in Privacy Options) to "Yes". A few weeks later, I changed my mind and set this to "No". However, whenever someone tries to post to the list, I still receive a message from Mailman, saying that the posting requires approval (the subject line says "Posting to a restricted list by sender requires approval"). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 00:58 Message: Logged In: YES user_id=12800 Check the member_postings_only and postings variables for other options that could be affecting your settings. I'm closing this bug report because the list is likely working as expected. However, in MM2.0.x the interaction of these three variables is definitely confusing, so for more help please contact mailman-users(a)python.org. Note that this have greatly improved in MM2.1. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id…

1 0

[ mailman-Bugs-560127 ] qrunner segfaults on specific message
by noreply＠sourceforge.net 28 May '02

28 May '02

Bugs item #560127, was opened at 2002-05-24 10:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id… Category: mail delivery >Group: Unreproducible >Status: Closed Resolution: None Priority: 5 Submitted By: Douglas Paul (dwpaul) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner segfaults on specific message Initial Comment: I received the following bounce message to the -admin account on a mailing list I run. When qrunner tries to process this message, it segfaults, and leaves its locks. When subsequent qrunner passes occur, it just complains that it can't get the lock. Removing the locks just causes it to segfault again. The only solution I've found it to simply remove the message from the queue. This originally happened with Mailman 2.0.8, but I upgraded to 2.0.11 and it still occurred. I was able to reproduce the problem by mailing the contents of the message to the -admin address again. The .msg and .db files are attached. Version Info: Mailman 2.0.8 / 2.0.11 Python 1.5.2 (#1, Jan 19 2000, 19:01:15) [GCC 2.95.1 19990816 (release)] on linux-armv4l Linux elemental 2.4.17-rmk5 #7 Mon Feb 18 18:12:50 EST 2002 armv4l unknown Sendmail 8.9.3 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 00:55 Message: Logged In: YES user_id=12800 The backtrace is useless because the stack is trashed., but thanks anyway! :) I'm not sure what to blame, although i have a sneaking suspicion that it's bugs in Python 1.5.2's pickle or marshal code. I can't reproduce it with the files you've given, so I can't be sure. At this point, upgrading to Python 2.2.1 is probably your best bet. If you still get crashes after the upgrade, please open a new bug report. You'll definitely want to use MM2.0.11 with Python 2.2.1. ---------------------------------------------------------------------- Comment By: Douglas Paul (dwpaul) Date: 2002-05-25 12:20 Message: Logged In: YES user_id=552731 Unfortunately, my Python doesn't have any symbols, but here's what I get from a backtrace. It looks to me like it's trying to allocate a lot of memory, and a bug in glibc is making it crash: (gdb) backtrace #0 chunk_alloc (ar_ptr=0x4015bbe4, nb=40) at malloc.c:2814 #1 0x400c86fc in __libc_malloc (bytes=1075166260) at malloc.c:2643 #2 0xbfffdc10 in ?? () I also get this strange message, too: warning: core file may not match specified executable file. Core was generated by `'. Program terminated with signal 11, Segmentation fault. This system was running with glibc 2.1.2. I tried running it on in a chrooted environment I'm building to upgrade my system (glibc 2.2.5, Python 2.2) and it does work fine. Unless there's any other information you'd like me to find, I think I'll just upgrade my Python to 2.2. It's definitely not a bug in Mailman. Thanks for the quick response. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 03:14 Message: Logged In: YES user_id=12800 I've no idea why you get a core dump, but by definition it must be a bug in Python. No Python script should ever be able to crash the interpreter. I can't find anything wrong with the files you uploaded. Is there any chance you can 1) run gdb on the resulting core file to get a stack trace; 2) upgrade your Python to something newer than 1.5.2? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id…

1 0

Interfacing with MySQL?
by Chad Day 26 May '02

26 May '02

I've looked on SourceForge for a patch and didn't find anything, but I'm sure this has probably come up before.. couldn't find it in the archives either. Has anyone written a patch that will allow mailman to interface with MySQL for login verification? I have a bunch of user info in a mysql database and I want to tie these 2 together, and not have the user have to keep a seperate password (or have the ability to change them, throwing them out of sync).. Can anyone help me out? Thanks, Chad

1 0

Help on a code sample...
by Donal Hunt 26 May '02

26 May '02

Hi there, I've written the following example handler for Mailman but have a bug that I can't for the life of me understand why it's happening... It's based on Personalize.py (yes, I'm aware it's deprecated, but it works for me. :-)) Basically. The email gets encrypted correctly for the first person (and sent to them), but the second person gets person one's mail encrypted!! Basically "valu"e doesn't get reset back to the actual unencrypted email contents (msg). I'm sure I'm missing something stupid in my loop (to do the multi-part stuff). If someone spots it I'ld really appreciate a mail. Thanks in advance. Donal DCU ----------------------------------------------------- def process(mlist, msg, msgdata): if getattr(mlist, 'crypto_processing') <> 1: return if not msgdata.get('decrypted'): return # Make a copy for each recipient, and re-queue the copies to the incoming # queue. Set the pipeline for the copies to just Decorate and # ToOutgoing. The normal queue on the original copy should take care of # everything else. newpipeline = ['Decorate', 'ToOutgoing'] inq = get_switchboard(mm_cfg.INQUEUE_DIR) # Save the original To: line originalto = msg['To'] # Create a separate message for each recipient savedmsg = msg for member in msgdata.get('recips', []): msg = savedmsg syslog('error', 'msg: %s' % msg) r_code = 1 metadatacopy = msgdata.copy() metadatacopy['pipeline'] = newpipeline metadatacopy['recips'] = [member] metadatacopy['encrypted'] = 1 del msg['To'] name = mlist.getMemberName(member) if name: msg['To'] = '%s (%s)' % (member, name) else: msg['To'] = member # Walk the message tree and tree to encrypt text/plain parts. for part in msg.walk(): if part.get_type('text/plain') == 'text/plain': # text/plain message part - encrypt it. value = part.get_payload() if not value: pass else: try: syslog('error', 'value **2**: %s' % value) (r_code,result) = IBE.encrypt_msg(value, mlist.getMemberCPAddress(member)) syslog('error', 'result: %s' % result) if r_code == 1: part.set_payload("""Error occurred during encryption of this message / message part.\n\n Error msg:\n"""+result) else: part.set_payload(result) del metadatacopy['decrypted'] except Exception, e: syslog('error', 'Error in encrypt_msg, IBE.py: %s' % e) else: # Non text/plain msg part. Ignore. pass inq.enqueue(msg, metadatacopy, listname=mlist.internal_name()) # Restore the original To: line del msg['To'] msg['To'] = originalto # Don't let the normal ToOutgoing processing actually send the original # copy. del msgdata['recips'] -----------------------------------------------------

1 0

from python-list@python.org ... for those of you not subscribed to there
by Laura Creighton 26 May '02

26 May '02

(Message spamfixes:2) Date: Sat, 25 May 2002 22:18:12 EDT To: <Python(a)gbronline.com> cc: "'Sean 'Shaleh' Perry'" <shalehperry(a)attbi.com>, "'Python Mailing List'" <python-list(a)python.org> From: Matt Curtin <cmcurtin(a)interhack.net> Subject: Meta: Shibboleth (was: RE: Off Topic, But List Related) Return-Path: python-list-admin(a)python.org Delivery-Date: Sun May 26 04:25:35 2002 MIME-Version: 1.0 In-Reply-To: <007101c20458$335f1e20$388e7aa5@adirondacker> References: <XFMail.20020525095354.shalehperry(a)attbi.com> <007101c20458$335f1e20$388e7aa5@adirondacker> X-Mailer: VM 6.92 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid X-Attribution: Matt X-URL: http://www.interhack.net/people/cmcurtin/ X-message-flag: Thank you for using LookOut, the most insecure mailer available ***! X-Accept-Language: en-US, en, ru, de, fr X-Face: L"IcL.b%SDN]0Kql2b`e.}+i05V9fi\yX#H1+Xl)3!+n/3?5`%-SA-HDg<IT;O8XnF>Pk9 ***uTk<3dv^J5DCgal)-E{`zN#*o6F|y>r)\<<ui53(fC)EM]42*oF|P@Hm"Z+GK%"b#q'ycf= ***2s5%NNR0S;8"vcNN"O;O}YpB{&^1xazqDMg^v!6LS7S"5|}2uTl$NKV5}Bkca{M|Y^cZD@{ ***1 X-Spam-Level: Sender: python-list-admin(a)python.org Errors-To: python-list-admin(a)python.org X-BeenThere: python-list(a)python.org X-Mailman-Version: 2.0.11 (101270) Precedence: bulk List-Help: <mailto:python-list-request@python.org?subject=help> List-Post: <mailto:python-list@python.org> List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> List-Id: General discussion list for the Python programming language <python-li ***st.python.org> List-Unsubscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe> List-Archive: <http://mail.python.org/pipermail/python-list/> X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: On 25 May 2002, Peter F. Ferris presumably wrote: Hi, I'm the architect of Shibboleth, the privacy- and security-aware mailing list manager Peter mentioned. I'd like to clear up a few things, just to make sure there are no misconceptions. > perhaps you should read the white paper. [...] > The only addresses that would be gleaned would be those typed in the > message body by the user. Shibboleth addresses this problem by standardizing all addresses. If we have a set of lists dedicated to discussion of python, we might designate that list "family" as "python". All subscribers to any of the python lists would then have a standardized address form of python+nym(a)example.com Assuming that the local MTA uses + as the separator character between account and token for delivery. (I believe that qmail installations will use - by default, and the character is settable in most Unix MTAs.) Thus, if my nym is cmcurtin and I'm a subscriber, my posts would wind up in the archives (and posted through the lists) as python+cmcurtin(a)example.com. No one would ever know my address(es) unless I include them in signature blocks and whatnot. This means that all mail in connection with a list, or even person-to-person stuff that started on a list is run through Shibboleth. Mailing lists follow the same form, e.g., "Python Technical Discussion" might be python+tech(a)example.com, "Python Advocacy" might be python+perlsucks(a)example.com, and "Python Questions" might be python+help(a)example.com. Shibboleth performs a series of tests to detect whether a message has come from an "insider" (someone legitimately subscribed to one of the lists). If not, Shibboleth will return a "user unknown" bounce to the sender, e.g., an outsider (e.g., spammer) mailing python+cmcurtin(a)example.com would get a user unknown bounce, where an insider mailing python+cmcurtin(a)example.com would have the message delivered to me through the python list-supporting Shibboleth installation. (These tests also include provisions for handling of PGP signatures, reusable passwords in X-Password headers, E?SMTP/MTA path analysis for address forgery detection and some other useful stuff for enforcing the only-insiders-can-talk-to-insiders policy option.) We actually built the system so that groups that wanted privacy and security on a public network would be able to get it. Spam became a problem after the project was underway. Spam, email-worms, etc., are all handled remarkably well in practice on existing Shibboleth installations. That is, I know of no cases where any spam has been posted to a Shibboleth mailing list, or where any worm has propagated through a Shibboleth-run list or to a user whose address was published through participation in a Shibboleth list. (I know Peter from one such list family, and our lack of spam, malware, and other outsider-originated annoyances is likely what prompted his mention of Shibboleth. But I can't speak for him obviously. :-) Peter refers to a white paper, which isn't quite correct. The URI he gave is for a formal technical paper that is part of the Proceedings of the 9th USENIX Security Symposium. You can pick up the paper as it was presented at the conference from the USENIX site, of course. Shibboleth is implemented in that other language ;-) but I would be delighted to see its functionality become options in a more general-purpose and widely-used mailing list manager like Mailman. I'm presently too buried to perform the porting work myself, but if someone would like to do some fun coding, I would be happy to advise and to provide feedback on getting some of the more useful features of Shibboleth incorporated into another system. Happy hacking! -- Matt Curtin Interhack Corp +1 614 545 HACK http://web.interhack.com/ Author, Developing Trust: Online Privacy and Security (Apress, 2001) Knight, Lambda Calculus | Certum quod factum. --Giovanni Battista Vico -- http://mail.python.org/mailman/listinfo/python-list

1 0

'make install' error in cvs
by David Gibbs 25 May '02

25 May '02

I just updated cvs and ran 'make install', and got the following error ... make[1]: Entering directory `/root/mailman-2.1-beta/mailman/misc' for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/bin/python2 setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib); \ done File "/usr/local/mailman/pythonlib/email/_compat22.py", line 21 yield self ^ SyntaxError: invalid syntax ^C [ I killed it at this point ] interrupted make[1]: *** [install-packages] Error 1 make: *** [doinstall] Interrupt Ideas? david

3 7

Re: [Mailman-Users] Mailman does everything except send mail
by Norbert Bollow 25 May '02

25 May '02

barry(a)zope.com (Barry A. Warsaw) wrote on mailman-users: > MM2.1's qrunner will take almost no resources to just leave it > running. Is there a way to start say a hundred of them on the same box (in order to service a hundred separate Mailman installations) so that most of the memory is shared? Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com

3 3

compile error in mailman cvs?
by Marc MERLIN 25 May '02

25 May '02

I just synced my tree, and: make[1]: Entering directory `/var/local/src/mailman-cvs/misc' for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/var/local/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /var/local/mailman/pythonlib --install-purelib /var/local/mailman/pythonlib); \ done File "/var/local/mailman/pythonlib/email/_compat22.py", line 21 yield self ^ SyntaxError: invalid syntax File "/var/local/mailman/pythonlib/japanese/mappings/jis_x_0208.py", line 6234 "\x6d\x ^ Syntax Barry? Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

2 2

Python Upgrade problem with mailman
by Webmaster 25 May '02

25 May '02

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

2 1

[ mailman-Bugs-560127 ] qrunner segfaults on specific message
by noreply＠sourceforge.net 25 May '02

25 May '02

Bugs item #560127, was opened at 2002-05-24 10:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Douglas Paul (dwpaul) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner segfaults on specific message Initial Comment: I received the following bounce message to the -admin account on a mailing list I run. When qrunner tries to process this message, it segfaults, and leaves its locks. When subsequent qrunner passes occur, it just complains that it can't get the lock. Removing the locks just causes it to segfault again. The only solution I've found it to simply remove the message from the queue. This originally happened with Mailman 2.0.8, but I upgraded to 2.0.11 and it still occurred. I was able to reproduce the problem by mailing the contents of the message to the -admin address again. The .msg and .db files are attached. Version Info: Mailman 2.0.8 / 2.0.11 Python 1.5.2 (#1, Jan 19 2000, 19:01:15) [GCC 2.95.1 19990816 (release)] on linux-armv4l Linux elemental 2.4.17-rmk5 #7 Mon Feb 18 18:12:50 EST 2002 armv4l unknown Sendmail 8.9.3 ---------------------------------------------------------------------- >Comment By: Douglas Paul (dwpaul) Date: 2002-05-25 12:20 Message: Logged In: YES user_id=552731 Unfortunately, my Python doesn't have any symbols, but here's what I get from a backtrace. It looks to me like it's trying to allocate a lot of memory, and a bug in glibc is making it crash: (gdb) backtrace #0 chunk_alloc (ar_ptr=0x4015bbe4, nb=40) at malloc.c:2814 #1 0x400c86fc in __libc_malloc (bytes=1075166260) at malloc.c:2643 #2 0xbfffdc10 in ?? () I also get this strange message, too: warning: core file may not match specified executable file. Core was generated by `'. Program terminated with signal 11, Segmentation fault. This system was running with glibc 2.1.2. I tried running it on in a chrooted environment I'm building to upgrade my system (glibc 2.2.5, Python 2.2) and it does work fine. Unless there's any other information you'd like me to find, I think I'll just upgrade my Python to 2.2. It's definitely not a bug in Mailman. Thanks for the quick response. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 03:14 Message: Logged In: YES user_id=12800 I've no idea why you get a core dump, but by definition it must be a bug in Python. No Python script should ever be able to crash the interpreter. I can't find anything wrong with the files you uploaded. Is there any chance you can 1) run gdb on the resulting core file to get a stack trace; 2) upgrade your Python to something newer than 1.5.2? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id…

1 0

← Newer
1
2
3
4
5
6
7
...
23
Older →

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers May 2002