From noreply at sourceforge.net  Mon Oct  2 06:54:38 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 01 Oct 2006 21:54:38 -0700
Subject: [ mailman-Patches-1569059 ] Sender address cannot detected [2.1 / 2.2]
Message-ID: <E1GUFp8-0001jS-N6@sc8-sf-web2.sourceforge.net>

Patches item #1569059, was opened at 2006-10-02 13: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=1569059&group_id=103

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: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: ikedasoji (ikedasoji)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sender address cannot detected [2.1 / 2.2]

Initial Comment:
email.Utils.getaddresses() fails to pick up some
addresses, when header filed contains display-name
occupying whole one line or more.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1569059&group_id=103

From noreply at sourceforge.net  Mon Oct  2 06:55:11 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 01 Oct 2006 21:55:11 -0700
Subject: [ mailman-Patches-1569059 ] Sender address cannot be detected [2.1 /
	2.2]
Message-ID: <E1GUFpf-0000hm-K4@sc8-sf-web1.sourceforge.net>

Patches item #1569059, was opened at 2006-10-02 13:54
Message generated for change (Settings changed) made by ikedasoji
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1569059&group_id=103

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: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
>Priority: 7
Submitted By: ikedasoji (ikedasoji)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Sender address cannot be detected [2.1 / 2.2]

Initial Comment:
email.Utils.getaddresses() fails to pick up some
addresses, when header filed contains display-name
occupying whole one line or more.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1569059&group_id=103

From noreply at sourceforge.net  Mon Oct  2 09:41:02 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 02 Oct 2006 00:41:02 -0700
Subject: [ mailman-Patches-1569059 ] Sender address cannot be detected [2.1 /
	2.2]
Message-ID: <E1GUIQA-0000xl-Pv@sc8-sf-web2.sourceforge.net>

Patches item #1569059, was opened at 2006-10-02 13:54
Message generated for change (Comment added) made by ikedasoji
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1569059&group_id=103

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: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
>Priority: 9
Submitted By: ikedasoji (ikedasoji)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sender address cannot be detected [2.1 / 2.2]

Initial Comment:
email.Utils.getaddresses() fails to pick up some
addresses, when header filed contains display-name
occupying whole one line or more.


----------------------------------------------------------------------

>Comment By: ikedasoji (ikedasoji)
Date: 2006-10-02 16:41

Message:
Logged In: YES 
user_id=1553375

My description was inexact.

For example, when USE_ENVELOPE_SENDER = No and a message
contains:

From:
=?ISO-2022-JP?B?GyRCPHc4Qkw1PHc4Qkw1OF45ZSROOyQkakBaJGwzJDo9TXgbKEI=?=
 =?ISO-2022-JP?B?GyRCP2U1exsoQg==?= <jugemu at example.com>

msg.get_sender() returns:

=?ISO-2022-JP?B?GyRCPHc4Qkw1PHc4Qkw1OF45ZSROOyQkakBaJGwzJDo9TXgbKEI=?=


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1569059&group_id=103

From Peter.Soccar at bibalex.org  Mon Oct  2 09:42:32 2006
From: Peter.Soccar at bibalex.org (Peter Soccar)
Date: Mon, 2 Oct 2006 09:42:32 +0200
Subject: how do I add a new administrative role to mailman?
Message-ID: <AAA84820D5874F46B68C394C41FBBB22016CB0E1@SEXGW3K-H2010.local.bibalex.dom>

 

 

Hello,

I'm new to mailman, and I'm asked to find a way to add a new
administrative role in addition to the existing roles: (owner,
moderator)

i.e. I need to create something like "semi-owner" or
"advanced-moderator" that is to have some of the owners rights beside
the moderators right

 

any help will be extremely appreciated

 

Best Regards  

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/mailman-coders/attachments/20061002/190ec9f7/attachment.htm 

From Peter.Soccar at bibalex.org  Mon Oct  2 13:11:06 2006
From: Peter.Soccar at bibalex.org (Peter Soccar)
Date: Mon, 2 Oct 2006 13:11:06 +0200
Subject: source code for mailman 2.1.7-1.2
Message-ID: <AAA84820D5874F46B68C394C41FBBB2237E60B@SEXGW3K-H2010.local.bibalex.dom>


where, from which cvs repository can i download complete source code for mailman 2.1.7-1.2
thanks

From Peter.Soccar at bibalex.org  Mon Oct  2 13:18:33 2006
From: Peter.Soccar at bibalex.org (Peter Soccar)
Date: Mon, 2 Oct 2006 13:18:33 +0200
Subject: add new administration page like admin
Message-ID: <AAA84820D5874F46B68C394C41FBBB2237E60C@SEXGW3K-H2010.local.bibalex.dom>


how can i add a new administration page like admin or admindb to mailman
thanks

From msapiro at value.net  Mon Oct  2 16:42:14 2006
From: msapiro at value.net (Mark Sapiro)
Date: Mon, 2 Oct 2006 07:42:14 -0700
Subject: source code for mailman 2.1.7-1.2
In-Reply-To: <AAA84820D5874F46B68C394C41FBBB2237E60B@SEXGW3K-H2010.local.bibalex.dom>
Message-ID: <PC17602006100207421400625c02a4ec@msapiro>

Peter Soccar wrote:
>
>where, from which cvs repository can i download complete source code for mailman 2.1.7-1.2


Please do not post to mailman-coders at python.org. That list is only for
use by the SourceForge Mailman tracker to report changes.

There is no longer a cvs repository for Mailman. You can find the
subversion repository for the 2.1.7 release at
<http://svn.sourceforge.net/viewvc/mailman/tags/Release_2_1_7/>.

For subversion client access, see
<http://sourceforge.net/docman/?group_id=1> documents E09 and F06 or
F07.

As far as any differences between 2.1.7 and 2.1.7-1.2 are concerned,
you'll have to talk to whoever made your 2.1.7-1.2 package.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


From msapiro at value.net  Mon Oct  2 17:06:40 2006
From: msapiro at value.net (Mark Sapiro)
Date: Mon, 2 Oct 2006 08:06:40 -0700
Subject: how do I add a new administrative role to mailman?
In-Reply-To: <AAA84820D5874F46B68C394C41FBBB22016CB0E1@SEXGW3K-H2010.local.bibalex.dom>
Message-ID: <PC17602006100208064001875c02a583@msapiro>

Peter Soccar wrote:
>
>I'm new to mailman, and I'm asked to find a way to add a new
>administrative role in addition to the existing roles: (owner,
>moderator)


Please do not post to mailman-coders at python.org. That list is only for
use by the SourceForge Mailman tracker to report changes.

See my reply to your mailman-users at python.org post.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


From msapiro at value.net  Mon Oct  2 17:09:40 2006
From: msapiro at value.net (Mark Sapiro)
Date: Mon, 2 Oct 2006 08:09:40 -0700
Subject: add new administration page like admin
In-Reply-To: <AAA84820D5874F46B68C394C41FBBB2237E60C@SEXGW3K-H2010.local.bibalex.dom>
Message-ID: <PC17602006100208094008905c02a842@msapiro>

Peter Soccar wrote:
>
>how can i add a new administration page like admin or admindb to mailman


Please do not post to mailman-coders at python.org. That list is only for
use by the SourceForge Mailman tracker to report changes.

See my reply to your mailman-users at python.org post.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


From noreply at sourceforge.net  Tue Oct  3 12:55:07 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 03:55:07 -0700
Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index
Message-ID: <E1GUhvX-00044L-FX@sc8-sf-web5.sourceforge.net>

Patches item #444879, was opened at 2001-07-26 18:01
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103

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: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Archive indexer control to improve index

Initial Comment:
This patch is applicable to Mailman 2.0.6 release and 
supercedes ealier patches 401669 and 402422.

