Mailman-coders March 2007

mailman-coders@python.org

1 participants
22 discussions

[ mailman-Patches-1688957 ] fix concurrency problem in 2.2

by SourceForge.net

Patches item #1688957, was opened at 2007-03-27 08:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1688957&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix concurrency problem in 2.2 Initial Comment: The problem is described in a mailman-dev post. http://www.mail-archive.com/mailman-developers@python.org/msg10203.html Fix this by introducing reload mechanism in the interface to SQLAlchemy. I use session.refresh() to do this but because this function looks like to break locks, attempt is made to save the lock status and lock again after refresh. I'm not sure this is the right way to fix the problem but it is working (for now). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1688957&group_…

14 years, 4 months

[ mailman-Bugs-1687455 ] Mailman should detect mailextensions

by SourceForge.net

Bugs item #1687455, was opened at 2007-03-24 17:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1687455&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman should detect mailextensions Initial Comment: Mailextensions are realised by adding "+extension" to the userpart of the e-mail-address. It's helpful to filter mailinglists and other stuff. p.heinlein+extension1(a)heinlein-support.de is the same like "p.heinlein(a)heinlein-support.de". If user+extension@ is subscribed to a mailinglist, Mailman should also accept user@ as a subscribed member address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1687455&group_…

14 years, 4 months

[ mailman-Bugs-1495122 ] Mailman strips format=flowed from Content-Type header

by SourceForge.net

Bugs item #1495122, was opened at 2006-05-25 12:24 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bart Jacobs (radiantskies) Assigned to: Mark Sapiro (msapiro) Summary: Mailman strips format=flowed from Content-Type header Initial Comment: It seems that Mailman strips the format=flowed argument from the Content-Type: text/plain header when delivering incoming e-mails to subscribers. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-03-23 12:19 Message: Logged In: YES user_id=1123998 Originator: NO And yet again I have replaced the patch. Scrubber.py would throw an exception if a message it was processing had no text/plain part. The new patch adds line 190 to Scrubber.py format = delsp = None File Added: flowed.patch.txt ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-26 09:39 Message: Logged In: YES user_id=1123998 Originator: NO I replaced the patch again. This time, the Scrubber.py patch is functionally identical to 217616: flowed.patch.txt, but I have added more comments to the Scrubber patch specifically related to why it won't work for the archive or the plain format digest. The Decorate.py patch has been updated to remove any trailing spaces from lines of msg_header and msg_footer so they won't be inadvertently flowed. I have the feeling that the biggest issue for most occurs in Decorate.py in adding msg_header and/or msg_footer, and this is fixed. File Added: flowed.patch.txt ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-24 22:38 Message: Logged In: YES user_id=1123998 Originator: NO I have replaced the flowed.patch.txt file attached. The previous scrubber patch didn't work. This one has been more thoroughly tested and does work at least for the test cases tried. There is an additional fix in this scrubber patch which has to do with getting the appropriate character set for the part separator. See the thread beginning at <http://mail.python.org/pipermail/mailman-users/2006-November/054515.html>. File Added: flowed.patch.txt ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-19 17:12 Message: Logged In: YES user_id=1123998 Originator: NO I have attached a patch (flowed.patch.txt) that applies to Mailman 2.1.9 and 2.1.8. Line numbers may need adjusting for earlier versions. This is a preliminary patch for testing and shouldn't be considered official at this point. Feedback will be appreciated. File Added: flowed.patch.txt ---------------------------------------------------------------------- Comment By: P T Withington (ptwithy) Date: 2006-10-13 13:37 Message: Logged In: YES user_id=615189 Thanks, that's great. For now, I am very happy that I can just turn off my footer and get the right behavior (as a work-around). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-10-13 11:23 Message: Logged In: YES user_id=1123998 Regarding the previous comment. I don't disagee with you, and my 2006-06-13 comment wasn't meant to imply that I wasn't interested in fixing this, just that there might be more to it than is apparent at first glance. I do have it on my 'to do' list. ---------------------------------------------------------------------- Comment By: P T Withington (ptwithy) Date: 2006-10-13 10:05 Message: Logged In: YES user_id=615189 Man this bug drives me NUTS! Surely it is more important to maintain the content of the message that to quibble about the format on header/footer. Any halfway intelligent mail client will wrap long URLs, expecting them to be reflowed by the recipient, but since mailman strips out the format and delsp from the Content-type, the recipient is left in the lurch and sees the URL as multiple lines. In format-flowed, only lines that end in <space><linefeed> are re-flowed. If the header/footer lines end in <linefeed> they will not be reflowed, so I don't see the need to have a different format for them? What am I missing? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-06-13 09:34 Message: Logged In: YES user_id=1123998 I think you have found the cause. Scrubber also does the same thing when flattening the message, but now we have a difficult decision. If we want to 'fix' Decorate, we now are faced with a situation where we may be adding a 'format=fixed' header and/or footer to a 'format=flowed' message body. This potential incompatability may require us to 'wrap' the message and add the header/footer as separate parts in this case. This will undoubtedly raise additional complaints. In the case of Scrubber, this may lead us to scrub the actual message body part - not a good thing. I may be over-reacting here. It may turn out that it is OK to render the header/footer/scrubber messages as 'format=flowed'. Although I can contrive a footer for example (by putting trailing spaces on intermediate lines) that will be munged by rendering as 'format=flowed', this may not be a problem in practice, and Decorate could always be made to strip the spaces. There are also potentially issues with stripping of leading spaces because of the assumption that they are 'stuffed'. I don't know how big an issue this is in practice. Note, if we do preserve 'format=' we also need to preserve 'delsp='. ---------------------------------------------------------------------- Comment By: Bart Jacobs (radiantskies) Date: 2006-06-12 23:54 Message: Logged In: YES user_id=924185 I've browsed the mailman source code a bit and I found some suspicious code in /trunk/mailman/Mailman/Handlers/Decorate.py. If the list admin specifies a header or footer to be added to outgoing messages, then the content-type header is zapped and then regenerated from just the charset info, i.e. the format=flowed parameter is lost. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_…

