Mailman-coders January 2004

mailman-coders@python.org

1 participants
74 discussions

[ mailman-Patches-644810 ] Sendmail mailer in Python
by SourceForge.net 02 Jan '04

02 Jan '04

Patches item #644810, was opened at 2002-11-27 16:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion <dgc(a)uchicago.edu> which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:20 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:33 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:31 Message: Logged In: YES user_id=75166 mailer-2.1.2-0.1.patch.gz removes support for MM 2.0.13 mail aliases from the mailer and is MM 2.1.2 compatible ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-03 18:19 Message: Logged In: YES user_id=75166 the mm_mailer script in mailer-2.1-0.2.patch now handles VERP'ed return addresses in bounced mail which I missed in the original implementation ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:34 Message: Logged In: YES user_id=75166 mailer-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 12:16 Message: Logged In: YES user_id=75166 mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds the case of listname and servername for compaiblity with MMs naive belief that listnames are case all lower case. case "(Email addresses are not case sensitive, but they are sensitive to almost everything else :-)" ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:37 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:36 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_i…

1 0

[ mailman-Patches-644797 ] Revised mailer exit status
by SourceForge.net 02 Jan '04

02 Jan '04

Patches item #644797, was opened at 2002-11-27 15:56 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i… Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:14 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:39 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:40 Message: Logged In: YES user_id=75166 exitstatus-2.1.2-0.1.patch is a revision of the patch for MM 2.1.2 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i…

1 0

[ mailman-Feature Requests-868838 ] More variables for use in templates
by SourceForge.net 01 Jan '04

01 Jan '04

Feature Requests item #868838, was opened at 2004-01-01 10:52 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=868838&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert H. Bourdeau (bourdeau) Assigned to: Nobody/Anonymous (nobody) Summary: More variables for use in templates Initial Comment: When a template is rendered, only selected variables are included- ones that we're imagined as necessary for the default Mailman templates. All variables that are not "template-specific" should be made available to every template. For example, when rendering the "article" template to present a single message in a list archive, the variable 'listinfo' is not in the dictionary for use by the template. However, 'listinfo' IS available for use to in "archtoc" template. 'listinfo' can be used to create a hyperlink from an article BACK to the list information page. Better yet, some additional URL variables would be helpful. I'd really rather link from an article back to the 'archtoc' page (set to the same sort order as when the user chose the article to view). That would be useful to always have in a variable. Basic principle here is that the SafeDict object that is used to render a template should always be as fully populated as possible. This gives the Mailman administrator (and list administrator) many more options for designing web pages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=868838&group_i…

1 0

[ mailman-Feature Requests-415137 ] CSS for webpage design.
by SourceForge.net 01 Jan '04

01 Jan '04

Feature Requests item #415137, was opened at 2001-04-10 08:00 Message generated for change (Comment added) made by bourdeau You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=415137&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: CSS for webpage design. Initial Comment: It would be very nice to be able to change the looks of the web pages by using CSS. Ie, include a <link href="default.css" .. on every page, and set tag classes so that they can be configured. ---------------------------------------------------------------------- Comment By: Robert H. Bourdeau (bourdeau) Date: 2004-01-01 10:40 Message: Logged In: YES user_id=941458 Absolutely. I've done this myself when customizing the various template files. Not only should this be changed, but I also suggest that the templates themselves be coded to make CSS customization easy. This means using DIV tags for sections to facilitate layout changes and/or class attributes to facilitate typographic customizations. ---------------------------------------------------------------------- Comment By: Phil Iovino (nxtek) Date: 2003-05-29 15:48 Message: Logged In: YES user_id=582938 I would like this as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=415137&group_i…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders January 2004