This patch should improve the quality of search 
results returned by search engines
such as htdig (http://www.htdig.org) where the seach 
engine's index builder responds 
to strings embedded in the html pages that are the 
subject of the indexing. The 
changes in this patch: 

1. allow strings for enabling and disabling indexing 
to be defined in mm_cfg.py.

2. embeds those strings in the pages generated as the 
html version of a list's
   archive.

By default nothing in the html changes. To get the 
desired effect, you must
define ARCHIVE_INDEXING_ENABLE and 
ARCHIVE_INDEXING_DISABLE in mm_cfg.py

You probably want to run this patch as follows:

cd &lt;mailman 2.0.6 untarred and unzipped directory&gt;
patch -p1 &lt; &lt;this patch file&gt;

See also the associated patch for integrating the 
htdig search software with mailman's internal archiver 
ouput.



----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 10:55

Message:
Logged In: YES 
user_id=75166

indexing-2.1.9-0.1.patch is a MM 2.1.9 compatible version of the

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 22:49

Message:
Logged In: YES 
user_id=75166

Use indexing-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:36

Message:
Logged In: YES 
user_id=75166

indexing-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 09:39

Message:
Logged In: YES 
user_id=75166

indexing-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-03 09:20

Message:
Logged In: YES 
user_id=75166

indexing-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-09-30 20:10

Message:
Logged In: YES 
user_id=75166

indexing-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:37

Message:
Logged In: YES 
user_id=75166

indexing-2.1.2-0.1.patch.gz no longer needs patch #661138 
to be applied as that patch was incorporated in the MM 2.1.2 
release

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 14:34

Message:
Logged In: YES 
user_id=75166

indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 
compatibility.

Before applying thisversion of the patch you must also apply 
Bug fix patch #728836 to the source distribution

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-10 15:49

Message:
Logged In: YES 
user_id=75166

indexing-2.1.1-0.1.patch.gz introduces no functional change 
but applies without offset warnings to MM 2.1.1

Before applying this patch to the MM 2.1 source distribution 
you must apply patch 661138 (corrects defects in some 
HTML templates) to the distribution


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-02 16:05

Message:
Logged In: YES 
user_id=75166

indexing-2.1-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1.

Before applying this patch to the MM 2.1 source distribution 
you must apply patch 661138 (corrects defects in some 
HTML templates) to the distribution

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:55

Message:
Logged In: YES 
user_id=75166

indexing-2.1b6-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b6

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:53

Message:
Logged In: YES 
user_id=75166

indexing-2.1b6-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b6

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:52

Message:
Logged In: YES 
user_id=75166

indexing-2.1b6-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b6

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 10:22

Message:
Logged In: YES 
user_id=75166

indexing-2.1b5-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b5

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-30 11:40

Message:
Logged In: YES 
user_id=75166

indexing-2.1b4-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b4

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-30 11:39

Message:
Logged In: YES 
user_id=75166

indexing-2.1b4-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b4

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-14 16:46

Message:
Logged In: YES 
user_id=75166

indexing-2.1b3-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b3

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-08 17:32

Message:
Logged In: YES 
user_id=75166

An additional file, README.NOINDEXtags is added to 
indexing-2.0.13-0.3.patch version that discusses the issue of 
what tags to use for controlling various search engine 
indexers.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-08 17:19

Message:
Logged In: YES 
user_id=75166

An error when building the indexing-2.1b2-0.1.patch meant 
that copies of the originals of two of the files modified by this 
version of the patch were added when the patch was run. 
indexing-2.1b2-0.1.patch removes this error. However, the 
original error is benign and can be corrected by deleting the 
extra files HyperArch.py.orig and Defaults.py.in.orig.

An additional file, README.NOINDEXtags is added that 
discusses the issue of what tags to use for controlling various 
search engine indexers.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 14:19

Message:
Logged In: YES 
user_id=12800

Another question: is there no standard (de-facto or
otherwise) for generic markup that tells indexers not to
index a particular section?  IOW, for
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is
there some generic value that would instruct most (all?)
indexers to ignore that section?  Or does it necessarily
have to be indexer specific?  

I'm thinking of the situation where you might have ht://Dig
installed locally, but your archives are still being
spidered by external indexers.  It would be good if
something more generic could be added to Defaults.py.in

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 14:14

Message:
Logged In: YES 
user_id=12800

Looking at the 2.1b2 patch, why does it try to create
HyperArch.py.orig and Defaults.py.in.orig?  Are those
included in the patch by mistake?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-05 10:08

Message:
Logged In: YES 
user_id=75166

indexing-2.0.13-0.2.patch just adds a GPL notice to the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-01 16:33

Message:
Logged In: YES 
user_id=75166

indexing-2.1b2-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b2

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-30 11:23

Message:
Logged In: YES 
user_id=75166

indexing-2.0.13-0.1.patch is purely cosmetic to get no 
mumble application to MM 2.0.13

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 14:11

Message:
Logged In: YES 
user_id=75166

indexing-2.0.11-0.1.patch should apply without problems to 
MM 2.0.12

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-05-23 09:50

Message:
Logged In: YES 
user_id=75166

indexing-2.0.11-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.11

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-19 10:53

Message:
Logged In: YES 
user_id=75166

indexing-2.0.9-0.1.patch should apply without problems to 
MM 2.0.10

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-08 17:43

Message:
Logged In: YES 
user_id=75166

indexing-2.0.9-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.9

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-03-06 16:14

Message:
Logged In: YES 
user_id=75166

indexing-2.1cvs-20020306.patch is a revised version of the  patch that is compatible with the code 
published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002.

Corrects problem noted or 5 Mar 2002 by nobody

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2002-03-05 21:41

Message:
Logged In: NO 

When applying this patch I get an error with Hunk 1 and 
Defaults.py is not updated. This happens with the a clean 
download of the latest cvs installation (5 Mar 2002). Any 
ideas what the problem is?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-17 16:53

Message:
Logged In: YES 
user_id=75166

indexing-2.1cvs-20011217.patch is a revised version of the 
patch that is compatible with the code published in mailman 
CVS on sourceforge as 11:50 GMT 17 Dec 2001

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-13 16:48

Message:
Logged In: YES 
user_id=75166

indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in 
mailman-2.1a3.tgz on sourceforge. 

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 11:07

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-27 12:03

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.7

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103

From noreply at sourceforge.net  Tue Oct  3 12:58:15 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 03:58:15 -0700
Subject: [ mailman-Patches-444884 ] Integration of Mailman and htdig for
	archiving
Message-ID: <E1GUhyZ-0004Nx-1P@sc8-sf-web5.sourceforge.net>

Patches item #444884, was opened at 2001-07-26 18:27
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

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: Unofficial 2.0 patch
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Integration of Mailman and htdig for archiving

Initial Comment:
This patch is applicable to Mailman 2.0.6 release that 
has had search enhancement patch 444879 patch 
installed - if your Defaults.py has the 
ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE 
in it then you've got that patch.

It replaces earlier patches 401670 and 402423 and is 
mainly to correct some problems arising from fixes 
introduced into Mailman by bug fix releases since the 
402423 patch. 

This patch integrates htdig with Mailman and provides:

1. per list search facility with a search form on the 
list's TOC page.

2. maintenance of privacy of private archives which 
requires the user to establish their credentials via 
the normal private archive access before any access 
via htdig is allowed.
   
3. a common base URL for both public and private 
archive access via htsearch results so that htdig 
indices are unaffected by changingan archive from 
private to public and vice versa. All access to 
archives via htdig is controlled by a new wrapped cgi-
bin script called htdig.py.
   
4. a new cron activated script and extra crontab entry 
which runs htdig regularly to maintain the per list 
search indices.
   
5. automatic creation, deletion and maintenance of 
htdig configuration files and such. Beyond installing 
htdig and telling Mailman where it is via mm_cfg you 
do not have to do any other setup. Well not quite you 
do have to set up a single per installation symlink to 
allow htdig to find the automatically generated per 
list htdig configuration files.

You probably want to run this patch as follows:

cd &lt;mailman 2.0.6 untarred and unzipped directory&gt;
patch -p1 &lt; &lt;this patch file&gt;  

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 10:58

Message:
Logged In: YES 
user_id=75166

htdig-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of the
patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 22:53

Message:
Logged In: YES 
user_id=75166

Use htdig-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:38

Message:
Logged In: YES 
user_id=75166

htdig-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 09:45

Message:
Logged In: YES 
user_id=75166

htdig-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-03 09:16

Message:
Logged In: YES 
user_id=75166

htdig-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-12-15 16:13

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.5.patch modifies htdig.py and private.py; the
security changes introduced by htdig-2.1.3-0.2 patch to
these scripts incorrectly  blocked access to the
listname.mbox/listname.mbox file. The 0.5 revision of the
patch corrects this error. This problem and a suggested fix
were pointed out to me in a private email by Stephan Berndts
stb-mm at spline.de

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:55

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.4.patch provides minor improvements in
handling of HTTP request handled by htidg.py which lead to
the user receiving an authentication challenge.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-19 21:13

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.3.patch.gz add minor private archive security
improvements to the patch for MM 2.1.3

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-09-30 20:14

Message:
Logged In: YES 
user_id=75166

htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-06 17:47

Message:
Logged In: YES 
user_id=75166

last comment should have read: 

htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, 
mmsearch.py and remote_mmsearch, which caused an 
exception if list archives were being accessed via HTTPS and 
a search was performed.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-06 17:45

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, 
mmsearch.py and remote_mmsearch, which caused an 
exception if list archives were being accessed via HTTPS and 
a search was performed.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-05-01 19:00

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.3.patch.gz adds some minor performance 
improvement in template handling in MM 2.1.2

You should consider also applying this bug-fis patch:

[ 730769 ] template access hierarchy is broken

http://sourceforge.net/tracker/index.php?
func=detail&amp;aid=730769&amp;group_id=103&amp;atid=100103

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 15:44

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as 
htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-04-28 14:46

Message:
Logged In: YES 
user_id=75166

htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 
compatibility.

It also incoporates a previosuly unpublished change to 
overcome a potential problem with htdig excluced urls - see 
the INSTALL.htdig-mm file for more information

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-21 18:29

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch 
handling multi-page search results from htsearch.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-21 17:54

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is 
rasing an excpetion because it has had a problem running 
htsearch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-03-20 14:10

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.2.patch.gz close a security exploit which allows 
leakage of information held in htdig's per-list search indexes 
to users not authorized to view private list archives.

Read file INSTALL.htdig-mm installed by this patch for details 
and instructions for upgrading MM installations using earlier 
versions of this patch



----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-10 15:50

Message:
Logged In: YES 
user_id=75166

htdig-2.1.1-0.1.patch.gz introduces no functional change but 
applies without offset warnings to MM 2.1.1

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-02-05 18:12

Message:
Logged In: YES 
user_id=75166

It seems it is possible, if this patch is installed, for a list's 
htdig conf file and the list specific htdig index db files to be 
read directly through the web interface for list archives. 

Even if this patch isn't installed it seems a list's pipermail.pck 
file can also be read directly through the web interface for list 
archives.

This seems to be true for accesses via /pipermail for public 
lists and via /mailman/private for private lists.

The problem does not occur for htdig search results 
accessed via /mailman/htdig as the htdig.py script is more 
protective than private.py

Broadly speaking the data affected is availble to a user in 
normal operation which is why I do not consider the issue to 
be a security breach as such.

Adding the following RewriteRule to Apache's httpd.conf 
prevents the situation, assuming you got the RewriteEngine 
On:

RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ 
$1/index.html [F]

RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ 
$1/index.htm
l [F]

You could, of course, substitute an R flag for the F flag on the 
RewriteRules and be more hacker friendly.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-22 14:20

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope 
that all of them!

Stops use of obsolete config variable DEFAULT_HOST in 
several files.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:18

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with 
an adverse interaction between htdig.py and a bug in 
$prefix/scripts/driver (see #668685 for a patch to fix this).

It also improves the content type and security handling by 
htdig.py for MM 2.1 version of patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:14

Message:
Logged In: YES 
user_id=75166

Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt.

Should have been htdig-2.0.13-0.4.patch which improves the 
content type and security handling by htdig.py for MM 2.0.13 
version of patch.

Please ignore mailer-2.0.13-0.4.patch file

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-15 20:09

Message:
Logged In: YES 
user_id=75166

mailer-2.0.13-0.4.patch improves the content type and 
security handling by htdig.py for MM 2.0.13 version of patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-01-02 16:07

Message:
Logged In: YES 
user_id=75166

htdig-2.1-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-11 11:48

Message:
Logged In: YES 
user_id=75166

htdig-2.1b6-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b6

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-12-04 10:53

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.3.patch corrects a minor typo in text appearing 
in the list TOC after the patch is applied.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-11-27 10:24

Message:
Logged In: YES 
user_id=75166

htdig-2.1b5-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b5

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-30 11:43

Message:
Logged In: YES 
user_id=75166

htdig-2.1b4-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b4

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-10-14 11:50

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.3.patch removes use of the file() function, used 
instead of the open() function, in three cron scripts added by 
the patch. Use of the file() function created an unnecessary 
dependency on Python 2.2

----------------------------------------------------------------------

Comment By: Colin Mackinlay (cmackinlay)
Date: 2002-10-12 16:51

Message:
Logged In: YES 
user_id=624179

Got a workaround!

The line referred to in the traceback:
 file(rundig_run_file, 'w').close()
is used to create a 'rundig_last_run' file of lenght 0 bytes
Creating this manually (or copying it) means the line isn't 
called and everything seems to work.

Either file() is not a valid function call or my python is broken - 
I'm not literate enough in python to know the answer though! 

----------------------------------------------------------------------

Comment By: Colin Mackinlay (cmackinlay)
Date: 2002-10-06 14:18

Message:
Logged In: YES 
user_id=624179

Just rebuilt MM as 2.1b3 with htdig.
Upgraded lists which had htdig before work fine
New lists give the obvious error:
  Unable to read word database file
  Did you run htmerge?
Running the cronjob doesn't fix as it used to, message is:
  Output from command /usr/bin/python -
S /usr/local/mailman/cron/nightly_htdig ..

Traceback (most recent call last):
  File &quot;/usr/local/mailman/cron/nightly_htdig&quot;, line 153, in ?
    main()
  File &quot;/usr/local/mailman/cron/nightly_htdig&quot;, line 118, in main
    file(rundig_run_file, 'w').close()
NameError: global name 'file' is not defined

The archive/htdig folder only contains the xx.conf file, but no 
db.xx files

If I copy in db.xx files from another list then the problem goes 
away (except I've now got an invalid set of references!)

Is this my elementary error or is it more sinister?!


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-15 11:02

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig-
2.1b3-0.1.patch which will typically show up as logged errors 
in the operation of the ArchRunner qrunner at line 721 of 
HyperArch.py

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-14 16:51

Message:
Logged In: YES 
user_id=75166

htdig-2.1b3-0.1.patch is a revised version of the patch that is 
compatible with MM 2.1b3

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-08 16:33

Message:
Logged In: YES 
user_id=12800

I've sent Richard some comments off-line about this patch.

Meta comments: the 2.0.x patches can't be officially
supported, but I'm going to create an unofficial patches
page off the wiki for where the 2.0 patches can be migrated.

I think this patch set is too big for MM2.1, but if it's
cleaned up as per my private message, let's re-evaluate it
for MM2.2 (or 3.0).

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-05 10:11

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.2.patch just adds a GPL notice to the patch


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-08-01 16:35

Message:
Logged In: YES 
user_id=75166

htdig-2.1b2-0.1.patch is a revised version of the patch 
that is compatible with MM 2.1b2

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-30 11:25

Message:
Logged In: YES 
user_id=75166

htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble 
application to MM 2.0.13

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 15:07

Message:
Logged In: YES 
user_id=75166

Do not use htdig-2.0.12-0.1.patch there is an error in it.
Use htdig-2.0.12-0.2.patch instead

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-07-25 14:10

Message:
Logged In: YES 
user_id=75166

htdig-2.0.12-0.1.patch is a revised version of the patch that 
applies without complaint to MM 2.0.12.

It also add a facility for adding site wide htdig configuration 
attributes to all list specific htdig configuration files. 



----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-05-23 09:59

Message:
Logged In: YES 
user_id=75166

htdig-2.0.11-0.1.patch is a revised version of the patch that 
is compatible with MM 2.0.11

This version removes an incompatibility with Python 2.2 
which caused warning messages to be generated when any 
of the family cron/nightly_htdig scripts were run.

Some guidance on file access permissions for some htdig 
database files needed by rundig have been added to 
installation notes.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-19 10:59

Message:
Logged In: YES 
user_id=75166

htdig-2.0.10-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.10

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-04-08 17:46

Message:
Logged In: YES 
user_id=75166

htdig-2.0.9-0.1.patch is a revised version of the patch 
that is compatible with MM 2.0.9

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2002-03-06 16:22

Message:
Logged In: YES 
user_id=75166

htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in 
mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002

Known deficiency is that the non-English versions of files under $build/templates still contain text in English 
and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in 
files under $build/messages remain to be done.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-17 16:56

Message:
Logged In: YES 
user_id=75166

htdig-2.1cvs-20011217.patch is a revised version of the 
patch that is compatible with the code published in mailman 
CVS on sourceforge as 11:50 GMT 17 Dec 2001

The only known deficiency is that the non-English versions 
of files under $build/templates still contain text in 
English and need translations I cannot do. Also the 
necessary pygettext activity and subsequent translations in 
files under $build/messages remain to be done.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-12-13 16:58

Message:
Logged In: YES 
user_id=75166

htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in 
mailman-2.1a3.tgz on sourceforge.

The only known deficiency is that the non-English versions of files under $build/templates still contain text 
in English and need translations I cannot do. Also the necessary pygettext activity and subsequent 
translations in files under $build/messages remain to be done. 

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 17:33

Message:
Logged In: YES 
user_id=75166

The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the 
web_page_url for a list uses other than the http addressing (some folks want to use https). While specified 
as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If 
you do not have the requirement for using other than http addressing in you lists web_page_urls it probably 
isn't worth the trouble of upgrading to this patch level.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-28 11:08

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to MM 2.0.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-27 12:00

Message:
Logged In: YES 
user_id=75166

This patch should also apply without problems to Mm 2.0.7

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2001-11-09 11:54

Message:
Logged In: YES 
user_id=75166

The htdig-2.0.6-03.patch version of the patch makes some 
previously hard-coded things configurable and enhances the 
capability to run the htdig searches and indexing on a 
different machine to the one delivering Mailman and 
Mailman's web UI.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103

From noreply at sourceforge.net  Tue Oct  3 13:00:42 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:00:42 -0700
Subject: [ mailman-Patches-644797 ] Revised mailer exit status
Message-ID: <E1GUi0w-0004ar-GC@sc8-sf-web5.sourceforge.net>

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_id=103

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: 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 &lt; patch-filename

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:00

Message:
Logged In: YES 
user_id=75166

Use exitstatus-2.1.7-0.1.patch.gz for MM 2.1.9

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 22:55

Message:
Logged In: YES 
user_id=75166

Use exitstatus-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:46

Message:
Logged In: YES 
user_id=75166

exitstatus-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 09:56

Message:
Logged In: YES 
user_id=75166

exitstatus-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the 
patch

----------------------------------------------------------------------

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_id=103

From noreply at sourceforge.net  Tue Oct  3 13:03:07 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:03:07 -0700
Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python
Message-ID: <E1GUi3G-0004sj-Tb@sc8-sf-web5.sourceforge.net>

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_id=103

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: Mailman 2.1
>Status: Closed
>Resolution: Out of Date
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 &lt;dgc at uchicago.edu&gt; 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 &lt; patch-filename 

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:03

Message:
Logged In: YES 
user_id=75166

This patch is no longer being maintained.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 10:43

Message:
Logged In: YES 
user_id=75166

mailer-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:23

Message:
Logged In: YES 
user_id=75166

mailer-2.1.3-0.2.patch can be used with MM 2.1.4

----------------------------------------------------------------------

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 &quot;(Email addresses are not case sensitive, but they are 
sensitive to almost everything else :-)&quot;


----------------------------------------------------------------------

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_id=103

From noreply at sourceforge.net  Tue Oct  3 13:05:00 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:05:00 -0700
Subject: [ mailman-Patches-760567 ] moderation request message content
Message-ID: <E1GUi56-00052I-Ii@sc8-sf-web5.sourceforge.net>

Patches item #760567, was opened at 2003-06-25 15:25
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103

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: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: moderation request message content

Initial Comment:
This patch makes per-list configurable the inclusion of 
the body of messages that require moderation in the 
request messages sent to list moderators.

This patch has similar objectives to those of patch 
#593674 but is a simpler implementation.

This adds one list attribute, which can be set or unset 
via the web admin GUI, and which controls whether the 
moderated message body is included in the moderator 
request.

Apply the attached patch file with the MM build 
directory as the current working directory using the 
command:

patch -p1 &lt; path-to-patch-file



----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:05

Message:
Logged In: YES 
user_id=75166

modinc-2.1.9-0.1.patch is a MM 2.1.9 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 22:59

Message:
Logged In: YES 
user_id=75166

Use modinc-2.1.7-0.1.patch for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:41

Message:
Logged In: YES 
user_id=75166

modinc-2.1.6-0.1.patch is a MM 2.1.6 compatible version of the
patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 10:02

Message:
Logged In: YES 
user_id=75166

modinc-2.1.5-0.1.patch is a MM 2.1.5 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:28

Message:
Logged In: YES 
user_id=75166

modinc-2.1.4-0.1.patch is a MM 2.1.4 compatible veriosn of
this patch

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-12-24 17:29

Message:
Logged In: YES 
user_id=12800

I'm going to defer this one until 2.1.5 since I don't want
to add any new list attributes at this late date.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-09-30 20:43

Message:
Logged In: YES 
user_id=75166

modinc-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-06-25 17:21

Message:
Logged In: YES 
user_id=75166

Missed one changed file from initial patch

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103

From noreply at sourceforge.net  Tue Oct  3 13:08:56 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:08:56 -0700
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
Message-ID: <E1GUi8u-0005QA-PX@sc8-sf-web5.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:08

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 23:01

Message:
Logged In: YES 
user_id=75166

Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-03-02 21:17

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of 
Mailman/Cgi/create.py which fails to get the initial setup of lists created 
through the web quite right. This leads to spurious errors being logged on 
message archiving until bin/arch --wipe is run for such a list affected. Lists 
created with bin/newlist did not have this problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-09-23 21:45

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of 
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the 
problem was not present in patches for previous MM versions. In some 
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a 
list my be generated using the wrong archiver. Examining index pages in 
the archives of a list will show if this problem has affected that list. 
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe 
should resolve the problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:43

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

----------------------------------------------------------------------

Comment By: dfragos (dfragos)
Date: 2005-07-21 15:24

Message:
Logged In: YES 
user_id=1310569

what about MM 2.1.6?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 10:04

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-19 23:53

Message:
Logged In: YES 
user_id=696559

I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 05:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Tue Oct  3 13:14:00 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:14:00 -0700
Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting
	measure
Message-ID: <E1GUiDo-0005uL-Tp@sc8-sf-web5.sourceforge.net>

Patches item #850805, was opened at 2003-11-28 16:23
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103

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: Mailman 2.1
Status: Open
Resolution: Postponed
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Aggressive anti email address harvesting measure

Initial Comment:
This patch is prompted by discussion on the mailman-
developers list won the following subject:

Re: [Mailman-Developers] bugtraq submission warning: 
email address harvesting exploit

For those with deep concerns about email address harvesting 
this patch offers a more aggressive masking of email 
addresses in Mailman mail archive files.

The patch modifes two files in the standard Mailman 
distribution: Mailman/Defaults.py and Mailman/Cgi/
private.py and can be applied using the following command 
from within the Mailman build directory:

    path -p1 &lt; path-to-patch-file
    
It would be fairly trivial to make enabling this feature per-
list configurable rather than it being a site admin decision 
and I will enhance this patch for that purpose if people show 
an interest in it being done.

The following notes about the patch can be found in 
Defaults.py. Rather idiosyncratically most of the operational 
elements of this patch are in that file. My reasoning behind 
this decision is that if people want to fool with the regexes 
that are at the heart of this patch they can see what will be 
affected by the changes more readily if the related bits are 
in the same place.


#####
# Anti-spam email address harvesting prevention measures.
#
# These measures are to limit the ability of spam generators 
to acquire
# email address from archived material in Mailman's list 
archives.
# Implementation is via a dynamic search and replace for 
email
# addresses, appearing in files of MIME type text/html or 
text/plain, as
# those files are requested. The underlying archive file 
content as 
# generated by the archiving software remains unchanged.
#
# The implementation requires that archive files are all 
delivered by a
# modified private.py CGI script which only requires user 
authentication 
# if the list whose archive material is being requested is set 
up as a private
# list. In order to get public archives served by private.py a 
RewriteRule
# like this:
#
#     RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT]
#
# needs to be used in the Apache httpd.conf to transparently 
redirect 
# public arechive file requests.
#
# When email addresses are found, the domain part of the 
addressed is replaced
# with a string of 'x' characters. If the local part of the 
address appears to 
# have been VERP'ed then the VERP information is similarly 
obscured. This is
# a fairly brutal set of irreversible modifications to any 
email addresses in 
# the returned text and will break any mailto: links in the 
text.
#
# Th eamil address regex looks for either an '@' character 
or its HTML escaped
# version '%40' as the local-part/domain separator. You 
should set
# ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch 
to rebuild existing archives 
# to prevent that feature interfering with the operation of 
these harvesting 
# prevention measures.
#
# If you decide to change the regexes then copy all of this 
stuff into
# mm_cfg.py and make the changes there.
#
#####


----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:14

Message:
Logged In: YES 
user_id=75166

antispam-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

----------------------------------------------------------------------

Comment By: O.S. (olaf)
Date: 2004-11-14 00:41

Message:
Logged In: YES 
user_id=11209

please, make these harvesting prevention measures per list configurable.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2004-11-14 00:28

Message:
Logged In: YES 
user_id=67709

Sorry, patch itself is for 2.1 (not 3.0).


----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2004-11-14 00:27

Message:
Logged In: YES 
user_id=67709

It looks nice but it may be too much for 2.1.x where the
archives are generated static. Also, I'm a little bit
anxious writing such a function in Defaults.py. It would be
better to include this feature in 3.0 or later.


----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-20 09:52

Message:
Logged In: YES 
user_id=696559

Ohh, sorry, the patch really wasn't applied. After proper
installation, I can confirm it works fine.

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-20 00:00

Message:
Logged In: YES 
user_id=696559

What sould I do with this error caused by the patch?

Traceback (most recent call last):
  File "/usr/local/mailman/scripts/driver", line 87, in run_main
    main()
  File "/usr/local/mailman/Mailman/Cgi/private.py", line
165, in main
    sys.stdout.write(mm_cfg.deny_harvest(f.read()))
AttributeError: 'module' object has no attribute 'deny_harvest'




----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-11-30 07:02

Message:
Logged In: YES 
user_id=75166

As pointed out on the mailman-developers list, potential users of 
this patch should be aware that the simple approach to masking 
email addresses used by this patch will also capture and munge 
any other strings in the archive data that resemble email 
addresses. This can include mailto URLs, other URLs and Message 
ids. This side-effect may make the patch unsuitable for use with 
your system, although you also need to consider that the patch 
does not irreversibly change the source pipermail archived 
material held on the server; the changes are only made in the 
copy of the archive material sent to the requesting browser by the 
server.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103

From noreply at sourceforge.net  Tue Oct  3 13:53:53 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:53:53 -0700
Subject: [ mailman-Patches-1442025 ] List Specialisation for Support Groups
Message-ID: <E1GUiqP-0004NG-OL@sc8-sf-web4.sourceforge.net>

Patches item #1442025, was opened at 2006-03-02 20:32
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1442025&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: List Specialisation for Support Groups

Initial Comment:
This patch modifies Mailman to address the following scenario: 

1. A Mailman list to be used as the means by which a closed set of list 
subcribers (support staff) can provide responses to requests for 
support made by non-subscribers (customers) posting messages to the 
list. 

2. Requirement that the incoming posts from customers (both original 
and follow up) and consequential responses from support staff should 
be entirely list-centric:

    a. The customer should see the response to a posting to the list as 
coming from the list, not the support person that responded.
    
    b. Any subsequent reply by the customer to a message from the list 
should go back to the list.
    
    c. Replies to customers by support staff should automatically be 
distributed to the the list.
    
    d. This should all happen by use of the basic features of typical 
MUAs by both support staff and customers; use of the MUA GUI's 
"Reply" button should do all that is necessary.

    e. Using the list in the way described should require no or minimal 
explanation to support staff and absolutely no explanation to 
customers.

    f. The e-mail addresses of support staff should remain hidden 
behind the list address.

For more detail of implementation see:

http://www.openinfo.co.uk/mm/patches/supportlist/index.html


----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:53

Message:
Logged In: YES 
user_id=75166

response-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-20 06:15

Message:
Logged In: YES 
user_id=75166

Use response-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1442025&group_id=103

From noreply at sourceforge.net  Tue Oct  3 13:58:32 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 03 Oct 2006 04:58:32 -0700
Subject: [ mailman-Patches-1483446 ] Daily mbox files for list mbox archives
Message-ID: <E1GUius-0004qv-Qv@sc8-sf-web4.sourceforge.net>

Patches item #1483446, was opened at 2006-05-07 18:14
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1483446&group_id=103

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: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Daily mbox files for list mbox archives

Initial Comment:
The daily mbox patch changes the way Mailman does its archive-to-mbox 
archiving, if that is enabled.

The standard Mailman system single .mbox file per list used for mbox 
archiving can, over time, become very unwieldy, presenting problems for 
disk space management.

The mailman daily mbox patch modifies Mailman's behaviour so that a 
sparse series of daily mbox files is used for archiving rather than a single 
mbox file. Each archived message is normally appended to a daily mbox 
file for the UTC date when the message is first archived.

For more information, download the patch and check out the file 
README.dailymbox or visit the URL http://www.openinfo.co.uk/mm/
patches/dailymbox/

Apply the patch from within the Mailman build directory using the 
command: 

    patch -p1 &lt; path-to-patch-file


----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:58

Message:
Logged In: YES 
user_id=75166

Uae dailymbox-2.1.8-0.1.patch.gz for MM 2.1.9

----------------------------------------------------------------------

Comment By: Jim Popovitch (jimpop)
Date: 2006-05-28 21:10

Message:
Logged In: YES 
user_id=3142

Working very well on a production system.  Nice addition to
Mailman, makes file management and backups MUCH easier.

Thanks!!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1483446&group_id=103

From noreply at sourceforge.net  Fri Oct  6 18:34:58 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 06 Oct 2006 09:34:58 -0700
Subject: [ mailman-Bugs-1572256 ] -1 moderator request(s) waiting
Message-ID: <E1GVsf4-0007vy-V6@sc8-sf-web5.sourceforge.net>

Bugs item #1572256, was opened at 2006-10-06 09: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=1572256&group_id=103

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: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Roberts (timroberts)
Assigned to: Nobody/Anonymous (nobody)
Summary: -1 moderator request(s) waiting

Initial Comment:
I run a dozen or more mailing lists with Mailman 2.1.5.
 Last night, I created a new list, but instead of using
the command line like usual, I decided to use the web
interface.  This morning I received an admin email saying:

The Eleets at probo.com mailing list has -1 request(s)
waiting for your consideration at: ...

If I bring up the admin page, it shows me the
instructions as if there were admin requests, but no
requests are listed.

A minor issue, to be sure, but interesting...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1572256&group_id=103

From noreply at sourceforge.net  Fri Oct  6 19:19:36 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 06 Oct 2006 10:19:36 -0700
Subject: [ mailman-Bugs-1572256 ] -1 moderator request(s) waiting
Message-ID: <E1GVtMG-0002AX-UK@sc8-sf-web6.sourceforge.net>

Bugs item #1572256, was opened at 2006-10-06 09:34
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1572256&group_id=103

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: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Tim Roberts (timroberts)
Assigned to: Nobody/Anonymous (nobody)
Summary: -1 moderator request(s) waiting

Initial Comment:
I run a dozen or more mailing lists with Mailman 2.1.5.
 Last night, I created a new list, but instead of using
the command line like usual, I decided to use the web
interface.  This morning I received an admin email saying:

The Eleets at probo.com mailing list has -1 request(s)
waiting for your consideration at: ...

If I bring up the admin page, it shows me the
instructions as if there were admin requests, but no
requests are listed.

A minor issue, to be sure, but interesting...

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-06 10:19

Message:
Logged In: YES 
user_id=1123998

Fixed in 2.1.6. See
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.038.htp

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1572256&group_id=103

From noreply at sourceforge.net  Mon Oct  9 01:36:08 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 08 Oct 2006 16:36:08 -0700
Subject: [ mailman-Bugs-1573392 ] http://list.org/bugs.html mangled text
Message-ID: <E1GWiBk-0007rT-HN@sc8-sf-web3.sourceforge.net>

Bugs item #1573392, was opened at 2006-10-09 08:36
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=1573392&group_id=103

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: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Jim Tittsler (jtittsler)
Assigned to: Nobody/Anonymous (nobody)
Summary: http://list.org/bugs.html mangled text

Initial Comment:
On #mailman IRC 'Piet' reported the text of the first
sentence of http://list.org/bugs.html is broken:

Although we are currently transitioning to Atlassian's
the fine bug tracker called Jira, we are still
accepting bugs via the Please use the SourceForge bug
tracker. For now, if you have patches you'd like to
submit, the best place to do that is on the SourceForge
patch manager.

P.S.  There probably should be a 'website' bugs category.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1573392&group_id=103

From noreply at sourceforge.net  Mon Oct  9 01:37:13 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 08 Oct 2006 16:37:13 -0700
Subject: [ mailman-Bugs-1573393 ] Missing handling for unexpected content of
	'varhelp'
Message-ID: <E1GWiCn-00049K-1I@sc8-sf-web2.sourceforge.net>

Bugs item #1573393, was opened at 2006-10-09 01:37
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=1573393&group_id=103

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/CGI
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Moritz Naumann (mnaumann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing handling for unexpected content of 'varhelp'

Initial Comment:
Invoking
  /mailman/admin/mailman/?VARHELP=/
after having logged in triggers an error.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1573393&group_id=103

From noreply at sourceforge.net  Mon Oct  9 23:34:22 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 09 Oct 2006 14:34:22 -0700
Subject: [ mailman-Feature Requests-1574060 ] export member list in web
	interface
Message-ID: <E1GX2lS-0006GE-Hf@sc8-sf-web2.sourceforge.net>

Feature Requests item #1574060, was opened at 2006-10-09 23:34
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=1574060&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: export member list in web interface

Initial Comment:
our users / mailman list owners really would like to
have the possability to export the member list into an
text and / or csv file using the web interface

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574060&group_id=103

From noreply at sourceforge.net  Mon Oct  9 23:36:35 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 09 Oct 2006 14:36:35 -0700
Subject: [ mailman-Feature Requests-1574062 ] changing member options in
	web-interface
Message-ID: <E1GX2nb-0006Sh-5t@sc8-sf-web2.sourceforge.net>

Feature Requests item #1574062, was opened at 2006-10-09 23:36
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=1574062&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: changing member options in web-interface

Initial Comment:
our users / list owners would like it very much to have
the possability to change any subscription - option
globally for all list members using the web interface.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574062&group_id=103

From noreply at sourceforge.net  Mon Oct  9 23:39:19 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 09 Oct 2006 14:39:19 -0700
Subject: [ mailman-Feature Requests-1574066 ] show list members in web
	interface
Message-ID: <E1GX2qF-0006kn-LT@sc8-sf-web2.sourceforge.net>

Feature Requests item #1574066, was opened at 2006-10-09 23:39
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=1574066&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: show list members in web interface

Initial Comment:
our users / list owners would like it very much to have
the possability to get a list of ALL users one one page
in the web.interface

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

From noreply at sourceforge.net  Mon Oct  9 23:41:28 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 09 Oct 2006 14:41:28 -0700
Subject: [ mailman-Feature Requests-1574060 ] export member list in web
	interface
Message-ID: <E1GX2sK-0006xN-Nt@sc8-sf-web2.sourceforge.net>

Feature Requests item #1574060, was opened at 2006-10-09 23:34
Message generated for change (Comment added) made by ulph
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574060&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: export member list in web interface

Initial Comment:
our users / mailman list owners really would like to
have the possability to export the member list into an
text and / or csv file using the web interface

----------------------------------------------------------------------

>Comment By: ulph (ulph)
Date: 2006-10-09 23:41

Message:
Logged In: YES 
user_id=1617063

... of course including member names

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574060&group_id=103

From noreply at sourceforge.net  Mon Oct  9 23:46:31 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 09 Oct 2006 14:46:31 -0700
Subject: [ mailman-Feature Requests-1574070 ] fix_url make url indeoendent
	from host_name
Message-ID: <E1GX2xD-0007Rt-3h@sc8-sf-web2.sourceforge.net>

Feature Requests item #1574070, was opened at 2006-10-09 23:46
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=1574070&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix_url make url indeoendent from host_name

Initial Comment:
we just moved with our mailserver. for each list i had to
bin/withlist -l -r fix_url listname -u urlhost

but then, not only the url of the list changed, what i
wanted, but also the host_name which we use for the
virtual domain name of each list. so i had to change
that back manually afterwards. thats not so nice! at
least, because i have to do that again for each list ...



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574070&group_id=103

From noreply at sourceforge.net  Tue Oct 10 00:20:21 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 09 Oct 2006 15:20:21 -0700
Subject: [ mailman-Bugs-1573392 ] http://list.org/bugs.html mangled text
Message-ID: <E1GX3Tx-0001Ur-Hs@sc8-sf-web1.sourceforge.net>

Bugs item #1573392, was opened at 2006-10-08 19:36
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1573392&group_id=103

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: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Jim Tittsler (jtittsler)
Assigned to: Nobody/Anonymous (nobody)
Summary: http://list.org/bugs.html mangled text

Initial Comment:
On #mailman IRC 'Piet' reported the text of the first
sentence of http://list.org/bugs.html is broken:

Although we are currently transitioning to Atlassian's
the fine bug tracker called Jira, we are still
accepting bugs via the Please use the SourceForge bug
tracker. For now, if you have patches you'd like to
submit, the best place to do that is on the SourceForge
patch manager.

P.S.  There probably should be a 'website' bugs category.


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2006-10-09 18:20

Message:
Logged In: YES 
user_id=12800

r8053

I'm sure we'll create a website category when we actually
complete the move to Jira.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1573392&group_id=103

From noreply at sourceforge.net  Wed Oct 11 05:12:26 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 10 Oct 2006 20:12:26 -0700
Subject: [ mailman-Feature Requests-1574060 ] export member list in web
	interface
Message-ID: <E1GXUWA-0004Aa-7l@sc8-sf-web3.sourceforge.net>

Feature Requests item #1574060, was opened at 2006-10-09 14:34
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574060&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: export member list in web interface

Initial Comment:
our users / mailman list owners really would like to
have the possability to export the member list into an
text and / or csv file using the web interface

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-10 20:12

Message:
Logged In: YES 
user_id=1123998

I know this isn't what you're asking for, but there are
scripts that can obtain this information from the admin
Membership List web interface. See
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.062.htp
for more information and links to some scripts.

----------------------------------------------------------------------

Comment By: ulph (ulph)
Date: 2006-10-09 14:41

Message:
Logged In: YES 
user_id=1617063

... of course including member names

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574060&group_id=103

From noreply at sourceforge.net  Wed Oct 11 17:48:22 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 11 Oct 2006 08:48:22 -0700
Subject: [ mailman-Feature Requests-1574066 ] show list members in web
	interface
Message-ID: <E1GXgJi-00006f-PJ@sc8-sf-web2.sourceforge.net>

Feature Requests item #1574066, was opened at 2006-10-09 14:39
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: show list members in web interface

Initial Comment:
our users / list owners would like it very much to have
the possability to get a list of ALL users one one page
in the web.interface

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 08:48

Message:
Logged In: YES 
user_id=1123998

Would the current 'roster' page be sufficient if it showed
ALL members to a user logged in with the list admin or site
password?

See request # 782436 for a related request.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

From noreply at sourceforge.net  Wed Oct 11 17:56:06 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 11 Oct 2006 08:56:06 -0700
Subject: [ mailman-Feature Requests-1574066 ] show list members in web
	interface
Message-ID: <E1GXgRC-0005aN-Jw@sc8-sf-web1.sourceforge.net>

Feature Requests item #1574066, was opened at 2006-10-09 17:39
Message generated for change (Comment added) made by jimpop
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: show list members in web interface

Initial Comment:
our users / list owners would like it very much to have
the possability to get a list of ALL users one one page
in the web.interface

----------------------------------------------------------------------

Comment By: Jim Popovitch (jimpop)
Date: 2006-10-11 11:56

Message:
Logged In: YES 
user_id=3142

I don't think so Mark.  I think there needs to be a way to
"click and download" a list of members that can be saved as
a backup.  Then one day in the future add a feature to
"click and upload" a membership list to import those members
into the system.  This way bob's list at providerA could
very easily be moved to providerB without much worry by bob. 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 11:48

Message:
Logged In: YES 
user_id=1123998

Would the current 'roster' page be sufficient if it showed
ALL members to a user logged in with the list admin or site
password?

See request # 782436 for a related request.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

From noreply at sourceforge.net  Wed Oct 11 18:06:20 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 11 Oct 2006 09:06:20 -0700
Subject: [ mailman-Feature Requests-1574066 ] show list members in web
	interface
Message-ID: <E1GXgb6-0006eJ-Sm@sc8-sf-web1.sourceforge.net>

Feature Requests item #1574066, was opened at 2006-10-09 14:39
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: show list members in web interface

Initial Comment:
our users / list owners would like it very much to have
the possability to get a list of ALL users one one page
in the web.interface

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 09:06

Message:
Logged In: YES 
user_id=1123998

I understand what you're saying Jim, and I agree, but I
think that is RFE 1574060 by the same submitter, so I think
this RFE is for something different.

----------------------------------------------------------------------

Comment By: Jim Popovitch (jimpop)
Date: 2006-10-11 08:56

Message:
Logged In: YES 
user_id=3142

I don't think so Mark.  I think there needs to be a way to
"click and download" a list of members that can be saved as
a backup.  Then one day in the future add a feature to
"click and upload" a membership list to import those members
into the system.  This way bob's list at providerA could
very easily be moved to providerB without much worry by bob. 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 08:48

Message:
Logged In: YES 
user_id=1123998

Would the current 'roster' page be sufficient if it showed
ALL members to a user logged in with the list admin or site
password?

See request # 782436 for a related request.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

From noreply at sourceforge.net  Wed Oct 11 18:15:24 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 11 Oct 2006 09:15:24 -0700
Subject: [ mailman-Feature Requests-1574066 ] show list members in web
	interface
Message-ID: <E1GXgjs-0007Gt-2S@sc8-sf-web6.sourceforge.net>

Feature Requests item #1574066, was opened at 2006-10-09 17:39
Message generated for change (Comment added) made by jimpop
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

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
Submitted By: ulph (ulph)
Assigned to: Nobody/Anonymous (nobody)
Summary: show list members in web interface

Initial Comment:
our users / list owners would like it very much to have
the possability to get a list of ALL users one one page
in the web.interface

----------------------------------------------------------------------

Comment By: Jim Popovitch (jimpop)
Date: 2006-10-11 12:15

Message:
Logged In: YES 
user_id=3142

I can't imagine the submitter wanted two different, yet
related, features.  I would say this RFE could be closed if
 RFE 1574060 is going forward.  (IMHO)

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 12:06

Message:
Logged In: YES 
user_id=1123998

I understand what you're saying Jim, and I agree, but I
think that is RFE 1574060 by the same submitter, so I think
this RFE is for something different.

----------------------------------------------------------------------

Comment By: Jim Popovitch (jimpop)
Date: 2006-10-11 11:56

Message:
Logged In: YES 
user_id=3142

I don't think so Mark.  I think there needs to be a way to
"click and download" a list of members that can be saved as
a backup.  Then one day in the future add a feature to
"click and upload" a membership list to import those members
into the system.  This way bob's list at providerA could
very easily be moved to providerB without much worry by bob. 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 11:48

Message:
Logged In: YES 
user_id=1123998

Would the current 'roster' page be sufficient if it showed
ALL members to a user logged in with the list admin or site
password?

See request # 782436 for a related request.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1574066&group_id=103

From noreply at sourceforge.net  Wed Oct 11 18:55:55 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 11 Oct 2006 09:55:55 -0700
Subject: [ mailman-Bugs-1573393 ] Missing handling for unexpected content of
	'varhelp'
Message-ID: <E1GXhN5-00031J-3f@sc8-sf-web1.sourceforge.net>

Bugs item #1573393, was opened at 2006-10-08 16:37
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1573393&group_id=103

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/CGI
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Moritz Naumann (mnaumann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing handling for unexpected content of 'varhelp'

Initial Comment:
Invoking
  /mailman/admin/mailman/?VARHELP=/
after having logged in triggers an error.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-11 09:55

Message:
Logged In: YES 
user_id=1123998

Fixed in Subversion for Mailman 2.1 and 2.2. Thanks for the
report.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1573393&group_id=103

From noreply at sourceforge.net  Thu Oct 12 18:47:10 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 12 Oct 2006 09:47:10 -0700
Subject: [ mailman-Bugs-1576038 ] unexistent sender adress:
	mailman-bounces@virtualdomain.tld
Message-ID: <E1GY3iA-0002Zd-Id@sc8-sf-web3.sourceforge.net>

Bugs item #1576038, was opened at 2006-10-12 16:47
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=1576038&group_id=103

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: (un)subscribing
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: brrrt (brrrt)
Assigned to: Nobody/Anonymous (nobody)
Summary: unexistent sender adress: mailman-bounces at virtualdomain.tld

Initial Comment:
subscription notices were sent by
mailman-bounces at virtualdomain.tld instead of
listname-bounces at virtualdomain.tld.

mailman-bounces at virtualdomain.tld is invalid and
nonexistent, which also leads to such mails being
dropped to "nirvana" if some mailserver rejects mail
from invalid senders.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1576038&group_id=103

From noreply at sourceforge.net  Fri Oct 13 03:04:44 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 12 Oct 2006 18:04:44 -0700
Subject: [ mailman-Patches-645297 ] Add PGP support
Message-ID: <E1GYBTg-0005Wd-GY@sc8-sf-web4.sourceforge.net>

Patches item #645297, was opened at 2002-11-28 14:54
Message generated for change (Comment added) made by s0undt3ch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103

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: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Ben Laurie (benl)
Assigned to: Thomas Wouters (twouters)
Summary: Add PGP support

Initial Comment:
Support PGP encrypted lists using GnuPG.

----------------------------------------------------------------------

Comment By: Pedro Algarvio (s0undt3ch)
Date: 2006-10-13 02:04

Message:
Logged In: YES 
user_id=927681

+1 for this patch

----------------------------------------------------------------------

Comment By: Joost van Baal (vanbaal)
Date: 2005-03-22 08:30

Message:
Logged In: YES 
user_id=28781

One might like to take a look at patch #1167696 too.  It
implements
about the same functionality.  As an added bonus, it has some
documentation :)

----------------------------------------------------------------------

Comment By: Arthur Lutz (arthur_lutz)
Date: 2004-12-20 14:24

Message:
Logged In: YES 
user_id=848508

another +1 for this patch, I've been looking for this
functionality too... willing to contribute

----------------------------------------------------------------------

Comment By: Justin Mason (jmason)
Date: 2003-11-10 18:31

Message:
Logged In: YES 
user_id=935

another +1 for this patch, I've been looking for this
functionality too...


----------------------------------------------------------------------

Comment By: Thomas Wouters (twouters)
Date: 2003-03-17 22:17

Message:
Logged In: YES 
user_id=34209

I'll look at incorporating this when I look at the
SecureList patch by NAH6 (SF patch #646989, currently.)


----------------------------------------------------------------------

Comment By: Nicolas Marchildon (elecnix)
Date: 2003-02-06 05:16

Message:
Logged In: YES 
user_id=106549

My vote goes to a PGP whitelist and blacklist feature.
Messages signed with a key present in the whitelist could go
skip moderation, messages in the blacklist would be either
ignored or rejected, and all other messages could go through
moderation. That way, PGP signatures are not required, but
those using them would see their messages delivered quickly.
Mailman would have two keyrings, and would manage them by
specifying --keyring to gpg. PGP keys would be retreived
from a PGP key server. When moderating a message that was
signed with a key missing from the whitelist, there would be
an option named &quot;Add key to whitelist&quot;, and an other one for
the blacklist. Keys could be added to the white/blacklist
through the web interface by specifying at least a key ID,
and mailman would ask gpg to fetch the key from mailman's
default key server.

Initially proposed in French on:
http://www.linux-quebec.org/archives/general/msg03787.html

Nicolas Marchildon

----------------------------------------------------------------------

Comment By: David Shaw (dmshaw)
Date: 2003-01-04 19:59

Message:
Logged In: YES 
user_id=606006

Another vote of support.  I actually submitted an
enhancement request earlier today for exactly this.

----------------------------------------------------------------------

Comment By: captain larry (captainlarry)
Date: 2002-12-23 19:37

Message:
Logged In: YES 
user_id=147905

Adding a vote of support for this patch.  Please add it as
soon as it's appropriate!  I've been waiting a long time for
this functionality and I'd hate to see the patch bitrot. :-)

Adam.

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-12 03:56

Message:
Logged In: YES 
user_id=12800

I have to defer this patch until after MM2.1 since we're
about ready for the first release candidate.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103

From noreply at sourceforge.net  Fri Oct 13 03:05:01 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 12 Oct 2006 18:05:01 -0700
Subject: [ mailman-Patches-943827 ] true virtual hosting patch for 2.1
Message-ID: <E1GYBTx-00025f-ME@sc8-sf-web3.sourceforge.net>

Patches item #943827, was opened at 2004-04-28 17:57
Message generated for change (Comment added) made by s0undt3ch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_id=103

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: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: The Anarcat (anarcat)
Assigned to: Nobody/Anonymous (nobody)
Summary: true virtual hosting patch for 2.1

Initial Comment:
[copy of the mail sent to -developpers@]

We developped a reliable solution for running lists
with the same name
on different domains on the same Mailman installation.

I implemented that on top of the Mailman 2.1.1-5.1
Debian stable
package.  All that is needed is to patch 2 files
(bin/newlist,
Mailman/MailList.py) in the mailman install, and here
is the patch:

http://bugs.koumbit.net/file_download.php?file_id=3&type=bug

There's only one caveat right now:
Mailman/Cgi/create.py might need to
get patched too, but I haven't got around looking at it
yet, and it
"just works", for now.

I don't know what's the current status of virtual
hosting support on
Mailman, but this patch is a simple hack that should
bring joy in the
homes of all Mailman admins around the world. :)

I got my inspiration and part of the code from:

http://mithrandr.moria.org/blog/139.html

All it does is to add the domain to the internal_name()
of a list. The
real_name is kept as is, and the getListAddress() does
the Right Thing.

This makes Mailman generate aliases like:

list-example.com:             
"|/var/lib/mailman/mail/mailman post list-example.com"

Care will have to be taken on the MTA side to map those
list-example.com
to list at example.com. We are using alternc.org to manage
our server, so
we are using LDAP, so everything went pretty smoothly.
:) But I guess it
will require some magic on the Postfix side or something...

Cheers,

A.

PS: for those wanting to see more, you can come to our
Wiki:

http://koumbit.net/wiki/VirtualMailman

You'll probably have a little trouble finding your way
if you don't
read french though. :) Babelfish might help, haven't tried.

----------------------------------------------------------------------

Comment By: Pedro Algarvio (s0undt3ch)
Date: 2006-10-13 02:05

Message:
Logged In: YES 
user_id=927681

+1 for this patch

----------------------------------------------------------------------

Comment By: Paul Hampson (tbble)
Date: 2006-04-22 12:48

Message:
Logged In: YES 
user_id=87909

Crud, wrapping... The changes are all on one line.

----------------------------------------------------------------------

Comment By: Paul Hampson (tbble)
Date: 2006-04-22 12:47

Message:
Logged In: YES 
user_id=87909

minfrin, create it as
listname-domain
or try this patch:
diff -urNad mailman-2.1.5/Mailman/Cgi/create.py
/tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py
--- mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22
20:58:10.324872941 +1000
+++ /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py   
2006-04-22 21:13:31.596133649 +1000
@@ -184,7 +184,7 @@
         oldmask = os.umask(002)
         try:
             try:
-                mlist.Create(listname, owner, pw, langs,
emailhost)
+                mlist.Create("%s@%s" % (listname,hostname),
owner, pw, langs, emailhost)
             finally:
                 os.umask(oldmask)
         except Errors.EmailAddressError, s:

Which will add the '@domain' to the listname before passing
it to mlist.Create, which the patch changes to deal with '@'
the way we want.

----------------------------------------------------------------------

Comment By: Graham Leggett (minfrin)
Date: 2006-03-17 20:39

Message:
Logged In: YES 
user_id=129704

I tried the patch at
http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch and it
applied cleanly to mailman as provided by RHEL4.

I tried to create a list called "list at domain1.com", but this
failed with the error "Error: List name must not include "@"".

Does this patch have any sort of instructions anywhere?


----------------------------------------------------------------------

Comment By: Arnaud Lavrard (arnaudlavrard)
Date: 2005-07-20 14:52

Message:
Logged In: YES 
user_id=1315788

I ported the patch to mailman 2.1.5 :
http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch

----------------------------------------------------------------------

Comment By: The Anarcat (anarcat)
Date: 2005-03-16 20:40

Message:
Logged In: YES 
user_id=246797

I have ported the patch to 2.1.4, no news on 2.1.5 yet. I
have also put the patch in a seperate CVS server. Fetch all
the goods there:

http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-virtual-2.1.1.patch
http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-virtual-2.1.4.patch

I've also updated the 2.1.1 patch to fix the list-id, so I
delete the attachment, fetch the patch straight from our CVS
for the latest fixes.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_id=103

From noreply at sourceforge.net  Fri Oct 13 03:06:23 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 12 Oct 2006 18:06:23 -0700
Subject: [ mailman-Patches-646989 ] NAH6 Secure List patch: GPG plugin
Message-ID: <E1GYBVH-0002HK-27@sc8-sf-web3.sourceforge.net>

Patches item #646989, was opened at 2002-12-02 16:07
Message generated for change (Comment added) made by s0undt3ch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103

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: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 6
Submitted By: Rop Gonggrijp (rop)
Assigned to: Thomas Wouters (twouters)
Summary: NAH6 Secure List patch: GPG plugin

Initial Comment:
&quot;NAH6 Secure List&quot; is a patch for Mailman 2.1b5 that 
adds GPG functionality. It is built around a key-scheme 
that allows an admin to create an encrypted list for 
which even the server operator doesn't have access to 
the messages.

Only the public key for the list is given to the server, so 
it can perform 'emergency encryption' in case someone 
forgets, and all users get the public and private key for 
the list.


We think we've done a decent job of describing the new 
functionality from server-operator, list-admin and list-
member points of view. There's also a technical 
document for those familiar with the Mailman code. 
Please have a look at:

http://www.nah6.com/products/secure-list/

and follow the links from there


We feel more people need this, and we'd really like it to 
be part of the Mailman distribution at some point...


Kind Regards,

Rop Gonggrijp
Joshua Eichen


Please forgive mangling the Mailman logo on the site: if 
y'all don't like it or think it's over the top we'll use 
something else....

----------------------------------------------------------------------

Comment By: Pedro Algarvio (s0undt3ch)
Date: 2006-10-13 02:06

Message:
Logged In: YES 
user_id=927681

+1 for this patch

----------------------------------------------------------------------

Comment By: Pat Carr (pcarr)
Date: 2003-06-21 03:23

Message:
Logged In: YES 
user_id=710070

The problem with the NAH approach is that every time a
member leaves the list, the administrator needs to generate
and distribute a new key, and every remaining member would
have to remove the old list key and replace it with the new
one. This could become a logistical nightmare, and makes it
more difficult to sell this capability to a group that has
people who are email savvy, but not necessarily pgp-savvy.

I prefer the approach in patch #645297, recognizing that the
task there is to maintain strict security of the server and
the secret keys of the lists.


----------------------------------------------------------------------

Comment By: Thomas Wouters (twouters)
Date: 2003-03-10 16:16

Message:
Logged In: YES 
user_id=34209

I'm looking at this patch, but I'm a bit confused. Which is
the newer patch, v1.0 for Mailman 2.1 (uploaded last) or
v1.1 for Mailman 2.1b5 (which is linked to from the NAH6
secure-list page.)

Otherwise, the patch looks okay. There are some whitespace
issues, and the PGP specific options aren't properly
internationalized, but that can all be fixed. The patch
edits Defaults.py, but it should be Defaults.py.in (if you
want to apply to CVS before installation, anyway.) Oh, and a
'global' statement for DETAILS in the global namespace
really isn't necessary... Do you need someone to come over
and give a Python tutorial at NAH6 ? :-)

Assigning to myself so I don't forget it; if someone else
wants it, that's fine by me.


----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-12 04:01

Message:
Logged In: YES 
user_id=12800

The logo's fine (plus the original is free software).

I'm defering this until after MM2.1 because we're about
ready for the first release candidate.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103

From noreply at sourceforge.net  Fri Oct 13 07:37:40 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 12 Oct 2006 22:37:40 -0700
Subject: [ mailman-Patches-1167696 ] add support for PGP and S/MIME encryption
	and signing
Message-ID: <E1GYFjo-0004T2-Ro@sc8-sf-web2.sourceforge.net>

Patches item #1167696, was opened at 2005-03-21 16:28
Message generated for change (Settings changed) made by vanbaal
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1167696&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Joost van Baal (vanbaal)
Assigned to: Nobody/Anonymous (nobody)
>Summary: add support for PGP and S/MIME encryption and signing

Initial Comment:

This patch is based upon a patch by Stefan Schlott (
http://medien.informatik.uni-ulm.de/~stefan/gpg-mailman.html )

It extends Mailman to:

- A post will be distributed only if the PGP signature on the post is from
  one of the list members.
- For sending encrypted email, a list member encrypts to the public key of
  the list.  The post will be decrypted and re-encrypted to the public keys
  of all list members.
(Later, the patch will handle RFC 2633 (S/MIME) messages too, next to RFC 2440
(OpenPGP)).

In order to achieve this, each list has a public and private key, as well
as a key passphrase.  Furthermore, new list settings are defined:

 gpg_postings_allowed: Is it allowed to send to this list postings which are
  encrypted with the GPG list key?
 gpg_msg_distribution: Are subscribers allowed (or even forced) to upload
  their GPG public key in order to receive all messages encrypted?
 gpg_post_sign: Should posts be GPG signed with an acknowledged subscriber key
  before being distributed?
 gpg_msg_sign: Should the server sign encrypted messages?

Finally, each subscriber can upload her PGP public key using the webinterface.

Latest version of the patch is available from
http://www.non-gnu.uvt.nl/pub/mailman/ .



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1167696&group_id=103

From noreply at sourceforge.net  Fri Oct 13 07:40:29 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 12 Oct 2006 22:40:29 -0700
Subject: [ mailman-Patches-1167696 ] add support for PGP and S/MIME encryption
	and signing
Message-ID: <E1GYFmX-0004l5-3q@sc8-sf-web2.sourceforge.net>

Patches item #1167696, was opened at 2005-03-21 16:28
Message generated for change (Comment added) made by vanbaal
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1167696&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Joost van Baal (vanbaal)
Assigned to: Nobody/Anonymous (nobody)
Summary: add support for PGP and S/MIME encryption and signing

Initial Comment:

This patch is based upon a patch by Stefan Schlott (
http://medien.informatik.uni-ulm.de/~stefan/gpg-mailman.html )

It extends Mailman to:

- A post will be distributed only if the PGP signature on the post is from
  one of the list members.
- For sending encrypted email, a list member encrypts to the public key of
  the list.  The post will be decrypted and re-encrypted to the public keys
  of all list members.
(Later, the patch will handle RFC 2633 (S/MIME) messages too, next to RFC 2440
(OpenPGP)).

In order to achieve this, each list has a public and private key, as well
as a key passphrase.  Furthermore, new list settings are defined:

 gpg_postings_allowed: Is it allowed to send to this list postings which are
  encrypted with the GPG list key?
 gpg_msg_distribution: Are subscribers allowed (or even forced) to upload
  their GPG public key in order to receive all messages encrypted?
 gpg_post_sign: Should posts be GPG signed with an acknowledged subscriber key
  before being distributed?
 gpg_msg_sign: Should the server sign encrypted messages?

Finally, each subscriber can upload her PGP public key using the webinterface.

Latest version of the patch is available from
http://www.non-gnu.uvt.nl/pub/mailman/ .



----------------------------------------------------------------------

>Comment By: Joost van Baal (vanbaal)
Date: 2006-10-13 05:40

Message:
Logged In: YES 
user_id=28781

The patch fully supports S/MIME too.

Between 2006-01 and 2006-10, no work has been done on this
patch.  It applies to Mailman 2.1.7 only.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1167696&group_id=103

From noreply at sourceforge.net  Fri Oct 13 19:05:45 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 13 Oct 2006 10:05:45 -0700
Subject: [ mailman-Bugs-1495122 ] Mailman strips format=flowed from
	Content-Type header
Message-ID: <E1GYQTh-00029Z-AU@sc8-sf-web4.sourceforge.net>

Bugs item #1495122, was opened at 2006-05-25 15:24
Message generated for change (Comment added) made by ptwithy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_id=103

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
Submitted By: Bart Jacobs (radiantskies)
Assigned to: Nobody/Anonymous (nobody)
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: P T Withington (ptwithy)
Date: 2006-10-13 13: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 12: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-13 02: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_id=103

From noreply at sourceforge.net  Fri Oct 13 20:23:35 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 13 Oct 2006 11:23:35 -0700
Subject: [ mailman-Bugs-1495122 ] Mailman strips format=flowed from
	Content-Type header
Message-ID: <E1GYRh1-0000ot-6V@sc8-sf-web5.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_id=103

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
Submitted By: Bart Jacobs (radiantskies)
Assigned to: Nobody/Anonymous (nobody)
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: 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_id=103

From noreply at sourceforge.net  Fri Oct 13 21:15:08 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 13 Oct 2006 12:15:08 -0700
Subject: [ mailman-Bugs-1576775 ] check_perms.py check_data check if it's a dir
Message-ID: <E1GYSUu-00081E-IR@sc8-sf-web3.sourceforge.net>

Bugs item #1576775, was opened at 2006-10-13 20:15
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=1576775&group_id=103

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: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Pedro Algarvio (s0undt3ch)
Assigned to: Nobody/Anonymous (nobody)
Summary: check_perms.py check_data check if it's a dir

Initial Comment:
on check_perms.py function check_data(), if you're
trying to join files to dirs found on lists, you should
check if it's really a dir or a file.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1576775&group_id=103

From noreply at sourceforge.net  Fri Oct 13 22:37:18 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 13 Oct 2006 13:37:18 -0700
Subject: [ mailman-Bugs-1495122 ] Mailman strips format=flowed from
	Content-Type header
Message-ID: <E1GYTmQ-0002ed-Fx@sc8-sf-web5.sourceforge.net>

Bugs item #1495122, was opened at 2006-05-25 15:24
Message generated for change (Comment added) made by ptwithy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_id=103

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
Submitted By: Bart Jacobs (radiantskies)
Assigned to: Nobody/Anonymous (nobody)
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: P T Withington (ptwithy)
Date: 2006-10-13 16: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 14: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 13: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 12: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-13 02: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_id=103

From noreply at sourceforge.net  Sat Oct 14 22:25:54 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 14 Oct 2006 13:25:54 -0700
Subject: [ mailman-Feature Requests-1577361 ] Need simple mailman python module
Message-ID: <E1GYq4w-0004Vx-B4@sc8-sf-web3.sourceforge.net>

Feature Requests item #1577361, was opened at 2006-10-14 15:25
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=1577361&group_id=103

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
Submitted By: Lindsay Haisley (fmouse)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need simple mailman python module

Initial Comment:
When I'm doing utility programming in python for which
I need direct access to the objects in a mailman list,
it would be nice if I could include a module which
would give me this access.  withlist come close, but
still requires that a callback module be defined with
-r, or else an interactive shell is started and
anything defined before the module include goes out of
scope.

Here's an example of how it might work.  Supposing
withlist had an option, say -m, that bypassed the
interactive shell as -r does, but didn't requre a
callback module.  I create a symbolic link,
withlist.py, to /usr/local/mailman/bin/withlist and put
this where it's accessable to my script.  I could do
the following:

import sys
sys.path.append("/usr/local/mailman/bin")
sys.argv.extend(["-m", "listname"])
import withlist
..... etc.
..... all list data is now available.

I can do this now by creating a dummy callback module
and  using "-r", but it shouldn't be necessary to go
around the block to get across the street here.  It's
also possible to use os.popen to pull in specific
pieces of information, but in a python context it
should be possible to simply include a python module
and have full access to the objects specific to a list
without having to fork off a process.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577361&group_id=103

From noreply at sourceforge.net  Sat Oct 14 22:46:56 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 14 Oct 2006 13:46:56 -0700
Subject: [ mailman-Feature Requests-1577374 ] PHP in mailman templates
Message-ID: <E1GYqPI-0004JQ-TS@sc8-sf-web1.sourceforge.net>

Feature Requests item #1577374, was opened at 2006-10-14 15:46
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=1577374&group_id=103

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
Submitted By: Lindsay Haisley (fmouse)
Assigned to: Nobody/Anonymous (nobody)
Summary: PHP in mailman templates

Initial Comment:
Here's a way to force html produced from mailman
templates to execute PHP code when they're served from
a mailman CGI.  This idea needs a lot of development,
and although I'm using it on a production system, it's
mainly a proof of concept.

I don't claim much credit for this.  I stole the idea
quite blatantly from Fredrik Lundh's "Python Standard
Library" (pub. by O'Reilly).

~mailman/Mailman/Cgi/private.py is patched with two
lines of code:

--- private.py.orig     2006-09-18 14:00:19.000000000 -0500
+++ private.py  2006-10-08 18:36:35.000000000 -0500
@@ -29,6 +29,7 @@
 from Mailman import i18n
 from Mailman.htmlformat import *
 from Mailman.Logging.Syslog import syslog
+from php_redirect import Redirect
 
 # Set up i18n.  Until we know which list is being
requested, we use the
 # server's default.
@@ -123,6 +124,8 @@
     realname = mlist.real_name
     message = ''
 
+    sys.stdout = Redirect(sys.stdout)
+
     if not mlist.WebAuthenticate((mm_cfg.AuthUser,
                                  
mm_cfg.AuthListModerator,
                                   mm_cfg.AuthListAdmin,


The Redirect class, in php_redirect.py, is as follows:

class Redirect:
    """Redirect stdout to PHP command line interpreter.
    Usage:  sys.stdout = Redirect(sys.stdout)"""

    def __init__(self, stdout):
        self.stdout = stdout
        import os
        self.os = os

    def write(self, s):
        if self.os.access("/usr/bin/php", self.os.X_OK):
            wpipe = self.os.popen("/usr/bin/php", "w")
            wpipe.write(s)
        else:
            self.stdout.write(s)


Any output after the sys.stdout = Redirect(sys.stdout)
line in private.py will be passed through the PHP
command line interpreter if it's present.

This solution doesn't cover the situation where an
archive index.html is public and is accessed directly
by the web server rather than by a mailman CGI.  For
this, the quick and dirty hack is to tell apache to
'AddType application/x-httpd-php .html' for the mailman
archive directory, but mailman might look at the
filename on a template and create the working file with
the same extension.  e.g. if, say,
~mailman/templates/en/archtocnombox.html existed, then
it would be used to create
~mailman/archives/private/listname/index.html.  On the
other hand, if the same template were called
archtocnombox.php, then it would be used to create
index.php in the proper archive directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577374&group_id=103

From noreply at sourceforge.net  Sat Oct 14 22:53:29 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 14 Oct 2006 13:53:29 -0700
Subject: [ mailman-Feature Requests-1577361 ] Need simple mailman python module
Message-ID: <E1GYqVd-0004zk-JJ@sc8-sf-web1.sourceforge.net>

Feature Requests item #1577361, was opened at 2006-10-14 13:25
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577361&group_id=103

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
Submitted By: Lindsay Haisley (fmouse)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need simple mailman python module

Initial Comment:
When I'm doing utility programming in python for which
I need direct access to the objects in a mailman list,
it would be nice if I could include a module which
would give me this access.  withlist come close, but
still requires that a callback module be defined with
-r, or else an interactive shell is started and
anything defined before the module include goes out of
scope.

Here's an example of how it might work.  Supposing
withlist had an option, say -m, that bypassed the
interactive shell as -r does, but didn't requre a
callback module.  I create a symbolic link,
withlist.py, to /usr/local/mailman/bin/withlist and put
this where it's accessable to my script.  I could do
the following:

import sys
sys.path.append("/usr/local/mailman/bin")
sys.argv.extend(["-m", "listname"])
import withlist
..... etc.
..... all list data is now available.

I can do this now by creating a dummy callback module
and  using "-r", but it shouldn't be necessary to go
around the block to get across the street here.  It's
also possible to use os.popen to pull in specific
pieces of information, but in a python context it
should be possible to simply include a python module
and have full access to the objects specific to a list
without having to fork off a process.


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-14 13:53

Message:
Logged In: YES 
user_id=1123998

This already exists. Think of /usr/local/bin/Mailman as a
library of Mailman modules.

e.g.

import sys
sys.path.append('/usr/local/mailman')
from Mailman import MailList
mlist = MailList.MailList('listname', lock=False)



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577361&group_id=103

From noreply at sourceforge.net  Sat Oct 14 22:53:46 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 14 Oct 2006 13:53:46 -0700
Subject: [ mailman-Feature Requests-1577374 ] PHP in mailman templates
Message-ID: <E1GYqVu-00050B-Bg@sc8-sf-web1.sourceforge.net>

Feature Requests item #1577374, was opened at 2006-10-14 15:46
Message generated for change (Comment added) made by fmouse
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577374&group_id=103

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
Submitted By: Lindsay Haisley (fmouse)
Assigned to: Nobody/Anonymous (nobody)
Summary: PHP in mailman templates

Initial Comment:
Here's a way to force html produced from mailman
templates to execute PHP code when they're served from
a mailman CGI.  This idea needs a lot of development,
and although I'm using it on a production system, it's
mainly a proof of concept.

I don't claim much credit for this.  I stole the idea
quite blatantly from Fredrik Lundh's "Python Standard
Library" (pub. by O'Reilly).

~mailman/Mailman/Cgi/private.py is patched with two
lines of code:

--- private.py.orig     2006-09-18 14:00:19.000000000 -0500
+++ private.py  2006-10-08 18:36:35.000000000 -0500
@@ -29,6 +29,7 @@
 from Mailman import i18n
 from Mailman.htmlformat import *
 from Mailman.Logging.Syslog import syslog
+from php_redirect import Redirect
 
 # Set up i18n.  Until we know which list is being
requested, we use the
 # server's default.
@@ -123,6 +124,8 @@
     realname = mlist.real_name
     message = ''
 
+    sys.stdout = Redirect(sys.stdout)
+
     if not mlist.WebAuthenticate((mm_cfg.AuthUser,
                                  
mm_cfg.AuthListModerator,
                                   mm_cfg.AuthListAdmin,


The Redirect class, in php_redirect.py, is as follows:

class Redirect:
    """Redirect stdout to PHP command line interpreter.
    Usage:  sys.stdout = Redirect(sys.stdout)"""

    def __init__(self, stdout):
        self.stdout = stdout
        import os
        self.os = os

    def write(self, s):
        if self.os.access("/usr/bin/php", self.os.X_OK):
            wpipe = self.os.popen("/usr/bin/php", "w")
            wpipe.write(s)
        else:
            self.stdout.write(s)


Any output after the sys.stdout = Redirect(sys.stdout)
line in private.py will be passed through the PHP
command line interpreter if it's present.

This solution doesn't cover the situation where an
archive index.html is public and is accessed directly
by the web server rather than by a mailman CGI.  For
this, the quick and dirty hack is to tell apache to
'AddType application/x-httpd-php .html' for the mailman
archive directory, but mailman might look at the
filename on a template and create the working file with
the same extension.  e.g. if, say,
~mailman/templates/en/archtocnombox.html existed, then
it would be used to create
~mailman/archives/private/listname/index.html.  On the
other hand, if the same template were called
archtocnombox.php, then it would be used to create
index.php in the proper archive directory.


----------------------------------------------------------------------

>Comment By: Lindsay Haisley (fmouse)
Date: 2006-10-14 15:53

Message:
Logged In: YES 
user_id=694133

Since the tracker munged my code a bit, I'm attaching a
couple of files.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577374&group_id=103

From noreply at sourceforge.net  Sun Oct 15 00:47:30 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 14 Oct 2006 15:47:30 -0700
Subject: [ mailman-Feature Requests-1577361 ] Need simple mailman python module
Message-ID: <E1GYsHy-0006LB-0F@sc8-sf-web5.sourceforge.net>

Feature Requests item #1577361, was opened at 2006-10-14 15:25
Message generated for change (Comment added) made by fmouse
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577361&group_id=103

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: Deleted
Resolution: None
Priority: 5
Submitted By: Lindsay Haisley (fmouse)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need simple mailman python module

Initial Comment:
When I'm doing utility programming in python for which
I need direct access to the objects in a mailman list,
it would be nice if I could include a module which
would give me this access.  withlist come close, but
still requires that a callback module be defined with
-r, or else an interactive shell is started and
anything defined before the module include goes out of
scope.

Here's an example of how it might work.  Supposing
withlist had an option, say -m, that bypassed the
interactive shell as -r does, but didn't requre a
callback module.  I create a symbolic link,
withlist.py, to /usr/local/mailman/bin/withlist and put
this where it's accessable to my script.  I could do
the following:

import sys
sys.path.append("/usr/local/mailman/bin")
sys.argv.extend(["-m", "listname"])
import withlist
..... etc.
..... all list data is now available.

I can do this now by creating a dummy callback module
and  using "-r", but it shouldn't be necessary to go
around the block to get across the street here.  It's
also possible to use os.popen to pull in specific
pieces of information, but in a python context it
should be possible to simply include a python module
and have full access to the objects specific to a list
without having to fork off a process.


----------------------------------------------------------------------

>Comment By: Lindsay Haisley (fmouse)
Date: 2006-10-14 17:47

Message:
Logged In: YES 
user_id=694133

Very well!  You're absolutely right.  Sorry for the noise. 
I'm deleting this feature request.


----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-14 15:53

Message:
Logged In: YES 
user_id=1123998

This already exists. Think of /usr/local/bin/Mailman as a
library of Mailman modules.

e.g.

import sys
sys.path.append('/usr/local/mailman')
from Mailman import MailList
mlist = MailList.MailList('listname', lock=False)



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1577361&group_id=103

From noreply at sourceforge.net  Tue Oct 17 00:03:19 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 16 Oct 2006 15:03:19 -0700
Subject: [ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
Message-ID: <E1GZaYJ-0002aD-5o@sc8-sf-web4.sourceforge.net>

Bugs item #1578539, was opened at 2006-10-17 00:03
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=1578539&group_id=103

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
Submitted By: Duelago (stekardavid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with Microsoft Entourage

Initial Comment:
When posting to a Mailman list with Microsoft Entourage
(all versions) the subject line gets crippled if you
use characters like ???.

Sm?g?sbord ends up liks Sm ? rg ? rdsbord.
I don't have this problem if I post to other list
servers like Majordomo or ezmlm. I guess we can blame
Microsoft, but why don't I have a problem with other
list solutions?




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

From noreply at sourceforge.net  Tue Oct 17 01:30:44 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 16 Oct 2006 16:30:44 -0700
Subject: [ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
Message-ID: <E1GZbuu-0002PV-CP@sc8-sf-web3.sourceforge.net>

Bugs item #1578539, was opened at 2006-10-16 15:03
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

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
Submitted By: Duelago (stekardavid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with Microsoft Entourage

Initial Comment:
When posting to a Mailman list with Microsoft Entourage
(all versions) the subject line gets crippled if you
use characters like ???.

Sm?g?sbord ends up liks Sm ? rg ? rdsbord.
I don't have this problem if I post to other list
servers like Majordomo or ezmlm. I guess we can blame
Microsoft, but why don't I have a problem with other
list solutions?




----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 16:30

Message:
Logged In: YES 
user_id=1123998

I am unable to duplicate the problem on Mailman 2.1.5.

Can you post the raw Subject: header from both the message
as sent to the list and as received from the list. I'm
looking for things that look like

Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?=

or

Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?=

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

From noreply at sourceforge.net  Tue Oct 17 01:38:14 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 16 Oct 2006 16:38:14 -0700
Subject: [ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
Message-ID: <E1GZc2A-0003Ak-7C@sc8-sf-web3.sourceforge.net>

Bugs item #1578539, was opened at 2006-10-16 15:03
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

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
Submitted By: Duelago (stekardavid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with Microsoft Entourage

Initial Comment:
When posting to a Mailman list with Microsoft Entourage
(all versions) the subject line gets crippled if you
use characters like ???.

Sm?g?sbord ends up liks Sm ? rg ? rdsbord.
I don't have this problem if I post to other list
servers like Majordomo or ezmlm. I guess we can blame
Microsoft, but why don't I have a problem with other
list solutions?




----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 16:38

Message:
Logged In: YES 
user_id=1123998

I should say, I am unable to duplicate with Mailman 2.1.5
and Thunderbird. I don't have Entourage to test with.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 16:30

Message:
Logged In: YES 
user_id=1123998

I am unable to duplicate the problem on Mailman 2.1.5.

Can you post the raw Subject: header from both the message
as sent to the list and as received from the list. I'm
looking for things that look like

Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?=

or

Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?=

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

From noreply at sourceforge.net  Tue Oct 17 02:45:19 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 16 Oct 2006 17:45:19 -0700
Subject: [ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
Message-ID: <E1GZd55-0006wI-LL@sc8-sf-web6.sourceforge.net>

Bugs item #1578539, was opened at 2006-10-16 22:03
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

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
Submitted By: Duelago (stekardavid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with Microsoft Entourage

Initial Comment:
When posting to a Mailman list with Microsoft Entourage
(all versions) the subject line gets crippled if you
use characters like ???.

Sm?g?sbord ends up liks Sm ? rg ? rdsbord.
I don't have this problem if I post to other list
servers like Majordomo or ezmlm. I guess we can blame
Microsoft, but why don't I have a problem with other
list solutions?




----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-10-17 00:45

Message:
Logged In: YES 
user_id=67709

I tested with my Entourage which I didn't use so far.
It gave:
  Sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord
and ends up by processed by mailman email.Header module:
  Sm =?iso-8859-1?q?=F6?= g =?iso-8859-1?q?=E5?= sbord

It looks like they break a statement of RFC-2047:
    Ordinary ASCII text and 'encoded-word's may appear
together in the
    same header field.  However, an 'encoded-word' that
appears in a
    header field defined as '*text' MUST be separated from
any adjacent
    'encoded-word' or 'text' by 'linear-white-space'.



----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 23:38

Message:
Logged In: YES 
user_id=1123998

I should say, I am unable to duplicate with Mailman 2.1.5
and Thunderbird. I don't have Entourage to test with.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 23:30

Message:
Logged In: YES 
user_id=1123998

I am unable to duplicate the problem on Mailman 2.1.5.

Can you post the raw Subject: header from both the message
as sent to the list and as received from the list. I'm
looking for things that look like

Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?=

or

Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?=

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

From noreply at sourceforge.net  Tue Oct 17 10:24:34 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 17 Oct 2006 01:24:34 -0700
Subject: [ mailman-Patches-1578740 ] fblast needs a shebang line
Message-ID: <E1GZkFW-0000wj-S3@sc8-sf-web6.sourceforge.net>

Patches item #1578740, was opened at 2006-10-17 10:24
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=1578740&group_id=103

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: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: fblast needs a shebang line

Initial Comment:
Hi!

tests/fblast.py is installed as executable by the
Makefile in that dir. It does however not have a
shebang line at the start, thus making it not directly
executable.

It should either not be set +x, or add the line. I've
done the latter. Patch is attached, please consider.


Thanks!
Thijs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578740&group_id=103

From noreply at sourceforge.net  Tue Oct 17 10:31:56 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 17 Oct 2006 01:31:56 -0700
Subject: [ mailman-Patches-1578740 ] fblast needs a shebang line
Message-ID: <E1GZkMe-0001dl-JN@sc8-sf-web6.sourceforge.net>

Patches item #1578740, was opened at 2006-10-17 10:24
Message generated for change (Settings changed) made by kink
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578740&group_id=103

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: command line scripts
>Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: fblast needs a shebang line

Initial Comment:
Hi!

tests/fblast.py is installed as executable by the
Makefile in that dir. It does however not have a
shebang line at the start, thus making it not directly
executable.

It should either not be set +x, or add the line. I've
done the latter. Patch is attached, please consider.


Thanks!
Thijs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578740&group_id=103

From noreply at sourceforge.net  Tue Oct 17 10:45:49 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 17 Oct 2006 01:45:49 -0700
Subject: [ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
Message-ID: <E1GZka5-0003QQ-HF@sc8-sf-web4.sourceforge.net>

Patches item #1578756, was opened at 2006-10-17 10:45
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=1578756&group_id=103

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.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Handle unexpected HTTP method gracefully

Initial Comment:
Hi!

When Mailman is confronted with an unexpected HTTP
method type (e.g. PROPFIND instead of GET/HEAD/POST),
it crashes. The attached patch fixes that more
gracefully by throwing the appropriate HTTP error.

Thanks for considering.
Thijs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

From noreply at sourceforge.net  Tue Oct 17 10:59:38 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 17 Oct 2006 01:59:38 -0700
Subject: [ mailman-Patches-1578766 ] Russian newlist template has wrong
	variable
Message-ID: <E1GZknS-0004OF-OU@sc8-sf-web6.sourceforge.net>

Patches item #1578766, was opened at 2006-10-17 10:59
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=1578766&group_id=103

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.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Russian newlist template has wrong variable

Initial Comment:
Hi,

The Russian newlist template ends with 
"mailman-owner@%(hostname)s", while in more recent
templates this is "%(siteowner)s". The attached patch
corrects that, you don't need to speak Russian to
understand it :)


Thijs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578766&group_id=103

From noreply at sourceforge.net  Thu Oct 19 10:18:42 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 19 Oct 2006 01:18:42 -0700
Subject: [ mailman-Patches-1580310 ] In-Reply-To: in mailto: links incorrect.
Message-ID: <E1GaT6w-00021w-M7@sc8-sf-web3.sourceforge.net>

Patches item #1580310, was opened at 2006-10-19 09:18
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=1580310&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: David Woodhouse (dwmw2)
Assigned to: Nobody/Anonymous (nobody)
Summary: In-Reply-To: in mailto: links incorrect.

Initial Comment:
Mails in the archive have a mailto: link with which you
can reply to the email you're viewing. That mailto: URL
contains an &In-Reply-To= part, to set the In-Reply-To:
header in the generated mail and thus enable correct
threading of replies.

Unfortunately, we give the wrong ID. We give the
In-Reply-To: header of the message to which the user
would be replying, but we should be using Message-Id:
of the message in question, instead.

See also 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123768

(although the example given there no longer shows the
problem because I've fixed the bug and recreated the
archives since then)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1580310&group_id=103

From noreply at sourceforge.net  Fri Oct 20 00:18:17 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 19 Oct 2006 15:18:17 -0700
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
Message-ID: <E1GagDR-0002qC-M9@sc8-sf-web6.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 18:19
Message generated for change (Comment added) made by mmokrejs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2006-10-20 00:18

Message:
Logged In: YES 
user_id=696559

ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
patching file Mailman/Cgi/private.py
patching file Mailman/Defaults.py.in
ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1
patching file INSTALL.mhonarc-mm
patching file Mailman/Archiver/Archiver.py
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Archiver/pipermail.py
patching file Mailman/Cgi/create.py
patching file Mailman/Defaults.py.in
Hunk #2 succeeded at 1390 (offset 73 lines).
patching file Mailman/Errors.py
patching file Mailman/Gui/Archive.py
patching file Mailman/Mailbox.py
patching file Mailman/Version.py
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file
Mailman/Version.py.rej
patching file bin/arch
patching file bin/newlist
patching file templates/Makefile.in
patching file templates/en/author.mrc
patching file templates/en/mhonarc.mrc
patching file templates/en/subject.mrc
ribosome mailman-2.1.9 # less Mailman/Version.py.rej
***************
*** 39,45 ****
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
- DATA_FILE_VERSION = 96.1
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
--- 39,50 ----
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
+ # DATA_FILE_VERSION = 96.1
+ # 96.2 to take account of extra which_archiver and 
+ # archiver_when_wiped list attributes
+ # must be applied AFTER the modinc-2.1.7-0.1.patch
+ DATA_FILE_VERSION = 96.2
+ 
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
ribosome mailman-2.1.9 # 

So, which patch do I have to apply before applying the 2.1.9
-0.1 version of this? It is a pitty this is not yet in the
official releases. I am using mailman-20041012.tar.bz2 with
these for some years and see only 2 or three types of error
in the logs. But damn mailman ignores some subscription
confirmation messages and breaks on some non-us-ascii
encoded messages so I should upgrade to see if it helps. :((

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 13:08

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-20 01:01

Message:
Logged In: YES 
user_id=75166

Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-03-02 22:17

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of 
Mailman/Cgi/create.py which fails to get the initial setup of lists created 
through the web quite right. This leads to spurious errors being logged on 
message archiving until bin/arch --wipe is run for such a list affected. Lists 
created with bin/newlist did not have this problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-09-23 23:45

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of 
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the 
problem was not present in patches for previous MM versions. In some 
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a 
list my be generated using the wrong archiver. Examining index pages in 
the archives of a list will show if this problem has affected that list. 
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe 
should resolve the problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 19:43

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

----------------------------------------------------------------------

Comment By: dfragos (dfragos)
Date: 2005-07-21 17:24

Message:
Logged In: YES 
user_id=1310569

what about MM 2.1.6?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 12:04

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-20 01:53

Message:
Logged In: YES 
user_id=696559

I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 16:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 16:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 07:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 19:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Fri Oct 20 00:39:25 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 19 Oct 2006 15:39:25 -0700
Subject: [ mailman-Patches-1176284 ] CommandRunner-UnicodeDecodeError
Message-ID: <E1GagXt-0003KN-VG@sc8-sf-web5.sourceforge.net>

Patches item #1176284, was opened at 2005-04-04 13:01
Message generated for change (Comment added) made by mmokrejs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1176284&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Myroslav Opyr (interra)
Assigned to: Nobody/Anonymous (nobody)
Summary: CommandRunner-UnicodeDecodeError

Initial Comment:
Another two messages got stuck in my shunt folder:
Apr 04 13:48:45 2005 (31466) Traceback (most recent
call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 111, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py",
line 167, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Queue/CommandRunner.py",
line 224, in _dispose
    res = Results(mlist, msg, msgdata)
  File
"/usr/local/mailman/Mailman/Queue/CommandRunner.py",
line 78, in __init__
    subj = make_header(decode_header(subj)).__unicode__()
  File
"/usr/local/lib/python2.3/site-packages/email/Header.py",
line 124, in make_header
    h.append(s, charset)
  File
"/usr/local/lib/python2.3/site-packages/email/Header.py",
line 252, in append
    ustr = unicode(s, incodec, errors)
UnicodeDecodeError: 'ascii' codec can't decode byte
0xd5 in position 0: ordinal not in range(128)

Attached patch pushed them.

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2006-10-20 00:39

Message:
Logged In: YES 
user_id=696559

This does not apply to 2.1.9. Is this still necessary? It
doesn't seem to me.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1176284&group_id=103

From noreply at sourceforge.net  Fri Oct 20 09:50:15 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 20 Oct 2006 00:50:15 -0700
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
Message-ID: <E1Gap8x-0003n9-RN@sc8-sf-web4.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-20 07:50

Message:
Logged In: YES 
user_id=75166

The file INSTALL.mhonarc-mm installed by this patch contains the following 
words. The same information is also on the openinfo web page whose URL is 
above.

Necessary Precursors
--------------------

The following patch must be applied to Mailman before applying this patch: 

1.	Mailman Patch #760567: both this patch and #760567 update the 
version number ...


----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2006-10-19 22:18

Message:
Logged In: YES 
user_id=696559

ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
patching file Mailman/Cgi/private.py
patching file Mailman/Defaults.py.in
ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1
patching file INSTALL.mhonarc-mm
patching file Mailman/Archiver/Archiver.py
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Archiver/pipermail.py
patching file Mailman/Cgi/create.py
patching file Mailman/Defaults.py.in
Hunk #2 succeeded at 1390 (offset 73 lines).
patching file Mailman/Errors.py
patching file Mailman/Gui/Archive.py
patching file Mailman/Mailbox.py
patching file Mailman/Version.py
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file
Mailman/Version.py.rej
patching file bin/arch
patching file bin/newlist
patching file templates/Makefile.in
patching file templates/en/author.mrc
patching file templates/en/mhonarc.mrc
patching file templates/en/subject.mrc
ribosome mailman-2.1.9 # less Mailman/Version.py.rej
***************
*** 39,45 ****
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
- DATA_FILE_VERSION = 96.1
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
--- 39,50 ----
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
+ # DATA_FILE_VERSION = 96.1
+ # 96.2 to take account of extra which_archiver and 
+ # archiver_when_wiped list attributes
+ # must be applied AFTER the modinc-2.1.7-0.1.patch
+ DATA_FILE_VERSION = 96.2
+ 
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
ribosome mailman-2.1.9 # 

So, which patch do I have to apply before applying the 2.1.9
-0.1 version of this? It is a pitty this is not yet in the
official releases. I am using mailman-20041012.tar.bz2 with
these for some years and see only 2 or three types of error
in the logs. But damn mailman ignores some subscription
confirmation messages and breaks on some non-us-ascii
encoded messages so I should upgrade to see if it helps. :((

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:08

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 23:01

Message:
Logged In: YES 
user_id=75166

Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-03-02 21:17

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of 
Mailman/Cgi/create.py which fails to get the initial setup of lists created 
through the web quite right. This leads to spurious errors being logged on 
message archiving until bin/arch --wipe is run for such a list affected. Lists 
created with bin/newlist did not have this problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-09-23 21:45

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of 
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the 
problem was not present in patches for previous MM versions. In some 
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a 
list my be generated using the wrong archiver. Examining index pages in 
the archives of a list will show if this problem has affected that list. 
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe 
should resolve the problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:43

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

----------------------------------------------------------------------

Comment By: dfragos (dfragos)
Date: 2005-07-21 15:24

Message:
Logged In: YES 
user_id=1310569

what about MM 2.1.6?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 10:04

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-19 23:53

Message:
Logged In: YES 
user_id=696559

I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 05:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Fri Oct 20 10:03:51 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 20 Oct 2006 01:03:51 -0700
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
Message-ID: <E1GapM7-0008Gw-6C@sc8-sf-web5.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 16:19
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

>Comment By: Richard Barrett (ppsys)
Date: 2006-10-20 08:03

Message:
Logged In: YES 
user_id=75166

Apologies, but the URL cited above had to be changed when I changed hosting 
service provider as they have co-opted the /mailman/ URI root. See instead:

http://www.openinfo.co.uk/mm/patches/mhonarc/index.html

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-20 07:50

Message:
Logged In: YES 
user_id=75166

The file INSTALL.mhonarc-mm installed by this patch contains the following 
words. The same information is also on the openinfo web page whose URL is 
above.

Necessary Precursors
--------------------

The following patch must be applied to Mailman before applying this patch: 

1.	Mailman Patch #760567: both this patch and #760567 update the 
version number ...


----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2006-10-19 22:18

Message:
Logged In: YES 
user_id=696559

ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
patching file Mailman/Cgi/private.py
patching file Mailman/Defaults.py.in
ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1
patching file INSTALL.mhonarc-mm
patching file Mailman/Archiver/Archiver.py
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Archiver/pipermail.py
patching file Mailman/Cgi/create.py
patching file Mailman/Defaults.py.in
Hunk #2 succeeded at 1390 (offset 73 lines).
patching file Mailman/Errors.py
patching file Mailman/Gui/Archive.py
patching file Mailman/Mailbox.py
patching file Mailman/Version.py
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file
Mailman/Version.py.rej
patching file bin/arch
patching file bin/newlist
patching file templates/Makefile.in
patching file templates/en/author.mrc
patching file templates/en/mhonarc.mrc
patching file templates/en/subject.mrc
ribosome mailman-2.1.9 # less Mailman/Version.py.rej
***************
*** 39,45 ****
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
- DATA_FILE_VERSION = 96.1
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
--- 39,50 ----
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
+ # DATA_FILE_VERSION = 96.1
+ # 96.2 to take account of extra which_archiver and 
+ # archiver_when_wiped list attributes
+ # must be applied AFTER the modinc-2.1.7-0.1.patch
+ DATA_FILE_VERSION = 96.2
+ 
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
ribosome mailman-2.1.9 # 

So, which patch do I have to apply before applying the 2.1.9
-0.1 version of this? It is a pitty this is not yet in the
official releases. I am using mailman-20041012.tar.bz2 with
these for some years and see only 2 or three types of error
in the logs. But damn mailman ignores some subscription
confirmation messages and breaks on some non-us-ascii
encoded messages so I should upgrade to see if it helps. :((

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 11:08

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-19 23:01

Message:
Logged In: YES 
user_id=75166

Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-03-02 21:17

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of 
Mailman/Cgi/create.py which fails to get the initial setup of lists created 
through the web quite right. This leads to spurious errors being logged on 
message archiving until bin/arch --wipe is run for such a list affected. Lists 
created with bin/newlist did not have this problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-09-23 21:45

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of 
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the 
problem was not present in patches for previous MM versions. In some 
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a 
list my be generated using the wrong archiver. Examining index pages in 
the archives of a list will show if this problem has affected that list. 
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe 
should resolve the problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 17:43

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

----------------------------------------------------------------------

Comment By: dfragos (dfragos)
Date: 2005-07-21 15:24

Message:
Logged In: YES 
user_id=1310569

what about MM 2.1.6?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 10:04

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-19 23:53

Message:
Logged In: YES 
user_id=696559

I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 15:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 14:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 05:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 17:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Sat Oct 21 11:43:24 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 21 Oct 2006 02:43:24 -0700
Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
Message-ID: <E1GbDO0-0007z8-PO@sc8-sf-web1.sourceforge.net>

Patches item #820723, was opened at 2003-10-09 18:19
Message generated for change (Comment added) made by mmokrejs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman/pipermail/MHonArc integration patch

Initial Comment:
This patch tightly integrates the MHonArc mail-to-HTML
convertor  with Mailman and its internal pipermail
archiving code. 

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2006-10-21 11:43

Message:
Logged In: YES 
user_id=696559

Yes, that helped. Thanks. After years I documented a bit
which patches I use for mailman:

#!/bin/sh
gzip -dc mailman-2.1.9.tgz | tar xvf -
cd mailman-2.1.9
patch -p1 < ../mailman-2.1.9-patches/modinc-2.1.9-0.1.patch
gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
gzip -dc ../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz
| patch -p1
cat ../mailman-2.1.9-patches/11_handle_propfind.patch |
patch -p0
cat ../mailman-2.1.9-patches/72_fblast_add_shebang.patch |
patch -p0
cat
../mailman-2.1.9-patches/75_emaillist_only_show_bad_emails.dpatch
| patch -p1
cat ../mailman-2.1.9-patches/passwd-rfc3834.patch | patch -p0
cat ../mailman-2.1.9-patches/mailman-2.1.6rc3-relpath.patch
| patch -p1


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-20 10:03

Message:
Logged In: YES 
user_id=75166

Apologies, but the URL cited above had to be changed when I changed hosting 
service provider as they have co-opted the /mailman/ URI root. See instead:

http://www.openinfo.co.uk/mm/patches/mhonarc/index.html

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-20 09:50

Message:
Logged In: YES 
user_id=75166

The file INSTALL.mhonarc-mm installed by this patch contains the following 
words. The same information is also on the openinfo web page whose URL is 
above.

Necessary Precursors
--------------------

The following patch must be applied to Mailman before applying this patch: 

1.	Mailman Patch #760567: both this patch and #760567 update the 
version number ...


----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2006-10-20 00:18

Message:
Logged In: YES 
user_id=696559

ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
patching file Mailman/Cgi/private.py
patching file Mailman/Defaults.py.in
ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1
patching file INSTALL.mhonarc-mm
patching file Mailman/Archiver/Archiver.py
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Archiver/pipermail.py
patching file Mailman/Cgi/create.py
patching file Mailman/Defaults.py.in
Hunk #2 succeeded at 1390 (offset 73 lines).
patching file Mailman/Errors.py
patching file Mailman/Gui/Archive.py
patching file Mailman/Mailbox.py
patching file Mailman/Version.py
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file
Mailman/Version.py.rej
patching file bin/arch
patching file bin/newlist
patching file templates/Makefile.in
patching file templates/en/author.mrc
patching file templates/en/mhonarc.mrc
patching file templates/en/subject.mrc
ribosome mailman-2.1.9 # less Mailman/Version.py.rej
***************
*** 39,45 ****
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
- DATA_FILE_VERSION = 96.1
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
--- 39,50 ----
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
+ # DATA_FILE_VERSION = 96.1
+ # 96.2 to take account of extra which_archiver and 
+ # archiver_when_wiped list attributes
+ # must be applied AFTER the modinc-2.1.7-0.1.patch
+ DATA_FILE_VERSION = 96.2
+ 
  
  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
ribosome mailman-2.1.9 # 

So, which patch do I have to apply before applying the 2.1.9
-0.1 version of this? It is a pitty this is not yet in the
official releases. I am using mailman-20041012.tar.bz2 with
these for some years and see only 2 or three types of error
in the logs. But damn mailman ignores some subscription
confirmation messages and breaks on some non-us-ascii
encoded messages so I should upgrade to see if it helps. :((

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-03 13:08

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-04-20 01:01

Message:
Logged In: YES 
user_id=75166

Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-03-02 22:17

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of 
Mailman/Cgi/create.py which fails to get the initial setup of lists created 
through the web quite right. This leads to spurious errors being logged on 
message archiving until bin/arch --wipe is run for such a list affected. Lists 
created with bin/newlist did not have this problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-09-23 23:45

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of 
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the 
problem was not present in patches for previous MM versions. In some 
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a 
list my be generated using the wrong archiver. Examining index pages in 
the archives of a list will show if this problem has affected that list. 
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe 
should resolve the problem.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2005-08-23 19:43

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

----------------------------------------------------------------------

Comment By: dfragos (dfragos)
Date: 2005-07-21 17:24

Message:
Logged In: YES 
user_id=1310569

what about MM 2.1.6?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-08-03 12:04

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the 
patch

----------------------------------------------------------------------

Comment By: Martin Mokrejs (mmokrejs)
Date: 2004-04-20 01:53

Message:
Logged In: YES 
user_id=696559

I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2004-01-02 16:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-22 16:32

Message:
Logged In: YES 
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-14 07:49

Message:
Logged In: YES 
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself 
defined in Defaults.py is the empty string and, until this is 
changed, the option to select MHonArc instead of pipermail for 
per-list archiving is not offered on the web admin GUI.

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-10-10 19:51

Message:
Logged In: YES 
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103

From noreply at sourceforge.net  Sun Oct 22 09:35:17 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 22 Oct 2006 00:35:17 -0700
Subject: [ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
Message-ID: <E1GbXrZ-0001eQ-Rs@sc8-sf-web5.sourceforge.net>

Patches item #1578756, was opened at 2006-10-17 08:45
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

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.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Handle unexpected HTTP method gracefully

Initial Comment:
Hi!

When Mailman is confronted with an unexpected HTTP
method type (e.g. PROPFIND instead of GET/HEAD/POST),
it crashes. The attached patch fixes that more
gracefully by throwing the appropriate HTTP error.

Thanks for considering.
Thijs

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-22 07:35

Message:
Logged In: YES 
user_id=75166

There is an alternative to fixing cgi scripts  to cope with inappropriate 
WebDAV methods being applied to them, which works regardless of whether 
they are Mailman cgi scripts or not.

Configure Apache not to apply WebDAV methods to inappropriate resources 
by the use of Apache directives such as DAV Off and LimitExcept GET POST. 
See:

http://httpd.apache.org/docs/2.0/mod/mod_dav.html

and

http://httpd.apache.org/docs/2.0/mod/core.html#limitexcept

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

From noreply at sourceforge.net  Sun Oct 22 12:03:32 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 22 Oct 2006 03:03:32 -0700
Subject: [ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
Message-ID: <E1GbaB2-0001Rq-KI@sc8-sf-web2.sourceforge.net>

Bugs item #1578539, was opened at 2006-10-17 00:03
Message generated for change (Comment added) made by stekardavid
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

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
Submitted By: Duelago (stekardavid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with Microsoft Entourage

Initial Comment:
When posting to a Mailman list with Microsoft Entourage
(all versions) the subject line gets crippled if you
use characters like ???.

Sm?g?sbord ends up liks Sm ? rg ? rdsbord.
I don't have this problem if I post to other list
servers like Majordomo or ezmlm. I guess we can blame
Microsoft, but why don't I have a problem with other
list solutions?




----------------------------------------------------------------------

>Comment By: Duelago (stekardavid)
Date: 2006-10-22 12:03

Message:
Logged In: YES 
user_id=1622511

I start with the Mailman headers
---

User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 22 Oct 2006 11:45:57 +0200
From: xxxxx <xxxxx at gof.se>
To: FK Cirrus Goteborgs skvallerlista <xxxxx at hoppafallskarm.nu>,
	swoop xxxxx <bofh-list-xxxxx at diegeekdie.com>
Message-ID: <C1610A75.D7E4%xxxxx at gof.se>
Thread-Topic:
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow==
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Subject: [CG] =?iso-8859-1?q?Sm_=F6_rg_=E5_sbord?=
X-BeenThere: xxxxx at hoppafallskarm.nu
X-Mailman-Version: 2.1.8rc1
Precedence: list
Reply-To: FK Cirrus Goteborgs skvallerlista
<xxxxx at hoppafallskarm.nu>
List-Id: FK Cirrus Goteborgs skvallerlista
<xxxxx.hoppafallskarm.nu>
List-Unsubscribe:
<http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>,
	<mailto:xxxxx-request at hoppafallskarm.nu?subject=unsubscribe>
List-Post: <mailto:xxxxx at hoppafallskarm.nu>
List-Help: <mailto:xxxxx-request at hoppafallskarm.nu?subject=help>
List-Subscribe:
<http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>,
	<mailto:xxxxx-request at hoppafallskarm.nu?subject=subscribe>
Sender: xxxxx-bounces at hoppafallskarm.nu
Errors-To: xxxxx-bounces at hoppafallskarm.nu

Detta =E4r ett test. Ignorera


---
And this are the headers when I send a mail directly from
Entourage to a Gmail-adress (Works fine)

X-Gmail-Received: 22aebdd20f2ca6fecf30a29de7d439cfb62ebeb3
Delivered-To: stekarxxxxx at gmail.com
Received: by 10.78.174.12 with SMTP id w12cs532759hue;
        Sun, 22 Oct 2006 02:46:12 -0700 (PDT)
Received: by 10.48.14.4 with SMTP id 4mr11975145nfn;
        Sun, 22 Oct 2006 02:46:12 -0700 (PDT)
Return-Path: <xxxxx at gof.se>
Received: from www.gof.se ([193.201.96.157])
        by mx.google.com with ESMTP id
p20si769907nfc.2006.10.22.02.46.11;
        Sun, 22 Oct 2006 02:46:12 -0700 (PDT)
Received-SPF: neutral (google.com: 193.201.96.157 is neither
permitted nor denied by best guess record for domain of
xxxxx at gof.se)
Received: from [83.215.47.240]
(83-215-47-240.bruck.dyn.salzburg-online.at [83.215.47.240])
	by www.gof.se (Postfix) with ESMTP id DB574BEF10;
	Sun, 22 Oct 2006 11:46:00 +0200 (CEST)
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 22 Oct 2006 11:45:57 +0200
Subject: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
From: xxxxx <xxxxx at gof.se>
To: FK Cirrus Goteborgs skvallerlista <xxxxx at hoppafallskarm.nu>,
	swoop xxxxx <bofh-list-xxxxx at diegeekdie.com>
Message-ID: <C1610A75.D7E4%xxxxx at gof.se>
Thread-Topic:
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow==
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Detta =E4r ett test. Ignorera

--?
Headers from ezmlm. Also works fine!

Return-Path:
<bofh-list-xxxxx-return-21-xxxxx=gof.se at diegeekdie.com>
X-Spam-Checker-Version: SpamAssassin 3.1.6-gr0 (2006-10-03)
on olga
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 required=4.0
tests=AWL,BAYES_00,SPF_PASS,
	SUBJECT_ENCODED_TWICE autolearn=no version=3.1.6-gr0
X-Original-To: xxxxx at gof.se
Delivered-To: xxxxx at gof.se
Received: from smtp.hogia.net (phillip.hogia.net [195.78.148.4])
	by www.gof.se (Postfix) with SMTP id 41E8CBEF10
	for <xxxxx at gof.se>; Sun, 22 Oct 2006 11:46:30 +0200 (CEST)
Received: (qmail 14409 invoked by uid 509); 22 Oct 2006
11:46:12 +0200
Mailing-List: contact bofh-list-xxxxx-help at diegeekdie.com;
run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Post: <mailto:bofh-list-xxxxx at diegeekdie.com>
List-Help: <mailto:bofh-list-xxxxx-help at diegeekdie.com>
List-Unsubscribe:
<mailto:bofh-list-xxxxx-unsubscribe at diegeekdie.com>
List-Subscribe:
<mailto:bofh-list-xxxxx-subscribe at diegeekdie.com>
Delivered-To: mailing list bofh-list-xxxxx at diegeekdie.com
Received: (qmail 14397 invoked by uid 64017); 22 Oct 2006
11:46:12 +0200
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 22 Oct 2006 11:45:57 +0200
From: xxxxx <xxxxx at gof.se>
To: FK Cirrus Goteborgs skvallerlista
<listan at hoppafallskarm.nu>,
	swoop xxxxx <bofh-list-xxxxx at diegeekdie.com>
Message-ID: <C1610A75.D7E4%xxxxx at gof.se>
Thread-Topic:
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow==
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Subject: [xxxxx]
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord

Detta =E4r ett test. Ignorera



----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-10-17 02:45

Message:
Logged In: YES 
user_id=67709

I tested with my Entourage which I didn't use so far.
It gave:
  Sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord
and ends up by processed by mailman email.Header module:
  Sm =?iso-8859-1?q?=F6?= g =?iso-8859-1?q?=E5?= sbord

It looks like they break a statement of RFC-2047:
    Ordinary ASCII text and 'encoded-word's may appear
together in the
    same header field.  However, an 'encoded-word' that
appears in a
    header field defined as '*text' MUST be separated from
any adjacent
    'encoded-word' or 'text' by 'linear-white-space'.



----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-17 01:38

Message:
Logged In: YES 
user_id=1123998

I should say, I am unable to duplicate with Mailman 2.1.5
and Thunderbird. I don't have Entourage to test with.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-17 01:30

Message:
Logged In: YES 
user_id=1123998

I am unable to duplicate the problem on Mailman 2.1.5.

Can you post the raw Subject: header from both the message
as sent to the list and as received from the list. I'm
looking for things that look like

Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?=

or

Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?=

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

From noreply at sourceforge.net  Sun Oct 22 14:59:06 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 22 Oct 2006 05:59:06 -0700
Subject: [ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
Message-ID: <E1Gbcuw-00076K-KA@sc8-sf-web1.sourceforge.net>

Bugs item #1578539, was opened at 2006-10-16 22:03
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

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: Invalid
Priority: 5
Submitted By: Duelago (stekardavid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with Microsoft Entourage

Initial Comment:
When posting to a Mailman list with Microsoft Entourage
(all versions) the subject line gets crippled if you
use characters like ???.

Sm?g?sbord ends up liks Sm ? rg ? rdsbord.
I don't have this problem if I post to other list
servers like Majordomo or ezmlm. I guess we can blame
Microsoft, but why don't I have a problem with other
list solutions?




----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-10-22 12:59

Message:
Logged In: YES 
user_id=67709

As I stated on 2006-10-17, Microsoft Entourage's way of
encoding violates the RFC-2047 in that encoding should be in
'encoded-WORD' and not in 'encoded-character'. i.e.,
  =?iso-8859-1?q?sm=F6g=E5sbord?= ... OK
  =?iso-8859-1?b?c232Z+VzYm9yZA==?= ... OK
  sm=?iso-8859-1?q?=F6?=g=?iso-8859-1?q?=E5?=sbord ... NG
  sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord ... NG



----------------------------------------------------------------------

Comment By: Duelago (stekardavid)
Date: 2006-10-22 10:03

Message:
Logged In: YES 
user_id=1622511

I start with the Mailman headers
---

User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 22 Oct 2006 11:45:57 +0200
From: xxxxx <xxxxx at gof.se>
To: FK Cirrus Goteborgs skvallerlista <xxxxx at hoppafallskarm.nu>,
	swoop xxxxx <bofh-list-xxxxx at diegeekdie.com>
Message-ID: <C1610A75.D7E4%xxxxx at gof.se>
Thread-Topic:
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow==
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Subject: [CG] =?iso-8859-1?q?Sm_=F6_rg_=E5_sbord?=
X-BeenThere: xxxxx at hoppafallskarm.nu
X-Mailman-Version: 2.1.8rc1
Precedence: list
Reply-To: FK Cirrus Goteborgs skvallerlista
<xxxxx at hoppafallskarm.nu>
List-Id: FK Cirrus Goteborgs skvallerlista
<xxxxx.hoppafallskarm.nu>
List-Unsubscribe:
<http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>,
	<mailto:xxxxx-request at hoppafallskarm.nu?subject=unsubscribe>
List-Post: <mailto:xxxxx at hoppafallskarm.nu>
List-Help: <mailto:xxxxx-request at hoppafallskarm.nu?subject=help>
List-Subscribe:
<http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>,
	<mailto:xxxxx-request at hoppafallskarm.nu?subject=subscribe>
Sender: xxxxx-bounces at hoppafallskarm.nu
Errors-To: xxxxx-bounces at hoppafallskarm.nu

Detta =E4r ett test. Ignorera


---
And this are the headers when I send a mail directly from
Entourage to a Gmail-adress (Works fine)

X-Gmail-Received: 22aebdd20f2ca6fecf30a29de7d439cfb62ebeb3
Delivered-To: stekarxxxxx at gmail.com
Received: by 10.78.174.12 with SMTP id w12cs532759hue;
        Sun, 22 Oct 2006 02:46:12 -0700 (PDT)
Received: by 10.48.14.4 with SMTP id 4mr11975145nfn;
        Sun, 22 Oct 2006 02:46:12 -0700 (PDT)
Return-Path: <xxxxx at gof.se>
Received: from www.gof.se ([193.201.96.157])
        by mx.google.com with ESMTP id
p20si769907nfc.2006.10.22.02.46.11;
        Sun, 22 Oct 2006 02:46:12 -0700 (PDT)
Received-SPF: neutral (google.com: 193.201.96.157 is neither
permitted nor denied by best guess record for domain of
xxxxx at gof.se)
Received: from [83.215.47.240]
(83-215-47-240.bruck.dyn.salzburg-online.at [83.215.47.240])
	by www.gof.se (Postfix) with ESMTP id DB574BEF10;
	Sun, 22 Oct 2006 11:46:00 +0200 (CEST)
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 22 Oct 2006 11:45:57 +0200
Subject: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
From: xxxxx <xxxxx at gof.se>
To: FK Cirrus Goteborgs skvallerlista <xxxxx at hoppafallskarm.nu>,
	swoop xxxxx <bofh-list-xxxxx at diegeekdie.com>
Message-ID: <C1610A75.D7E4%xxxxx at gof.se>
Thread-Topic:
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow==
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Detta =E4r ett test. Ignorera

--?
Headers from ezmlm. Also works fine!

Return-Path:
<bofh-list-xxxxx-return-21-xxxxx=gof.se at diegeekdie.com>
X-Spam-Checker-Version: SpamAssassin 3.1.6-gr0 (2006-10-03)
on olga
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 required=4.0
tests=AWL,BAYES_00,SPF_PASS,
	SUBJECT_ENCODED_TWICE autolearn=no version=3.1.6-gr0
X-Original-To: xxxxx at gof.se
Delivered-To: xxxxx at gof.se
Received: from smtp.hogia.net (phillip.hogia.net [195.78.148.4])
	by www.gof.se (Postfix) with SMTP id 41E8CBEF10
	for <xxxxx at gof.se>; Sun, 22 Oct 2006 11:46:30 +0200 (CEST)
Received: (qmail 14409 invoked by uid 509); 22 Oct 2006
11:46:12 +0200
Mailing-List: contact bofh-list-xxxxx-help at diegeekdie.com;
run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Post: <mailto:bofh-list-xxxxx at diegeekdie.com>
List-Help: <mailto:bofh-list-xxxxx-help at diegeekdie.com>
List-Unsubscribe:
<mailto:bofh-list-xxxxx-unsubscribe at diegeekdie.com>
List-Subscribe:
<mailto:bofh-list-xxxxx-subscribe at diegeekdie.com>
Delivered-To: mailing list bofh-list-xxxxx at diegeekdie.com
Received: (qmail 14397 invoked by uid 64017); 22 Oct 2006
11:46:12 +0200
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 22 Oct 2006 11:45:57 +0200
From: xxxxx <xxxxx at gof.se>
To: FK Cirrus Goteborgs skvallerlista
<listan at hoppafallskarm.nu>,
	swoop xxxxx <bofh-list-xxxxx at diegeekdie.com>
Message-ID: <C1610A75.D7E4%xxxxx at gof.se>
Thread-Topic:
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow==
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Subject: [xxxxx]
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord

Detta =E4r ett test. Ignorera



----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-10-17 00:45

Message:
Logged In: YES 
user_id=67709

I tested with my Entourage which I didn't use so far.
It gave:
  Sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord
and ends up by processed by mailman email.Header module:
  Sm =?iso-8859-1?q?=F6?= g =?iso-8859-1?q?=E5?= sbord

It looks like they break a statement of RFC-2047:
    Ordinary ASCII text and 'encoded-word's may appear
together in the
    same header field.  However, an 'encoded-word' that
appears in a
    header field defined as '*text' MUST be separated from
any adjacent
    'encoded-word' or 'text' by 'linear-white-space'.



----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 23:38

Message:
Logged In: YES 
user_id=1123998

I should say, I am unable to duplicate with Mailman 2.1.5
and Thunderbird. I don't have Entourage to test with.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-10-16 23:30

Message:
Logged In: YES 
user_id=1123998

I am unable to duplicate the problem on Mailman 2.1.5.

Can you post the raw Subject: header from both the message
as sent to the list and as received from the list. I'm
looking for things that look like

Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?=

or

Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?=

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_id=103

From noreply at sourceforge.net  Sun Oct 22 16:34:20 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 22 Oct 2006 07:34:20 -0700
Subject: [ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
Message-ID: <E1GbeP6-0001rl-Fq@sc8-sf-web2.sourceforge.net>

Patches item #1578756, was opened at 2006-10-17 10:45
Message generated for change (Comment added) made by kink
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

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.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Handle unexpected HTTP method gracefully

Initial Comment:
Hi!

When Mailman is confronted with an unexpected HTTP
method type (e.g. PROPFIND instead of GET/HEAD/POST),
it crashes. The attached patch fixes that more
gracefully by throwing the appropriate HTTP error.

Thanks for considering.
Thijs

----------------------------------------------------------------------

>Comment By: Thijs Kinkhorst (kink)
Date: 2006-10-22 16:34

Message:
Logged In: YES 
user_id=285765

Yes, that's true. However, in any case mailman should output
a sensible error, I think?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-22 09:35

Message:
Logged In: YES 
user_id=75166

There is an alternative to fixing cgi scripts  to cope with inappropriate 
WebDAV methods being applied to them, which works regardless of whether 
they are Mailman cgi scripts or not.

Configure Apache not to apply WebDAV methods to inappropriate resources 
by the use of Apache directives such as DAV Off and LimitExcept GET POST. 
See:

http://httpd.apache.org/docs/2.0/mod/mod_dav.html

and

http://httpd.apache.org/docs/2.0/mod/core.html#limitexcept

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

From noreply at sourceforge.net  Sun Oct 22 19:22:56 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 22 Oct 2006 10:22:56 -0700
Subject: [ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
Message-ID: <E1Gbh2G-00069e-B7@sc8-sf-web6.sourceforge.net>

Patches item #1578756, was opened at 2006-10-17 08:45
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

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.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Handle unexpected HTTP method gracefully

Initial Comment:
Hi!

When Mailman is confronted with an unexpected HTTP
method type (e.g. PROPFIND instead of GET/HEAD/POST),
it crashes. The attached patch fixes that more
gracefully by throwing the appropriate HTTP error.

Thanks for considering.
Thijs

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-22 17:22

Message:
Logged In: YES 
user_id=75166

There are two issues:

1. Having Mailman's CGI scripts defend themselves against 
inappropriate application of WebDAV methods is good and would 
probably be required for RFC compliance if CGI had an RFC. The 
fact the fix only requires change to a single driver script 
to defend multiple functional scripts is a tribute to the 
original design.

2. Inappropriate configuration of Apache servers with respect
to WebDAV is wrong. 

	a. Many if not most legacy CGI scripts will not have been
	programmed to defend themselves against WebDAV methods. 
	Fixing them on an existing system is time consuming and 
	error prone. Fixing Apache config is easier and more 
	reliable.
	
	b. Mailman's pipermail archives and much other served 
	resource should also not be subject to WebDAV methods  
	Only getting the Apache config right can deal with this.

Fixing CGI scripts is good. Getting the Apache configuration  
correct is more important. 


----------------------------------------------------------------------

Comment By: Thijs Kinkhorst (kink)
Date: 2006-10-22 14:34

Message:
Logged In: YES 
user_id=285765

Yes, that's true. However, in any case mailman should output
a sensible error, I think?

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2006-10-22 07:35

Message:
Logged In: YES 
user_id=75166

There is an alternative to fixing cgi scripts  to cope with inappropriate 
WebDAV methods being applied to them, which works regardless of whether 
they are Mailman cgi scripts or not.

Configure Apache not to apply WebDAV methods to inappropriate resources 
by the use of Apache directives such as DAV Off and LimitExcept GET POST. 
See:

http://httpd.apache.org/docs/2.0/mod/mod_dav.html

and

http://httpd.apache.org/docs/2.0/mod/core.html#limitexcept

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_id=103

From noreply at sourceforge.net  Sat Oct 28 02:57:09 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 27 Oct 2006 17:57:09 -0700
Subject: [ mailman-Bugs-1586072 ] Spam Filter ACCEPT rule not valid
Message-ID: <E1GdcVZ-0000B7-Lp@sc8-sf-web4.sourceforge.net>

Bugs item #1586072, was opened at 2006-10-28 00:57
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=1586072&group_id=103

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: Mez (ubuntumez)
Assigned to: Nobody/Anonymous (nobody)
Summary: Spam Filter ACCEPT rule not valid

Initial Comment:
In my setup, I wish to have a moderated member list, 
however, I also wish this list to be able to recieve 
email regarding bugs from Launchpad 
(http://launchpad.net)

The way that Launchpad sends the bugs out is to use 
the users email address reporting the bug in 
the "From:" header, but uses special headers to 
identify the email as coming from Launchpad

Obviously, I could just accept each email as it comes 
in, and add each sender to the approved list, however, 
I would rather that Mailman accept emails if their 
headers match the Spam Filters (and the spam filter is 
set to accept)

At the moment, it matches the spam header, but doesnt 
do anything to the message - the default action for 
accept is "do nothing here" - which then passes the 
message down the chain, to be intercepted by another 
part of the code that holds the message.

Changing the pipeline won't make any difference here, 
as the way that mailman works with this is that it 
doesnt set anything to say "approve this" it just 
says "we're not going to do anything with this here" - 
changging the pipeline would just catch the "Non 
member posting" at a different point.

I'd like the Spam filters when set to Accept to 
actually ACCEPT the email, rather than just pass it on 
to other Handlers.

I'm trying to hack on this myself, and if I can will 
post a patch, but my trials have been fruitless so far

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1586072&group_id=103

From noreply at sourceforge.net  Sat Oct 28 03:20:40 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 27 Oct 2006 18:20:40 -0700
Subject: [ mailman-Feature Requests-1586072 ] Spam Filter ACCEPT rule not valid
Message-ID: <E1GdcsK-0003RD-JV@sc8-sf-web1.sourceforge.net>

Feature Requests item #1586072, was opened at 2006-10-27 17:57
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1586072&group_id=103

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: Mez (ubuntumez)
Assigned to: Nobody/Anonymous (nobody)
Summary: Spam Filter ACCEPT rule not valid

Initial Comment:
In my setup, I wish to have a moderated member list, 
however, I also wish this list to be able to recieve 
email regarding bugs from Launchpad 
(http://launchpad.net)

The way that Launchpad sends the bugs out is to use 
the users email address reporting the bug in 
the "From:" header, but uses special headers to 
identify the email as coming from Launchpad

Obviously, I could just accept each email as it comes 
in, and add each sender to the approved list, however, 
I would rather that Mailman accept emails if their 
headers match the Spam Filters (and the spam filter is 
set to accept)

At the moment, it matches the spam header, but doesnt 
do anything to the message - the default action for 
accept is "do nothing here" - which then passes the 
message down the chain, to be intercepted by another 
part of the code that holds the message.

Changing the pipeline won't make any difference here, 
as the way that mailman works with this is that it 
doesnt set anything to say "approve this" it just 
says "we're not going to do anything with this here" - 
changging the pipeline would just catch the "Non 
member posting" at a different point.

I'd like the Spam filters when set to Accept to 
actually ACCEPT the email, rather than just pass it on 
to other Handlers.

I'm trying to hack on this myself, and if I can will 
post a patch, but my trials have been fruitless so far

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-10-27 18:20

Message:
Logged In: YES 
user_id=1123998

Spam filters are working as designed. Therefore, I am moving
this to feature requests because that's what it is.

For your implemention efforts, if you modify the end of the
process() function in SPAMDetect.py to read

                if action == mm_cfg.ACCEPT:
                    msgdata['approved'] = 1
                    return

That will make an ACCEPT rule match bypass all other holds
except emergency moderation. If you want to bypass emergency
moderation too, add also

                    msgdata['adminapproved'] = 1

See Mailman/Handlers/Approve.py

Note however that it is probably better to use a custom
handler for this as you then won't have to maintain a patch
across updates. See
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.067.htp


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1586072&group_id=103

From noreply at sourceforge.net  Tue Oct 31 03:59:27 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 30 Oct 2006 18:59:27 -0800
Subject: [ mailman-Patches-1587651 ] Roster should list private members to
	admins
Message-ID: <E1GejqZ-0005fg-CB@sc8-sf-web2.sourceforge.net>

Patches item #1587651, was opened at 2006-10-30 21:59
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=1587651&group_id=103

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: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Eric Price (eprice)
Assigned to: Nobody/Anonymous (nobody)
Summary: Roster should list private members to admins

Initial Comment:
The roster page omits members of a list who choose to
remain concealed, even when the viewer has admin
authorization.  This means admins cannot get a single
list of all list members from the web interface.

The roster should instead list hidden members to people
who logged in with the admin password.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1587651&group_id=103