Mailman 3 September 2002 - Mailman-Developers

Re: [Mailman-Developers] feature request: new option forreply_goes_to_list
by J C Lawrence Sept. 13, 2002

Sept. 13, 2002

On Fri, 13 Sep 2002 00:30:31 +0200 Simone Piunno <pioppo(a)ferrara.linux.it> wrote: > but on the usability side, the very common reply-to-list case is made > more difficult for the user (he can't 1-click-reply to the list only > [1]: he has to reply to all and then remove the unwanted addresses). You assumed that doing a group reply is (significantly) more difficult than doing a personal reply, as well as that the recipient list must be edited in either case. In general neither assumption is supportable. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

[ mailman-Bugs-608789 ] Stripped port info from List-Archive URL
by noreply＠sourceforge.net Sept. 13, 2002

Sept. 13, 2002

Bugs item #608789, was opened at 2002-09-13 07:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from List-Archive URL Initial Comment: I'm running Mailman 2.1b3 on a host with Apache running on port 2000. In mm_cfg.py, I have: DEFAULT_URL_PATTERN = 'http://%s:2000/mailman/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:2000/pipermail/%(listname)s' This works fine for HTML pages generated by the CGI scripts, as well as for the URLs sent out in the bodies of confirmation e-mails. However, the URLs contained in List-Archive headers in e-mails sent to lists do not have port 2000 in them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_i…

1 0

[ mailman-Bugs-608774 ] Stripped port info from DEFAULT_URL_HOST
by noreply＠sourceforge.net Sept. 13, 2002

Sept. 13, 2002

Bugs item #608774, was opened at 2002-09-13 06:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_i… Category: Web/CGI Group: 2.1 beta >Status: Deleted Resolution: None Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from DEFAULT_URL_HOST Initial Comment: I installed Mailman 2.1b3 on a Linux box with Apache 2 running on port 2000. I added the following lines to mm_cfg.py: DEFAULT_URL_HOST = "host.domain:2000" add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (host.domain is my hostname and domain name.) I then accessed http://host.domain:2000/mailman/admin and created a new list. The list was created just fine, except in the resulting "Mailing list creation results" page, the first two options ("Visit list info" and "Visit list admin") stripped port 2000 from the URL. Also, the confirmation e-mail I received also stripped port 2000 from the URLs. However, the third option ("Create another list") did have port 2000 in the URL. ---------------------------------------------------------------------- >Comment By: Eugene Eric Kim (eekim) Date: 2002-09-13 06:50 Message: Logged In: YES user_id=39362 Sorry. I realize now that I should have edited DEFAULT_URL_PATTERN instead of DEFAULT_URL_HOST. I did that, and the above problem went away. I also had to make sure I added a new PUBLIC_ARCHIVE_URL to my mm_cfg.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_i…

1 0

[ mailman-Bugs-608774 ] Stripped port info from DEFAULT_URL_HOST
by noreply＠sourceforge.net Sept. 13, 2002

Sept. 13, 2002

Bugs item #608774, was opened at 2002-09-13 06:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_i… Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from DEFAULT_URL_HOST Initial Comment: I installed Mailman 2.1b3 on a Linux box with Apache 2 running on port 2000. I added the following lines to mm_cfg.py: DEFAULT_URL_HOST = "host.domain:2000" add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (host.domain is my hostname and domain name.) I then accessed http://host.domain:2000/mailman/admin and created a new list. The list was created just fine, except in the resulting "Mailing list creation results" page, the first two options ("Visit list info" and "Visit list admin") stripped port 2000 from the URL. Also, the confirmation e-mail I received also stripped port 2000 from the URLs. However, the third option ("Create another list") did have port 2000 in the URL. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_i…

1 0

Keeping only the last X months of archives
by Terri Oda Sept. 13, 2002

Sept. 13, 2002

Someone suggested that on our job posting list, there was no point to keeping postings more than, say, 3 months old. It sounds like everyone agrees that it's a waste of space and it's probably up to me to implement something. It shouldn't be too hard to make a little cron script to move the older archives (I'm a pack rat with data, sometimes. ;) ) and clean & rebuild the html, but before I sit down and do it... is this already an option somewhere? Has anyone got an implementation already? And if not, would such a thing be useful to anyone else? Terri

1 0

[ mailman-Patches-433767 ] Subscriber Profiler
by noreply＠sourceforge.net Sept. 13, 2002

Sept. 13, 2002

