From framstag at rus.uni-stuttgart.de  Wed Jul  1 08:50:43 2009
From: framstag at rus.uni-stuttgart.de (Ulli Horlacher)
Date: Wed, 1 Jul 2009 08:50:43 +0200
Subject: [Mailman-Developers] pre-filter for mailman
Message-ID: <20090701065043.GG30240@fex.rus.uni-stuttgart.de>


Since mailman is missing some important (for me) features and I do not
know python I have written a pre-filter in perl.

The features are:

- the admin can defines a config files
	: a list of allowed MIME types
        : weed = commercial ads footer 

- the mail is disassembled in its MIME parts, only allowed TEXT parts get
  in the reassembled mail, not allowed MIME types are substituted with a
  message "part XXX (MIME-type YYY) is not allowed, ignored", allowed
  MIME types are saved on the web server and substituted with a message
  "part XXX is saved at URL YYY"

- missing References header are added

- bad quoting (by wrong auto-wrapping of editor) is corrected

- overlong lines are reformated 

- non-RFC Subject prefixes like "AW:" are substituted with correct "Re:"

- commercial ads are deleted

- full quoting at end of mail is removed




-- 
Ullrich Horlacher              Server- und Arbeitsplatzsysteme
Rechenzentrum                  E-Mail: horlacher at rus.uni-stuttgart.de
Universitaet Stuttgart         Tel:    ++49-711-685-65868
Allmandring 30                 Fax:    ++49-711-682357
70550 Stuttgart (Germany)      WWW:    http://www.rus.uni-stuttgart.de/

From mark at msapiro.net  Thu Jul  2 04:13:45 2009
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 1 Jul 2009 19:13:45 -0700
Subject: [Mailman-Developers] pre-filter for mailman
In-Reply-To: <20090701065043.GG30240@fex.rus.uni-stuttgart.de>
Message-ID: <PC1922009070119134500787842e53b@Notebook>

Ulli Horlacher wrote:
>
>Since mailman is missing some important (for me) features and I do not
>know python I have written a pre-filter in perl.
>
>The features are:
>
>- the admin can defines a config files
>	: a list of allowed MIME types
>        : weed = commercial ads footer 
>
>- the mail is disassembled in its MIME parts, only allowed TEXT parts get
>  in the reassembled mail, not allowed MIME types are substituted with a
>  message "part XXX (MIME-type YYY) is not allowed, ignored", allowed
>  MIME types are saved on the web server and substituted with a message
>  "part XXX is saved at URL YYY"


Mailman's content filtering together with scrub_nondigest does
something similar.


>- missing References header are added


Constructed from what?


>- bad quoting (by wrong auto-wrapping of editor) is corrected
>
>- overlong lines are reformated 
>
>- non-RFC Subject prefixes like "AW:" are substituted with correct "Re:"
>
>- commercial ads are deleted
>
>- full quoting at end of mail is removed


I am interested in how you do these, particularly the last two. Can I
see your code?

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


From framstag at rus.uni-stuttgart.de  Thu Jul  2 21:16:00 2009
From: framstag at rus.uni-stuttgart.de (Ulli Horlacher)
Date: Thu, 2 Jul 2009 21:16:00 +0200
Subject: [Mailman-Developers] pre-filter for mailman
In-Reply-To: <PC1922009070119134500787842e53b@Notebook>
References: <20090701065043.GG30240@fex.rus.uni-stuttgart.de>
	<PC1922009070119134500787842e53b@Notebook>
Message-ID: <20090702191600.GO30240@fex.rus.uni-stuttgart.de>

On Wed 2009-07-01 (19:13), Mark Sapiro wrote:

> >- the mail is disassembled in its MIME parts, only allowed TEXT parts get
> >  in the reassembled mail, not allowed MIME types are substituted with a
> >  message "part XXX (MIME-type YYY) is not allowed, ignored", allowed
> >  MIME types are saved on the web server and substituted with a message
> >  "part XXX is saved at URL YYY"
> 
> 
> Mailman's content filtering together with scrub_nondigest does
> something similar.

Oh... this must be a new feature in 2.1.11?
I am still running 2.1.9
Sorry to offer you features mailman already has.

My excuse: my auto-deattach-feature is several years old. I only found now
the time to announce it.


> >- missing References header are added
> 
> Constructed from what?

