Dan Mick wrote:

Gian Franco Baroni wrote:

...

...

...

...

Dan Mick <dmick@utopia.West.Sun.COM> 16/04/02 19.31.31 >>> Yes, first, ask on mailman-users. Sorry, I sent the mail to wrong list... Shame on me :(

Well, probably not, if you're using 2.1a4. I should have asked.

...

...

...

Second, see FAQ entry 1.8. Read, but I'm using 2.1a4 and I'm not sure if all the hints cover that version.

Except for 2.1-latest's penchant for saving messages as pickles, rather than plain text. But you can turn that off with a switch inside the module, whose name I forget right at the moment. Barry, given that people seem to often want to edit these messages, is it really a good idea to save them as non-plain-text?

Argh. This had nothing to do with Gian Franco's question, but it's still a valid concern.

For the question of HTML stripping, I think Mailman 2.1 only provides "archive stripping" by default. I use, and am happy with, demime.

At 01:21 PM 4/19/02 -0700, Dan Mick wrote:

Except for 2.1-latest's penchant for saving messages as pickles, rather than plain text. But you can turn that off with a switch inside the module, whose name I forget right at the moment. Barry, given that people seem to often want to edit these messages, is it really a good idea to save them as non-plain-text?

I had the same thought when debugging the topic parser problem - that it'd be nice to be able to pick through the message without having to decode the pickle's wrappings.

Although rather than saving them as plaintext, I'd be just as happy with an unpickle/repickle util for when I want to monkey with a message. (if only to let me read it without swearing at it...)

At 05:28 PM 4/19/02 -0400, Barry A. Warsaw wrote:

bin/dumpdb knows how to print out the plaintext representation of a .pck message file, so

% bin/dumpdb qfiles/in/...pck > msg.txt

ought to do the trick. The other direction is fairly easy if you don't mind not saving the message metadata file (.db). Use bin/inject, possibly with the -q option.

And, you know, I actually knew that at the time, and now that you've mentioned it again, realize I actually did that eventually...

Although I hadn't thought about using inject to shove it back in.

...

...

...

...

"DM" == Dan Mick <dmick@utopia.west.sun.com> writes:

DM> Except for 2.1-latest's penchant for saving messages as
DM> pickles, rather than plain text.  But you can turn that off
DM> with a switch inside the module, whose name I forget right at
DM> the moment.  Barry, given that people seem to often want to
DM> edit these messages, is it really a good idea to save them as
DM> non-plain-text?

It may not be. Then again, maybe I should promote the variable up into Defaults.py.in, regardless of the default value. It would be easier to modify through mm_cfg.py than to hack on ListAdmin.py and potentially lose your changes when you upgrade.

-Barry