Patches item #433767, was opened at 2001-06-16 13:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Swee Heng (sweeheng) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber Profiler Initial Comment: This is a patch to mailman-2.0.5 to implement a "subscriber profiler" feature. See my 2 postings on the mailing list for more details: o http://mail.python.org/pipermail/mailman-developers/2001-May/004270.html o http://mail.python.org/pipermail/mailman-developers/2001-June/004279.html Feel free to email me comments and queries at <sh--at--srikant.org>. (I finally figured out how to use SourceForge! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 22:40 Message: Logged In: YES user_id=17693 Hello... I install mailman from a RPM file... and install the patch manually... I need to know how COMPILE profile CGI-BIN file manually... do you know how? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_i…

1 0

Moderator's Interface
by Raquel Rice Sept. 12, 2002

Sept. 12, 2002

I've just upgraded to using Mailman 2.1b3, which provides for an "administrator" and a "moderator". In the password setup, I've specified seperate passwords and in the general options I've specified seperate addresses. However, at the admin login, the moderator cannot login using her password. Is there a seperate page for the moderator(s) to login? The only thing I've been able to find is "admindb" for moderation purposes, but not for adding/editing/removing subscriber info. I'm lost. Thanks! -- Raquel ============================================================ The true secret of giving advice is, after you have honestly given it, to be perfectly indifferent whether it is taken or not and never persist in trying to set people right. --Hannah Whitall Smith, Writer and Evangelist

1 0

[ mailman-Patches-483696 ] Categorisation of lists in ListInfo View
by noreply＠sourceforge.net Sept. 12, 2002

Sept. 12, 2002

Patches item #483696, was opened at 2001-11-20 04:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=483696&group_i… Category: Web UI Group: None Status: Open Resolution: None Priority: 5 Submitted By: andy (andy_cat) Assigned to: Nobody/Anonymous (nobody) Summary: Categorisation of lists in ListInfo View Initial Comment: This patch allows categorisation of lists when displaying the "list of lists" in listinfo.py and admin.py It does this by adding a new property to the MailList object called "categories", a new MailList member function called GetListCategories, and a dictionary making function in Utils.py Changed files are: listinfo.py admin.py Defaults.py MailList.py Utils.py Version.py htmlformat.py Preexisting lists will show up as "Unclassified" once you apply the patch and set LISTINFO_USE_CATEGORIES = 1 in Defaults.py To set the categories, either use the Mailman list admin GUI for the list and set the "categories affilations" value (a list can be in multiple categories) in the General Options page ( Configuration Categories ) or if you have many lists to categorise it will be easier to use command line python. $python -i bin/withlist <listname> Loading list: <listname> (unlocked) >>> m.Lock() >>> m.categories='testing' >>> m.Save() >>> Unlocking (but not saving) list: <listname> Finalizing substitute your lists name for <listname>, and if you have lots you may want to script this. Python code done by <wormwood(a)speakeasy.org> Patch and these docs by <andy(a)cat.org.au> ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 16:54 Message: Logged In: YES user_id=17693 Hello, I install your patch but the listinfo don't show the list names... admin is working ok... the problem is listinfo... if possible, see: http://lists.homelinux.com/mailman/listinfo,admin, etc Thanks, ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=483696&group_i…

1 0

[ mailman-Bugs-608524 ] QRUNNER is fucking the machine perform..
by noreply＠sourceforge.net Sept. 12, 2002

Sept. 12, 2002

Bugs item #608524, was opened at 2002-09-12 14:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 9 Submitted By: Jozeph Brasil (jozeph) Assigned to: Nobody/Anonymous (nobody) Summary: QRUNNER is fucking the machine perform.. Initial Comment: Hello Everybody, I'm with a big problem... :( I'm running mailman-2.0.13-1U70_1cl under python-2.1-14cl with gcc-2.95.3-20U70_1cl in an IBM NETFINITY 300 PIII 500 XEXON with 64MiB. When qrunner starts the proccess my machine stay totally SLOWLY... Look the qrunner proccess: mailman 12365 95.7 51.2 32340 30092 tty1 R 15:27 4:37 python -S cron/qrunner How you can see... look at the CPU / MEM usage... I need to wait more less 30 minutes to qrunner stop the proccess and... In qfiles directory have only 10 or 15 messages in delivery... Anyone have idea what's up? How fix that? PS: I disable my mailman at moment... :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_i…

1 0

[ mailman-Patches-413752 ] Coerce posts to plain text.
by noreply＠sourceforge.net Sept. 12, 2002

Sept. 12, 2002

Patches item #413752, was opened at 2001-04-04 14:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_i… Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 14:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=1… I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 14:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 13:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. <dairiki(a)dairiki.org> ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 12:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 01:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-28 00:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-27 21:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 16:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 12:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 12:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 13:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 16:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 17:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 16:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 15:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-19 20:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 16:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 01:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 01:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 01:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at <dairiki(a)dairiki.org>. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-08 00:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 13:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter <pug(a)pug.net> -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 12:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_i…

1 0