>From old mails.
My filter does a full text search over all mails of the last 2 weeks.


> >- commercial ads are deleted
> >
> >- full quoting at end of mail is removed
> 
> 
> I am interested in how you do these, particularly the last two. Can I
> see your code?

I can send it to everyone who is interested. 
I do not want to put it online because the documentation is not good enogh.
I first want to see if there is really interest in my filter, then I will
enhance the documentation. Writing documentation no one will read is
maximum boring :-)

-- 
Ullrich Horlacher              Server- und Arbeitsplatzsysteme
Rechenzentrum                  E-Mail: horlacher at rus.uni-stuttgart.de
Universitaet Stuttgart         Tel:    ++49-711-685-65868
Allmandring 30                 Fax:    ++49-711-682357
70550 Stuttgart (Germany)      WWW:    http://www.rus.uni-stuttgart.de/

From bibekshrestha at gmail.com  Thu Jul  2 11:59:35 2009
From: bibekshrestha at gmail.com (Bibek Shrestha)
Date: Thu, 2 Jul 2009 15:44:35 +0545
Subject: [Mailman-Developers] External Interface XMLRPC and REST
Message-ID: <868f3a740907020259x66a25256yd68ec49e85dcad48@mail.gmail.com>

Hi All,

We are trying to integrate Mailman with external cms Drupal. For this we are
looking for two possible interface XMLRPC and REST.

Before we begin, Im just curious as to which Mailman Developers would
recommend to work with and supported for a longer period?

Regards
-- 
Bibek Shrestha
bibekshrestha at gmail dot com

From p at state-of-mind.de  Fri Jul  3 09:31:42 2009
From: p at state-of-mind.de (Patrick Ben Koetter)
Date: Fri, 3 Jul 2009 09:31:42 +0200
Subject: [Mailman-Developers] External Interface XMLRPC and REST
In-Reply-To: <868f3a740907020259x66a25256yd68ec49e85dcad48@mail.gmail.com>
References: <868f3a740907020259x66a25256yd68ec49e85dcad48@mail.gmail.com>
Message-ID: <20090703073141.GB22137@state-of-mind.de>

* Bibek Shrestha <bibekshrestha at gmail.com>:
> Hi All,
> 
> We are trying to integrate Mailman with external cms Drupal. For this we are
> looking for two possible interface XMLRPC and REST.
> 
> Before we begin, Im just curious as to which Mailman Developers would
> recommend to work with and supported for a longer period?

MM3 will offer a RESTful server.

p at rick

-- 
state of mind
Digitale Kommunikation

http://www.state-of-mind.de

Franziskanerstra?e 15	   Telefon +49 89 3090 4664
81669 M?nchen              Telefax +49 89 3090 4666

Amtsgericht M?nchen        Partnerschaftsregister PR 563

From barry at list.org  Fri Jul  3 15:44:36 2009
From: barry at list.org (Barry Warsaw)
Date: Fri, 3 Jul 2009 09:44:36 -0400
Subject: [Mailman-Developers] External Interface XMLRPC and REST
In-Reply-To: <868f3a740907020259x66a25256yd68ec49e85dcad48@mail.gmail.com>
References: <868f3a740907020259x66a25256yd68ec49e85dcad48@mail.gmail.com>
Message-ID: <C6FD84E4-7673-4357-83BC-6F2BBB0F4CD2@list.org>

On Jul 2, 2009, at 5:59 AM, Bibek Shrestha wrote:

> We are trying to integrate Mailman with external cms Drupal. For  
> this we are
> looking for two possible interface XMLRPC and REST.
>
> Before we begin, Im just curious as to which Mailman Developers would
> recommend to work with and supported for a longer period?

Definitely REST.

The Mailman 3 code base already has the framework for a RESTful admin  
interface, and there are two resources currently exposed by it, the  
system resource and the domains resource.  They're read-only at the  
moment, but the infrastructure seems solid enough that I'm now  
building out other resources, including writable resources.

The work is happening in the Mailman 3 trunk.

https://code.launchpad.net/~mailman-coders/mailman/3.0

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090703/936ae792/attachment.pgp>

From barry at python.org  Thu Jul  9 17:26:38 2009
From: barry at python.org (Barry Warsaw)
Date: Thu, 9 Jul 2009 11:26:38 -0400
Subject: [Mailman-Developers] [Mailman-Users] Rewriting or identifying
	late bounces