14 years, 4 months

[ mailman-Bugs-1642388 ] Mailman re-enables delivery when your address changes.

by SourceForge.net

Bugs item #1642388, was opened at 2007-01-23 03:04 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Laura Creighton (lcreighton) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman re-enables delivery when your address changes. Initial Comment: My email address changed. I went to a list on python.org (edu-sig) where I am subscribed, and changed my address to reflect the new address. I then clicked the box to change this globally. I immediately started receiving mail messages from the high-volume list, python-list which is also on python.org even though I have disabled the delivery there. I had to disable this by hand. I'm running a stable 2.1 but I suspect this will be a bug everywhere. Laura Creighton now lac(a)openend.se (who doesn't want tracker confirmations) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-03-20 17:01 Message: Logged In: YES user_id=1123998 Originator: NO This has been fixed in SVN for Mailman 2.1.10 and 2.2. Note that if delivery was disabled by bounce, it will still be enabled for the new address, but not if it was disabled by admin or user. ---------------------------------------------------------------------- Comment By: Laura Creighton (lcreighton) Date: 2007-01-23 03:09 Message: Logged In: YES user_id=376262 Originator: YES Hmmm, edu-sig is 2.1.9 Maybe that is not the stable version? I forget which is which. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_…

14 years, 4 months

[ mailman-Patches-1682990 ] Fix login template

by SourceForge.net

Patches item #1682990, was opened at 2007-03-18 09:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1682990&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Alberto Mardegan (mardy) Assigned to: Nobody/Anonymous (nobody) Summary: Fix login template Initial Comment: Hi, please apply this trivial patch for next release; it's quite critical, since without it it's impossible to login into the administrative panel once you select the interlingua language. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1682990&group_…

14 years, 4 months

[ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments

by SourceForge.net

Bugs item #1085651, was opened at 2004-12-15 18:54 Message generated for change (Comment added) made by sjlongland You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- Comment By: Stuart Longland (sjlongland) Date: 2007-03-17 14:52 Message: Logged In: YES user_id=777641 Originator: NO I'm noticing this behaviour myself on a mailing list I set up for a group at uni. HTML emails signed using PGP/MIME and plaintext emails with attachments, both fail signature tests when checked in Enigmail 0.94.0.0 (20060110) on Thunderbird 1.5.0.10 (20070310). I'm running Mailman 2.1.9_rc1 (Gentoo ebuild) on Linux, with the Qmail MTA. ---------------------------------------------------------------------- Comment By: Magnus Holmgren (proffe) Date: 2006-05-11 20:02 Message: Logged In: YES user_id=669310 This is a duplicate of bug #815297. ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-03-20 23:51 Message: Logged In: YES user_id=42389 That function does indeed not conserve whitespace. E-mail doesn't say whitespace in headers (or even the message) must be preserved, so strictly speaking it's not a bug. However, it is a missing feature, and I think python is the place to implement it, not mailman. The point is that signed e-mails with attachments are sent as two parts: One which is a complete e-mail by itself, and one which holds the signature for that e-mail. This is because in attachments whitespace must be preserved (as opposed to the situation in the message itself). It would be very convenient if such e-mail can be handled by python programs without rewriting the things which work fine for non-signed e-mails. If the attachment is really changed, of course the signature will be broken. However, if it is not, it should not be hard to write out the same message (with whitespace preserved) as was read in. If this is not possible, it is quite hard to do it in the program, as python doesn't seem to support loading a part of an e-mail which has headers of its own as a binary attachment (without touching whitespace, in particular). ---------------------------------------------------------------------- Comment By: Jonas Berlin (xkr47) Date: 2005-03-19 22:21 Message: Logged In: YES user_id=66259 from python's Message.py: def _get_params_preserve(self, failobj, header): # Like get_params() but preserves the quoting of values. BAW: # should this be part of the public interface? According to my analysis of the comment, the function in question does _not_ guarantee to preserve the header as-is, it only preserves _quoting_. Thus, I don't think we can call this a bug in python. If there's more official documentation elsewhere that states that it should preserve everything as-is, then ignore this comment altogether :). I didn't have time to grasp how mailman actually uses that Message class, but I think mailman should be changed to use functions that don't alter the message, and/or re-implement that work according to the requirements of mailman (or, users of mailman :). Anyway, an alternative could be to continue to use the Message.py functions to parse the values while analyzing the contents of the message, and then copypaste the original headers as-is after checking. - xkr47 ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-30 03:08 Message: Logged In: YES user_id=15365 Dear Bas, Thanks a lot for identifying the source of this bug and flagging an upstream bug on Python. Etienne ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-01-24 21:35 Message: Logged In: YES user_id=42389 I checked the source, and this appears to be a bug in Python. It can read and write e-mails, including headers, and they are interpreted. However, it doesn't preserve their whitespace, which is of course fatal for pgp signatures. The bug is filed for python here: http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=54… ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-19 03:30 Message: Logged In: YES user_id=15365 I am attaching a screen shot of the content filtering settings (see the options.png attachment I have added to this bug report). In short, content filtering is disabled, so I don't think it is the cause of the problem. :-/ Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-17 10:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-08 11:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg <toniw(a)iki.fi> ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-30 14:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…

14 years, 4 months

[ mailman-Feature Requests-1634521 ] Need admin alerts

by SourceForge.net

Feature Requests item #1634521, was opened at 2007-01-12 22:58 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1634521&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Need admin alerts Initial Comment: I just noticed that for some reason none of our mailing lists have been archived for a while. Yikes. It would be good if mailman by default would notify admins if anything goes wrong with archiving. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2007-03-16 13:31 Message: Logged In: YES user_id=3142 Originator: NO Look into running mmdsr from a crontab each night. Brad wrote this script that gives you a daily email of Mailman status (it stands for MM Daily Status Report, IIRC). It greps your Mailman log files and queue dirs and produces a very valuable system report. I highly recommend using this. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-01-12 23:31 Message: Logged In: YES user_id=1123998 Originator: NO I am moving this to feature requests because that's what it is. As far as your issue of not archiving is concerned, it seems that perhaps ArchRunner is/was not running. If this is the case, addressing the issuue that caused it to die and restarting it will probably archive all the unprocessed messages in the archive/ queue. OTOH, possible there is some issue causing the messages to be shunted. In this case, fixing the underlying issue and running bin/unshunt should archive the messages. It would be very unusual if the messages were completely lost. Regarding your feature request, look at the "Daily status report script" (mmdsr) <http://sourceforge.net/tracker/index.php?func=detail&aid=1123383&group_id=1…> and in Mailman's contrib/ directory since 2.1.7. It's not a 'default' but it does a good job of reporting things that go wrong. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1634521&group_…

14 years, 4 months

[ mailman-Feature Requests-1682306 ] content filtering for reply_goes_to_list

by SourceForge.net

Feature Requests item #1682306, was opened at 2007-03-16 13:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1682306&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jim Popovitch (jimpop) Assigned to: Nobody/Anonymous (nobody) Summary: content filtering for reply_goes_to_list Initial Comment: I think a great addition to Mailman would be the ability to dynamically change reply_goes_to_list based on content filtering. For instance if the Subject contains "OT:" then reply could be set to Poster instead of the current list setting. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1682306&group_…

14 years, 4 months

[ mailman-Bugs-645906 ] User supplied HTML with % kills index.ht

by SourceForge.net

Bugs item #645906, was opened at 2002-11-30 01:52 Message generated for change (Comment added) made by zuse You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 beta Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Joe R. Doupnik (jdoupnik) Assigned to: Nobody/Anonymous (nobody) Summary: User supplied HTML with % kills index.ht Initial Comment: Mailman 2.1b5. Edit archtoc.html or listinfo.html, include table with phrase width=100% and find that the list's archive overall index.html page is unformed (present but the various MM items are left as bare %(foobar)s style). After wasting a whole day on this the problem boils down to that percent sign in user-supplied HTML. It kills the high level index.html file. We don''t know about this until a full list archive operation is performed, because at the end the code creates the new index.html from the template files. Ugh. Likely some parser deep in the system is overreacting to the percent symbol. Needs fixing. ---------------------------------------------------------------------- Comment By: Holger Jeromin (zuse) Date: 2007-03-15 14:48 Message: Logged In: YES user_id=254889 Originator: NO Thanks. That works. But is is not very obvious for a normal mailinglist admin when editing the "Welcome email text file" per webgui. It simply generates a wrong welcome email. It costs me 15 minutes of debugging the new message. A check would be very nice, at least a warning on top of the input field "write a single % as %%" should be done. ---------------------------------------------------------------------- Comment By: Holger Jeromin (zuse) Date: 2007-03-15 13:46 Message: Logged In: YES user_id=254889 Originator: NO The Problem might be solved for HTML pages, but it is not solved for text! When editing subscribeack.txt it is not possible to write something like "We can reach 20% of our users", because this leads to %(foobar)s stuff. In pure text there is no workaround like this width="100%" possible... My mailman provider uses version 2.1.9 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-08 16:12 Message: Logged In: YES user_id=12800 archtoc.html and listinfo.html are templates (as implied by their being in the templates/xx directory :) which means Python substitutions are performed on the text. Python substitutions treat % as a special character so to get a literal % in the text you need to use %% E.g. change that to "width=100%%" and you'll be fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_i…

14 years, 4 months

[ mailman-Bugs-645906 ] User supplied HTML with % kills index.ht

by SourceForge.net

Bugs item #645906, was opened at 2002-11-30 01:52 Message generated for change (Comment added) made by zuse You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 beta Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Joe R. Doupnik (jdoupnik) Assigned to: Nobody/Anonymous (nobody) Summary: User supplied HTML with % kills index.ht Initial Comment: Mailman 2.1b5. Edit archtoc.html or listinfo.html, include table with phrase width=100% and find that the list's archive overall index.html page is unformed (present but the various MM items are left as bare %(foobar)s style). After wasting a whole day on this the problem boils down to that percent sign in user-supplied HTML. It kills the high level index.html file. We don''t know about this until a full list archive operation is performed, because at the end the code creates the new index.html from the template files. Ugh. Likely some parser deep in the system is overreacting to the percent symbol. Needs fixing. ---------------------------------------------------------------------- Comment By: Holger Jeromin (zuse) Date: 2007-03-15 13:46 Message: Logged In: YES user_id=254889 Originator: NO The Problem might be solved for HTML pages, but it is not solved for text! When editing subscribeack.txt it is not possible to write something like "We can reach 20% of our users", because this leads to %(foobar)s stuff. In pure text there is no workaround like this width="100%" possible... My mailman provider uses version 2.1.9 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-08 16:12 Message: Logged In: YES user_id=12800 archtoc.html and listinfo.html are templates (as implied by their being in the templates/xx directory :) which means Python substitutions are performed on the text. Python substitutions treat % as a special character so to get a literal % in the text you need to use %% E.g. change that to "width=100%%" and you'll be fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=645906&group_i…

14 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders March 2007