unsubscribe ----- Original Message ----- From: <mailman-developers-request@python.org> To: <mailman-developers@python.org> Sent: Monday, June 25, 2001 6:01 PM Subject: Mailman-Developers digest, Vol 1 #917 - 3 msgs
Send Mailman-Developers mailing list submissions to mailman-developers@python.org
To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-developers or, via email, send a message with subject or body 'help' to mailman-developers-request@python.org
You can reach the person managing the list at mailman-developers-admin@python.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Mailman-Developers digest..."
Today's Topics:
- qrunner -- problem with huge mail messages (Dirko van Schalkwyk)
- HTML Issue (James Dinan)
- Re: HTML Issue (Thomas Wouters)
--__--__--
Message: 1 Date: Mon, 25 Jun 2001 15:35:26 +0200 From: Dirko van Schalkwyk <dvschalk@ing.sun.ac.za> Reply-To: dvschalk@ing.sun.ac.za To: mailman-developers@python.org Subject: [Mailman-Developers] qrunner -- problem with huge mail messages
Hi
It is 6:02 AM Sat. and I'm fairly fed-up.
I have the following situation :
Mailman 2.0.5 Python 2.0 MTA : postfix
I set Mailman up, created a test list and played with it for a while. Then I send it a big "whopper" 5MB e-mail. I watched the logs and saw postfix running the wrapper. The cron started qrunner and all hell broke lose (over dramatizing a bit). It started running at 100% CPU, where it stayed until I killed it. The message was queued in $prefix/qfiles, it and its little .db file. I had to remove those as well as the locks in $prefix/locks before I could successfully use the list again.
So I thought, "well maybe the pipermail thingy can't handle the huge mime thingies I'm sending it". So I send a smaller attachment <150kb. Things went fine (except for the ugly html page:) ) Send it a 1MB attachment. qrunner started spinning it's wheels again. Had to seek and destroy again.
So I replaced pipermail with MHonArc (With PUBLIC_EXTERNAL_ARCHIVER , PRIVATE_EXTERNAL_ARCHIVER , PUBLIC_ARCHIVE_URL in mm_cfg.py and the appropriate thingies in httpd.conf). Small messages worked fine. Big whoppers = no joy i.e. still the same with big messages. So at least it is not the archiving bit that messes up.
So I upgraded my Python ;) Ermm, to version 2.0. Still the same.
Has anyone had the same problem? Can anyone confirm this as a bug by sending a 2MB file to a 2.0.5 testlist?
How do I do a trace in Python? (i.e. it is as familiar to me as the bacteria in my stomach (I runs on my machine and there endeth the relationship))
Any pointers? Anything? I need to get this list running before monday (yes this is for a business). Please!!!??
Sorry if this e-mail was not formal enough, the 48 hours strait is getting to me.
Greets
Dirko
Lab E352 E&E Engineering Univ. of Stellenbosch South Africa
--__--__--
Message: 2 From: "James Dinan" <james@gilbertwalker.com> To: <mailman-developers@python.org> Date: Mon, 25 Jun 2001 10:49:27 -0700 Subject: [Mailman-Developers] HTML Issue
This is a multi-part message in MIME format.
------=_NextPart_000_003C_01C0FD64.8168A650 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I posted this message to mailman-users, and then the more I was thinking = about it, the more I began to think this was a question for developers. = Please tell me what you think:
I am running Mailman 2.0.1 on Redhat 6.2 and I am having difficulty with = the Subscribe Results Page (/mailman/subscribe/listname). More = specifically, I have edited the HTML and whenever I view the page, = mailman appears to be prepending the following to the source:
<HTML> <HEAD> </HEAD> <BODY <BODY bgcolor=3D"#ffffff">
which I'm sure you can imagine is wreaking havoc on the rest of my HTML. = Has anyone else had this problem, or is this fixed in future releases? = Since I am not an admin on the server I am configuring it will be = difficult (Redhat installs mailman in /var/mailman) to recompile = mailman.
I have just checked = http://mail.python.org/mailman/subscribe/mailman-users and you can see = for yourself that this is also happening with the version of mailman = that serves this list.
- jim dinan.
James Dinan <james@gilbertwalker.com> Gilbert Walker Group: Lenox, MA U.S.A Available: http://www.gilbertwalker.com
------=_NextPart_000_003C_01C0FD64.8168A650 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
<BODY=20 bgcolor=3D"#ffffff"></FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>which I'm sure you can imagine is = wreaking havoc on=20
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I posted this message to mailman-users, = and then=20 the more I was thinking about it, the more I began to think this was a = question=20 for developers. Please tell me what you think:</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2> <DIV><FONT face=3DArial size=3D2>I am running Mailman 2.0.1 on Redhat = 6.2 and I am=20 having difficulty with the Subscribe Results Page=20 (/mailman/subscribe/listname). More specifically, I have edited = the HTML=20 and whenever I view the page, mailman appears to be prepending the = following to=20 the source:</FONT></DIV> <DIV><FONT face=3DArial=20 size=3D2><BR><HTML><BR><HEAD><BR></HEAD><BR><BODY<BR= the rest of my HTML. Has anyone else had this problem, or is this = fixed in=20 future releases? Since I am not an admin on the server I am = configuring it=20 will be difficult (Redhat installs mailman in /var/mailman) to recompile =
mailman.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>I have just checked <A=20 href=3D"http://mail.python.org/mailman/subscribe/mailman-users">http://ma= il.python.org/mailman/subscribe/mailman-users</A> and=20 you can see for yourself that this is also happening with the version of = mailman=20 that serves this list.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>- jim dinan.</FONT></DIV> <DIV><FONT face=3DArial=20 size=3D2>----------------------------------------------------------------= -------<BR>James=20 Dinan <<A=20 href=3D"mailto:james@gilbertwalker.com">james@gilbertwalker.com</A>><B= R>Gilbert=20 Walker Group: Lenox, MA U.S.A<BR>Available: <A=20 href=3D"http://www.gilbertwalker.com">http://www.gilbertwalker.com</A></F= ONT></FONT></DIV></DIV></BODY></HTML>
------=_NextPart_000_003C_01C0FD64.8168A650--
--__--__--
Message: 3 Date: Mon, 25 Jun 2001 17:47:58 +0200 From: Thomas Wouters <thomas@xs4all.net> To: James Dinan <james@gilbertwalker.com> Cc: mailman-developers@python.org Subject: Re: [Mailman-Developers] HTML Issue
On Mon, Jun 25, 2001 at 10:49:27AM -0700, James Dinan wrote:
I posted this message to mailman-users, and then the more I was thinking about it, the more I began to think this was a question for developers. Please tell me what you think:
I am running Mailman 2.0.1 on Redhat 6.2 and I am having difficulty with the Subscribe Results Page (/mailman/subscribe/listname). More specifically, I have edited the HTML and whenever I view the page, mailman appears to be prepending the following to the source:
<HTML> <HEAD> </HEAD> <BODY <BODY bgcolor="#ffffff">
Yes. This is an open bug, and an old one. It still requires a Pronouncement from Barry. The problem is that Mailman creates a HTMLgen Document instead of a HeadlessDocument, for the list page. From the top of my head the fix is to change
doc = Document()into
doc = HeadlessDocument()in Mailman/Cgi/listinfo.py, function listinfo_overview(). I believe Barry is reluctant to fix it because of possible breakage (people might have made template files with the (Headfull)Document in mind.) Barry ? :)
-- Thomas Wouters <thomas@xs4all.net>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
--__--__--
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers
End of Mailman-Developers Digest