In-Reply-To: <1da0196f18dc9c50c7d7ab36b11ee544.squirrel@www.msapiro.net>
References: <20090707212248.GP19748@mail.incertum.net>
	<c99e9f27f871e2796dd56fe59cb771b5.squirrel@www.msapiro.net>
	<20090708165628.GT19748@mail.incertum.net>
	<4A551E10.6070501@shub-internet.org>
	<20090708231242.GA19423@mail.incertum.net>
	<4A557B39.9000001@shub-internet.org>
	<20090709110003.GC19423@mail.incertum.net>
	<1da0196f18dc9c50c7d7ab36b11ee544.squirrel@www.msapiro.net>
Message-ID: <96E2136A-2140-4ADA-A102-F93126669AD1@python.org>

[Adding mailman-developers]

On Jul 9, 2009, at 10:22 AM, Mark Sapiro wrote:

> Stefan F?rster wrote:
>>
>> BTW - will MM3 be able to utilize the VERP features offered by many
>> modern MTAs?
>
>
> There are patches for Postfix which can probably be adapted for other
> MTAs. See the thread "Patch for use of Postfix VERP support"  
> starting at
> <http://mail.python.org/pipermail/mailman-users/2009-January/064588.html 
> >.
>
> This seems to be a good idea for future Mailman. I don't know if  
> Barry has
> thought about it for MM3, but I will look at it for 2.2.

I have, and it doesn't look difficult to do, although I really want to  
rework the current delivery architecture so that it's more modular.   
This would also allow different lists to have different delivery  
mechanisms (e.g. bulk vs. individual) and should be more efficient and  
more extensible.

VERPing is really only one half of the "personalization" or individual  
delivery story.  Ideally it's the half that would by default always be  
enabled since it improves the reliability of your memberships.  It's  
this part that would benefit greatly from adding MTA-specific  
support.  I think Exim supports VERPing without an SMTP extension, and  
I get the impression it can be made to work in Sendmail too.

The other half is really a "mail merge" operation, where the headers  
and footers (currently, but maybe someday the email body) contains  
placeholders that get filled in with personal information for the  
specific user.  I'm not aware of a standard way to do this in any MTA,  
so I think if you want to do this kind of message body  
personalization, you still have to do that in Mailman.  I'd like to  
support this better and would consider MTA-specific approaches.

Mailman also supports something called "full personalization" which  
hacks other headers too.  I put this in the category of mail merging  
since I'm not aware of any MTAs providing support for that either.

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090709/f6337dd4/attachment.pgp>

From ryan at linuxbox.com  Wed Jul 15 17:49:50 2009
From: ryan at linuxbox.com (Ryan Jud Hughes)
Date: Wed, 15 Jul 2009 11:49:50 -0400 (EDT)
Subject: [Mailman-Developers] Templates and CSS for Mailman
Message-ID: <alpine.DEB.2.00.0907151144260.19211@galaxor>

Hi.  I've heard people make some noises about wanting better CSS control 
of their mailman sites.  I've also wanted better template control -- 
currently, a lot of the cgi scripts create html in a hard-coded fashion.

I just posted a bug report that contains a patch that I've been working on 
to address these issues.  Most of the cgi is now created by preparing a 
dictionary with the strings, and running it through the template system. 
The archives, too.

There are a small number of template files to edit -- such as page.html -- 
that will end up putting your theme on all the pages.

I also created mailman.css, with default css to keep the current mailman 
look, and an empty site.css that can be tailored to your site.

I created bug #39830 (https://bugs.launchpad.net/mailman/+bug/398030) with 
my patch in it.

Could somebody please take a look at it and tell me what you think?

Thanks.
--Ryan

From ryan at linuxbox.com  Fri Jul 17 18:18:30 2009
From: ryan at linuxbox.com (Ryan Jud Hughes)
Date: Fri, 17 Jul 2009 12:18:30 -0400 (EDT)
Subject: [Mailman-Developers] Last 30 days archive
Message-ID: <alpine.DEB.2.00.0907171212570.26569@galaxor>

Hi.  I was doing some work for people that wanted a new mailman archive 
feature.  In addition to the different archives for the months, they 
wanted one that showed all mail traffic for the last 30 days -- whether or 
not that happened to correspond to month boundaries.

