Mailman 3 February 2003 - Mailman-coders

[ mailman-Feature Requests-679743 ] mail-to and reply-to links for archive view
by SourceForge.net 03 Feb '03

03 Feb '03

Feature Requests item #679743, was opened at 2003-02-03 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) Summary: mail-to and reply-to links for archive view Initial Comment: I believe it would be very, very desirable to have mail-to and reply-to links in the mailing list archives section. I do not subscribe (to Zope mailing lists which are reported run on mailman) but do browse and, on occasion, am inspired enough to post. It would be a great convenience to have a mail-to (new thread) and reply-to (reply to currently displayed post) links to ease the process. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_i…

1 0

[ mailman-Patches-640518 ] SpamAssassin handler
by SourceForge.net 02 Feb '03

02 Feb '03

Patches item #640518, was opened at 2002-11-19 00:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_i… Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- >Comment By: Jon Parise (jparise) Date: 2003-02-02 21:39 Message: Logged In: YES user_id=485579 Yes, use the version with the "footsie" code. I don't appear to have permission to delete the older version from this patch tracker. It doesn't make any special exceptions with regard to the list owner, but I'll have a look at making that part of the logic smarter. ---------------------------------------------------------------------- Comment By: Shamanic Acid (shamanicacid) Date: 2003-01-28 02:18 Message: Logged In: YES user_id=698712 I am a bit confused in which SpamAssassin.py file to use. There does not seem to be an embedded version number in the download links. The diff I see is as follows: $ diff SpamAssassin.1.py SpamAssassin.py 62,65d61 < # First, play footsie with _ so that the following are marked as translated, < # but aren't actually translated until we need the text later on. < def _(s): < return s 71,73d66 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < 78,80d70 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < Question # 1. Do I want to use the SpamAssassin.py file with the "footsie" code? Question # 2. Does the SpamAssassin.py code allow for exceptions when the e-mail is from the $list-owner ( bounces to moderator ) ? I ask because I ran into a problem with a mailer-loop occuring when SpamAssassin errantly tagged the $list-owner moderator bounces as spam. ( spamassasin marks pending e-mails from $list-owner with score 7.6 ) I have not read through all the code, I am curious if mlist.isMember(sender) includes the owner alias? Many Thanks in Advance ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-12 11:01 Message: Logged In: YES user_id=485579 I've updated the SpamAssassin handler to report a more detailed reason when a DiscardMessage and HoldMessage exception is raised. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2002-12-31 19:33 Message: Logged In: YES user_id=485579 The attached patch adds the SpamAssassin handler to Mailman's mail processing pipelines. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_i…

1 0

[ mailman-Feature Requests-679234 ] Nested Lists(Segments) enhanced support
by SourceForge.net 02 Feb '03

02 Feb '03

Feature Requests item #679234, was opened at 2003-02-03 00:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679234&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rosstyk Ivantsiv (lumik) Assigned to: Nobody/Anonymous (nobody) Summary: Nested Lists(Segments) enhanced support Initial Comment: Imagine a simple situation: I run the tourism-related mailing list, which I use to send various proposals to other companies providing touristic services and located in different cities. I want to group all subscribers into groups(segments) depending, for example, on their geographic location. I consider some postings not to be interesting (even abusing) for some groups of subscribers, so I set the WHOLE group not to receive mail with a single operation and than send my posting to the list. Sure, this can be realized in current version of mailman by creating nested lists but it looks not to be the best choice. I advise you to realize some little segment support in mailman (probably based on a subscriber description). Here is the quote from Lyris documentation: "Let's say you'd like to send a special message to only those list members who - joined your list a week ago - live in France - are celebrating their birthday today - have made a major purchase in the last year - have an email address at a particular domain (e.g., aol.com or hotmail.com) ListManager allows you to send to a segment, or subset, of your list who meet the criteria you define. Instead of sending to your entire list, you can use segments to filter exactly who should get a message based on whatever criteria you choose. " Lyris(www.lyris.com) ListManager is a list manager with lots of features but it really sucks: -stupid unconvenient web-interface(pages reload many times to perform a simple operation) -it's not absolutely free(for example, to support segments I have to pay) -no internationalization!!! That's why I've chosen Mailman :) If you include some segment support in your next release, mailman will be 100%convenience system for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679234&group_i…

