[Mailman-Users] Mailman-Users Digest, Vol 38, Issue 18

Ray westerpark at fastmail.fm
Tue Apr 10 13:04:41 CEST 2007


On Tue, 10 Apr 2007 12:00:09 +0200, mailman-users-request at python.org
said:
> Send Mailman-Users mailing list submissions to
> 	mailman-users at python.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mail.python.org/mailman/listinfo/mailman-users
> or, via email, send a message with subject or body 'help' to
> 	mailman-users-request at python.org
> 
> You can reach the person managing the list at
> 	mailman-users-owner at python.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mailman-Users digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Mailman web interface does not save changes (Brad Knowles)
>    2. Re: content filtering problem (Rick Pasotto)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 9 Apr 2007 20:29:35 -0500
> From: Brad Knowles <brad at shub-internet.org>
> Subject: Re: [Mailman-Users] Mailman web interface does not save
> 	changes
> To: Fernando Barros <fernando.barros at sipam.gov.br>,
> 	mailman-users at python.org
> Message-ID: <p06240502c24098c4dd3d@[192.168.132.163]>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
> 
> At 11:03 AM -0300 4/9/07, Fernando Barros wrote:
> 
> >  I've search Mailman FAQ and find a related issue
> >  (http://www.python.org/cgi-bin/faqw-mm.py?req=all#4.45) which points
> >  that the access to the site via redirect is tossing away the POST
> >  changes. The workaround would be to capture the POST data from the
> >  original request, convert it to a GET and redirect to that.
> >
> >  Can anybody show me how to configure that ?
> 
> You don't.  You eliminate the redirect instead.
> 
> See all the other FAQ entries and linked archive articles from the 
> mailman-users list.
> 
> -- 
> Brad Knowles <brad at shub-internet.org>, Consultant & Author
> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 9 Apr 2007 22:11:05 -0400
> From: Rick Pasotto <rick at niof.net>
> Subject: Re: [Mailman-Users] content filtering problem
> To: mailman-users at python.org
> Message-ID: <20070410021105.GB5169 at niof.net>
> Content-Type: text/plain; charset=us-ascii
> 
> On Mon, Apr 09, 2007 at 05:24:13PM -0700, Mark Sapiro wrote:
> > Rick Pasotto wrote:
> > 
> > >Today I received a message that had been rejected by the content
> > >filtering system and I'm not sure why. The sections of the message were:
> > >
> > > I  1 <no description>                 [text/plain, 7bit, us-ascii, 0.2K]
> > > I  2 Toastmaster Meeting for Tmrw            [message/rfc822, 7bit, 26K]
> > > I  3   ><no description>                    [multipa/related, 7bit, 24K]
> > > I  4     ><no description>              [multipa/alternativ, 7bit, 3.7K]
> > > I  5       ><no description>        [text/plain, quoted, us-ascii, 0.5K]
> > > I  6       ><no description>         [text/html, quoted, us-ascii, 2.9K]
> > > I  7     >NewCiscoLogo.jpg                     [image/jpeg, base64, 20K]
> > >
> > >In the pass_mime_types I have:
> > >
> > >multipart/mixed
> > >multipart/alternative
> > >text/plain
> > >
> > >Was the message rejected because the text/plain was quoted?
> > 
> > No.
> > 
> > You have two problems.
> > 
> > What is the overall message type in the main message headers? I suspect
> > it was not multipart/mixed or multipart/alternative; possibly
> > multipart/related or some such which would cause all of its sub-parts
> > to be skipped because multipart/whatever is not accepted.
> 
> I can see that I was insufficiently clear. What I posted above is the
> sections of the reject message that Mailman sent me. The
> 'message/rfc822' appears to be Mailman's encapsulation of the original
> message. From your explanation I see that the problem was that the
> original message was 'multipart/related'.
> 
> > Further, even if the main message is multipart/mixed, you don't accept
> > the message/rfc822 part so the only thing left would be the initial
> > 0.2K text/plain part.
> > 
> > You need to accept every multipart/ type that could possibly contain a
> > sub-part of interest. A better choice for pass_mime_types is
> > 
> > multipart
> > message/rfc822
> > text/plain
> > 
> > In your example above, this would pass all the multipart types
> > regardless of sub-type as well as the message/rfc822 part. This
> > doesn't mean the entire message will be passed. It just means that the
> > various sub-parts of those parts will be examined and the text/plain
> > parts accepted.
> > 
> > Even though the above seems very liberal, it ultimately only accepts
> > text/plain and elemental message/rfc822 parts, in this case only the
> > two text/plain parts.
> 
> Excellent. This is what I want. Thanks.
> 
> -- 
> "Only one thing can conquer war - that attitude of mind which can see
>  nothing in war but destruction and annihilation" -- Ludwig von Mises
>     Rick Pasotto    rick at niof.net    http://www.niof.net
> 
> 
> ------------------------------
> 
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users at python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> 
> End of Mailman-Users Digest, Vol 38, Issue 18
> *********************************************

-- 
  Ray
  westerpark at fastmail.fm



More information about the Mailman-Users mailing list