I made a patch against 2.1.12 and posted it on this bug: 
https://bugs.launchpad.net/mailman/+bug/400422

I hope somebody can take a look at it.

Incoming mail gets sent to the "last30" archive as well as whichever one 
it's supposed to go to.  It also works with bin/arch --wipe.  I also 
created a new command-line option for the arch program.  You can do 
bin/arch --last30 listname, and it will go through the last-30-days 
archive and remove the mails that are older than 30 days, and rebuild the 
indexes and prev/next.

So, tell me what you think.

Thanks.
--Ryan

From florian at wagner-flo.net  Mon Jul 20 10:31:22 2009
From: florian at wagner-flo.net (Florian Wagner)
Date: Mon, 20 Jul 2009 10:31:22 +0200
Subject: [Mailman-Developers] Merge request
Message-ID: <20090720103122.13a3d544@auedv3.syscomp.de>

Hello,

a few weeks ago I submitted a merge request through launchpad for a
small set of changes I've made to Mailman (see [1]). So far there has
been no reaction at all. Is there reason for this? Are patches to this
list preferred?


Regards
Florian Wagner

[1] https://code.launchpad.net/~wagnerflo/mailman/2.1-postfix-transport/+merge/7901
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090720/ebea4cb0/attachment.pgp>

From mark at msapiro.net  Tue Jul 21 05:40:22 2009
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 20 Jul 2009 20:40:22 -0700
Subject: [Mailman-Developers] Merge request
In-Reply-To: <20090720103122.13a3d544@auedv3.syscomp.de>
Message-ID: <PC1922009072020402209211787696f@msapiro>

Florian Wagner wrote:
>
>a few weeks ago I submitted a merge request through launchpad for a
>small set of changes I've made to Mailman (see [1]). So far there has
>been no reaction at all. Is there reason for this? Are patches to this
>list preferred?


A bzr branch and merge proposal such as the one at

>[1] https://code.launchpad.net/~wagnerflo/mailman/2.1-postfix-transport/+merge/7901

is definitely preferred over patches.

There are at least two reasons for no reaction from me.

1) Even though I am listed as a reviewer in the proposal, I do not
recall getting any push notice from Launchpad about the proposal. The
message here is in addition to proposing a merge on Launchpad, post a
note to Mailman-Developers as you now have done.

2) For various personal reasons, I have not been doing too much actual
code maintenance on Mailman the last couple of months, plus I was
traveling on vacation from June 27 through July 12 and I had a laptop
disaster during this time so even if I had gotten a notification, I
probably wouldn't have gotten to it yet.

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


From barry at list.org  Tue Jul 21 11:04:05 2009
From: barry at list.org (Barry Warsaw)
Date: Tue, 21 Jul 2009 05:04:05 -0400
Subject: [Mailman-Developers] Launchpad is Open Source
Message-ID: <D5829880-A21F-47DB-AAB2-C287EE716729@list.org>

Sometimes, insomnia has its reward:

http://www.ubuntu.com/news/canonical-open-sources-launchpad/

Yes, the entire platform, the whole kit-and-kaboodle.  Licensed under  
the AGPLv3.

https://dev.launchpad.net/Getting

It's nice both to be hosting our GNU project on open source, and  
personally to be working full time on pure open source software.  Note  
too the fact that Mailman runs Launchpad's mailing lists (no big  
surprise there) and if anybody has interest in discussing how this  
actually happens, we can do that here or in the various Launchpad  
forums.

Enjoy,
-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090721/284b14b0/attachment.pgp>

From barry at python.org  Tue Jul 21 12:17:23 2009
From: barry at python.org (Barry Warsaw)
Date: Tue, 21 Jul 2009 06:17:23 -0400
Subject: [Mailman-Developers] Merge request
In-Reply-To: <PC1922009072020402209211787696f@msapiro>
References: <PC1922009072020402209211787696f@msapiro>
Message-ID: <980D9272-9E5A-4E52-8C8D-D5C53E7F659A@python.org>

On Jul 20, 2009, at 11:40 PM, Mark Sapiro wrote:

> 1) Even though I am listed as a reviewer in the proposal, I do not
> recall getting any push notice from Launchpad about the proposal. The
> message here is in addition to proposing a merge on Launchpad, post a
> note to Mailman-Developers as you now have done.