1 0

[ mailman-Bugs-678672 ] no list identification in cron error mail
by SourceForge.net 01 Feb '03

01 Feb '03

Bugs item #678672, was opened at 2003-02-01 14:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678672&group_i… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: no list identification in cron error mail Initial Comment: in the message below from the checkdbs cron job, there is no identification of the list with the erroneous `tuple'. it sure would be nice if there was. i ended up adding a print statement to checkdbs to find out what it was -- perhaps this could become a -v option to checkdbs. Finally, it sure would be nice if mailman just dealt with this problem instead of aborting. Thanks to help from mailman-users, I can get past it now by removing any relevant heldmsg's and removing request.db. Seems like this does not take a human to do. The error has happened with every mailman migration I've been involved in. Thanks, karl *** checkdbs Fri Jan 31 14:30:50 2003 --- checkdbs.v Fri Jan 31 14:45:50 2003 *************** *** 54,55 **** --- 54,56 ---- # the list must be locked in order to open the requests database + sys.stdout.write (name + '\n') mlist = MailList.MailList(name) Here's the mail. >From mailman(a)tug.org Sat Feb 1 02:00:04 2003 Return-Path: <mailman(a)tug.org> Received: from tug.org (tug.org [130.225.2.178]) by f7.net (8.11.6/8.11.6) with ESMTP id h11703p21212 for <karl(a)freefriends.org>; Sat, 1 Feb 2003 02:00:04 -0500 Received: (from mailman@localhost) by tug.org (8.11.6/8.11.6) id h11702s25380 for mailman; Sat, 1 Feb 2003 08:00:02 +0100 Message-Id: <200302010700.h11702s25380(a)tug.org> X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/home/mailman2> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=mailman> Date: Sat, 1 Feb 2003 08:00:02 +0100 From: root(a)tug.org (Cron Daemon) To: mailman(a)tug.org Subject: Cron <mailman@tug> /usr/local/bin/python -S /usr/local/mailman/cron/checkdbs Traceback (most recent call last): File "/usr/local/mailman/cron/checkdbs", line 136, in ? main() File "/usr/local/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/usr/local/mailman/cron/checkdbs", line 102, in pending_requests when, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) ValueError: unpack tuple of wrong size ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678672&group_i…

1 0

[ mailman-Bugs-678626 ] "error: incorrect padding"
by SourceForge.net 01 Feb '03

01 Feb '03

Bugs item #678626, was opened at 2003-02-01 11:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) >Summary: "error: incorrect padding" Initial Comment: Just ran the cvs update, and have started getting messages that otherwise look normal kicking this message out and shunting. Attached the errorlog. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-01 12:24 Message: Logged In: YES user_id=67709 Are you not using an external demime/stripmime? This kind of message is generated when an attatchment is base64 encoded but somehow corruped. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_i…

1 0

[ mailman-Bugs-678626 ] "error: incorrect padding"
by SourceForge.net 01 Feb '03

01 Feb '03

Bugs item #678626, was opened at 2003-02-01 11:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) >Summary: "error: incorrect padding" Initial Comment: Just ran the cvs update, and have started getting messages that otherwise look normal kicking this message out and shunting. Attached the errorlog. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_i…

1 0

[ mailman-Bugs-678626 ] "error: incorrect padding"
by SourceForge.net 01 Feb '03

01 Feb '03

Bugs item #678626, was opened at 2003-02-01 11:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: "error: incorrect padding" Initial Comment: Just ran the cvs update, and have started getting messages that otherwise look normal kicking this message out and shunting. Attached the errorlog. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_i…

1 0