Hi,
Barry Warsaw wrote:
On Fri, 2005-07-01 at 20:04, Mark Sapiro wrote:
2). I'm not a Mailman developer, and I can't speak for anyone's intent,
but a patch which makes the above conditional on a new list attribute,
updates Mailman/Gui/ContentFilter.py to maintain and document the new
On Mon, 2005-07-11 at 03:55, Tokio Kikuchi wrote:
I'm going to do this as a part of my lecture (Anatomy of Mailman) for
our MS course students tommorow. :-)
Please be kind to our little chimera! There's plenty of nasty gore and
goo when you open up the patient, and it's had many many parents.
On Sun, 3 Jul 2005 17:48:37 -0400 (EDT) Michael Dunlap [EMAIL PROTECTED]
wrote:
Thanks - commenting out those lines did the trick and will make my clients
happy.
Developers- what was the reason for this behavior? I don't believe this
was an arbitrary decision, so what unwanted events is it
On Fri, 2005-07-01 at 20:04, Mark Sapiro wrote:
2). I'm not a Mailman developer, and I can't speak for anyone's intent,
but a patch which makes the above conditional on a new list attribute,
updates Mailman/Gui/ContentFilter.py to maintain and document the new
attribute and updates
On Mon, 2005-07-04 at 04:59, Brad Knowles wrote:
So far, the code has focused on doing just the simple things like
stripping specific bodypart types and converting HTML to plaintext.
So far as I know, no one has attempted to generalize this process.
Without any firm evidence to back
At 5:48 PM -0400 2005-07-03, Michael Dunlap wrote:
Developers- what was the reason for this behavior? I don't believe this
was an arbitrary decision, so what unwanted events is it designed to
prevent?
Features such as converting HTML to plain text, and stripping
various bodypart
Thanks - commenting out those lines did the trick and will make my clients
happy.
Developers- what was the reason for this behavior? I don't believe this
was an arbitrary decision, so what unwanted events is it designed to
prevent?
Michael
Michael Dunlap Systems Programmer
Michael Dunlap wrote:
I've been reading the archives and it looks as if the problem of having
content filtering on and passing multi-part emails (plain and html)
isn't really solvable. One email to the users list summarizes the
problem this way:
There is a basic design decision in content