That's odd because the Launchpad team 'mailman-coders' is the default  
review team for all three main branches (2.1, 2.2, and 3.0) and Mark  
is definitely on that team.

While I think mailman-developers should still be emailed separately,  
especially if you have a branch you really want someone to look at,  
I'll give this a try and make sure mailman-coders gets a notification.

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090721/2ce3641d/attachment.pgp>

From barry at list.org  Tue Jul 21 12:18:30 2009
From: barry at list.org (Barry Warsaw)
Date: Tue, 21 Jul 2009 06:18:30 -0400
Subject: [Mailman-Developers] Merge request
In-Reply-To: <20090720103122.13a3d544@auedv3.syscomp.de>
References: <20090720103122.13a3d544@auedv3.syscomp.de>
Message-ID: <4A3FC83D-702E-412F-ACCF-542DC361D035@list.org>

On Jul 20, 2009, at 4:31 AM, Florian Wagner wrote:

> a few weeks ago I submitted a merge request through launchpad for a
> small set of changes I've made to Mailman (see [1]). So far there has
> been no reaction at all. Is there reason for this? Are patches to this
> list preferred?

I should mention as well that I'm deliberately concentrating my time  
on getting Mailman 3 to a usable state, so I'm not spending much time  
on MM2.  Look for a new alpha release very soon now.

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090721/3e9e2eac/attachment.pgp>

From ryan at linuxbox.com  Thu Jul 30 18:15:00 2009
From: ryan at linuxbox.com (Ryan Jud Hughes)
Date: Thu, 30 Jul 2009 12:15:00 -0400 (EDT)
Subject: [Mailman-Developers] Merge requests
Message-ID: <alpine.DEB.2.00.0907301208370.10644@galaxor>

Hi.  I have done some mailman development for one of our customers.  I 
developed four separate features.  I'd like to send these features back 
upstream, and hopefully get them merged into the code base.  I'm told that 
submitting bzr merge requests is the right way to do this.

However, I'm new to bzr, so I'm not really sure how to do this.  I'm 
familiar with git, but I don't think that git has this "merge request" 
feature.

I've got the features separated into four bzr branches based off of 2.1. 
What do I do next?  bzr send?  It said there wasn't a mailto address 
listed.  Should I bzr send -o to a file and then upload that file 
somewhere?  Should I register a new branch in launchpad and then push my 
stuff there?  The box with my bzr branches is behind a nat -- is that 
going to be a problem?

If someone could point me to a FAQ or a document about submitting these 
things through launchpad, that would be great.

Thanks.
--Ryan


From mark at msapiro.net  Fri Jul 31 03:22:33 2009
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 30 Jul 2009 18:22:33 -0700
Subject: [Mailman-Developers] Merge requests
In-Reply-To: <alpine.DEB.2.00.0907301208370.10644@galaxor>
Message-ID: <PC192200907301822330140a8fddb2d@msapiro>

Ryan Jud Hughes wrote:

>Hi.  I have done some mailman development for one of our customers.  I 
>developed four separate features.  I'd like to send these features back 
>upstream, and hopefully get them merged into the code base.  I'm told that 
>submitting bzr merge requests is the right way to do this.


An actual merge proposal is a LaunchPad thing so in order to to that,
you have to push your branches to Launchpad. See
<http://wiki.list.org/display/DEV/MailmanOnLaunchpad> for more on this.


>However, I'm new to bzr, so I'm not really sure how to do this.  I'm 
>familiar with git, but I don't think that git has this "merge request" 
>feature.
>
>I've got the features separated into four bzr branches based off of 2.1. 
>What do I do next?  bzr send?  It said there wasn't a mailto address 
>listed.  Should I bzr send -o to a file and then upload that file 
>somewhere?  Should I register a new branch in launchpad and then push my 
>stuff there?  The box with my bzr branches is behind a nat -- is that 
>going to be a problem?
>
>If someone could point me to a FAQ or a document about submitting these 
>things through launchpad, that would be great.


The above wiki page should help.

You don't need to push your branches to LaunchPad in particular, but
they do need to be accessable. If they can be accessed through your
NAT by outsiders, it would be OK to just post here and give some info
on what your changes do and how to access your branches. If they
aren't accessable to outsiders where they are, pushing them to LP is
the best option.

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