At 1:43 AM -0500 12/9/06, John A. Martin wrote:
Oops. The first sentence of mine above was intended to end with a
question mark rather than an exclamation mark. Maybe that would have
sounded better.
That would have been somewhat better, yes.
Brad I didn't say that Debian did. Alan
At 3:16 PM +0900 12/9/06, Stephen J. Turnbull wrote:
The mailman package did install a
complete Mailman on several Debian systems where I use Mailman.
Understood. At least, now I do.
The problem is that the conversation I had with Alan up to that point
had
Brad Knowles wrote:
The problem is that the conversation I had with Alan up to that point
had lead me to believe that we were talking about a standard Mailman
installation as provided in package format by Debian, and yet Alan's
configuration clearly lacked what I consider to be a pretty
On Thu, Dec 07, 2006 at 06:04:55PM -0500, Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 7, 2006, at 5:22 PM, Paul Tomblin wrote:
I've just spent two days manipulating a bunch of mbox files into
archives.
Let me tell you how it goes:
[Screams of pain
On Thu, Dec 07, 2006 at 06:23:40PM -0600, Brad Knowles wrote:
At 4:57 PM -0500 12/7/06, Alan McConnell wrote:
Meanwhile, I am adminning(sp?), through my ISP, a new but quite active
E-list. But their mailman install is incomplete; they haven't put in
Pipermail(about which I know
At 7:52 AM -0500 12/8/06, Alan McConnell quoted me:
Uh, what version of Mailman is that? I thought that Mailman had
fully integrated Pipermail along with the base code, for many years
now? Are they running Mailman 1.x or something?
mm 2.1.5 . But under Debian, so it has
On Thu, 7 Dec 2006, Barry Warsaw wrote:
Have I mentioned recently how long I've been looking for a volunteer
to help make all this not suck? ;} Pipermail is just one of those
things that people either live with or ditch.
I've used Hypermail for probably a decade to archive Majordomo
Mark Sapiro wrote:
Paul Tomblin wrote:
Quoting Barry Warsaw ([EMAIL PROTECTED]):
It already does escape From lines in the body of the message. It
does this by way of the email package's Generator class, which is
instantiated with mangle_from_=True.
Must be a newer version than the one in
Quoting Todd Zullinger ([EMAIL PROTECTED]):
Mark Sapiro wrote:
Paul Tomblin wrote:
Quoting Barry Warsaw ([EMAIL PROTECTED]):
It already does escape From lines in the body of the message. It
does this by way of the email package's Generator class, which is
instantiated with
Brad == Brad Knowles
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 08:52:26 -0600
Brad At 7:52 AM -0500 12/8/06, Alan McConnell quoted me:
Uh, what version of Mailman is that? I thought that Mailman
had fully integrated Pipermail along
Paul Tomblin wrote:
Oh right, now I get it. I told you I didn't know Python, but I
should have been able to figure that
def __init__(self, outfp, mangle_from_=True, maxheaderlen=78):
meant that it defaulted to True in Generator.py so didn't need to be
changed in Mailman.
:-)
I actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 8, 2006, at 11:10 AM, Paul Tomblin wrote:
In that case, shouldn't any message that reaches mailman with an
unescaped From_ line in the body already be handled properly? It
seems like something else must be borked. That or all of the
Brad Knowles wrote:
At 7:52 AM -0500 12/8/06, Alan McConnell quoted me:
Uh, what version of Mailman is that? I thought that Mailman had
fully integrated Pipermail along with the base code, for many years
now? Are they running Mailman 1.x or something?
mm 2.1.5 . But under Debian,
At 11:43 AM -0500 12/8/06, John A. Martin wrote:
See http://packages.debian.org/unstable/mail/mailman for a
description of the Debian Mailman package that integrates
archiving Further down that page under the heading
Download mailman click on one of the list of files buttons
Quoting Brad Knowles ([EMAIL PROTECTED]):
At 11:43 AM -0500 12/8/06, John A. Martin wrote:
See http://packages.debian.org/unstable/mail/mailman for a
description of the Debian Mailman package that integrates
archiving Further down that page under the heading
Download
Paul == Paul Tomblin
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 20:04:51 -0500
Alan == Alan McConnell
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 07:52:33 -0500
Paul Quoting Brad Knowles ([EMAIL PROTECTED
At 10:17 PM -0500 12/8/06, John A. Martin wrote:
I've never claimed to be a Debian expert, and if they're
mucking about with packages that include certain features by
default in order to remove those features,
What makes you, Brad, think that Debian removes pipermail when
Brad Knowles writes:
I've never claimed to be a Debian expert, and if they're mucking
about with packages that include certain features by default in order
to remove those features, then there's not much I can do to help the
poor souls that are stuck with that kind of stuff.
That's
Brad == Brad Knowles
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 22:28:19 -0600
Brad At 10:17 PM -0500 12/8/06, John A. Martin wrote:
I've never claimed to be a Debian expert, and if they're
mucking about with packages that include
Kory Wheatley wrote:
I'm running Mailman 2.1.6 is there a script you can run to automatically
remove all archive messages from a list?
I'm not sure what you mean by automatically.
You can remove all messages from a list's pipermail archive by
bin/arch --wipe listname /dev/null
--
Mark
Quoting Mark Sapiro ([EMAIL PROTECTED]):
Kory Wheatley wrote:
I'm running Mailman 2.1.6 is there a script you can run to automatically
remove all archive messages from a list?
I'm not sure what you mean by automatically.
You can remove all messages from a list's pipermail archive by
Paul Tomblin wrote:
Quoting Mark Sapiro ([EMAIL PROTECTED]):
[...]
You can remove all messages from a list's pipermail archive by
bin/arch --wipe listname /dev/null
What, rm -rf not good enough for you?
:-)
You do have to know the location of the list archives with rm whereas
with
At 3:37 PM -0500 12/7/06, Todd Zullinger wrote:
You do have to know the location of the list archives with rm whereas
with bin/arch you don't. And if you put a typo into bin/arch it can
at worst wipe out the archives of the wrong list, not large chunks of
your file system.
Everyone
Quoting Brad Knowles ([EMAIL PROTECTED]):
Tools like bin/arch are much safer, albeit also slower.
I've lost more files to badly written programs than to PEBKAC errors. So
I'd be more inclined to trust rm than arch.
--
Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/
This also tells they
Brad Knowles wrote:
Everyone raise your hand if you have accidentally done the command:
# rm -rf / path/to/file/structure/you/really/want/to/delete
Or
rm -rf /path/to/somethingstar
and typed it
rm -rf /path/to/something star
Those pesky spaces - always raising havoc...
And that
Paul Tomblin wrote:
I've lost more files to badly written programs than to PEBKAC errors. So
I'd be more inclined to trust rm than arch.
This thread is fun, but just to be clear, I responded the way I did to
the OP because the OP was not at all clear about what was wanted, so I
gave an answer
On Thu, Dec 07, 2006 at 03:37:41PM -0500, Todd Zullinger wrote:
What, rm -rf not good enough for you?
G Yeah, yeah.
Meanwhile, I am adminning(sp?), through my ISP, a new but quite active
E-list. But their mailman install is incomplete; they haven't put in
Pipermail(about which I know
I just checked my blog, and found I message a step:
Quoting Paul Tomblin ([EMAIL PROTECTED]):
I've just spent two days manipulating a bunch of mbox files into archives.
Let me tell you how it goes:
1. Blow away the html archives. You may prefer to use that arch command
we were just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 7, 2006, at 5:22 PM, Paul Tomblin wrote:
I've just spent two days manipulating a bunch of mbox files into
archives.
Let me tell you how it goes:
[Screams of pain omitted]
Have I mentioned recently how long I've been looking for a
Quoting Paul Tomblin ([EMAIL PROTECTED]):
8. Discover that the mbox file had a bunch of un-escaped From lines
that confused bin/arch and so you have a bunch of half-articles in today's
archive page that shouldn't be there. Run bin/cleanarch to fix them, blow
away the html archives, and then
Quoting Barry Warsaw ([EMAIL PROTECTED]):
[Screams of pain omitted]
Have I mentioned recently how long I've been looking for a volunteer
to help make all this not suck? ;} Pipermail is just one of those
things that people either live with or ditch.
I suppose it would be a good excuse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 7, 2006, at 6:35 PM, Paul Tomblin wrote:
Quoting Paul Tomblin ([EMAIL PROTECTED]):
8. Discover that the mbox file had a bunch of un-escaped From
lines
that confused bin/arch and so you have a bunch of half-articles in
today's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 7, 2006, at 6:37 PM, Paul Tomblin wrote:
Quoting Barry Warsaw ([EMAIL PROTECTED]):
[Screams of pain omitted]
Have I mentioned recently how long I've been looking for a volunteer
to help make all this not suck? ;} Pipermail is just one
At 4:57 PM -0500 12/7/06, Alan McConnell wrote:
Meanwhile, I am adminning(sp?), through my ISP, a new but quite active
E-list. But their mailman install is incomplete; they haven't put in
Pipermail(about which I know _nothing_).
Uh, what version of Mailman is that? I thought that Mailman
At 5:22 PM -0500 12/7/06, Paul Tomblin wrote:
6. Discover an awk script in the mailman archives that will split the mbox
archive into managable chunks. Fix it so that it splits them into 500
message chunks instead of the 80 message chunks it defaults to.
There's also the formmail tool
Quoting Barry Warsaw ([EMAIL PROTECTED]):
On Dec 7, 2006, at 6:35 PM, Paul Tomblin wrote:
Speaking of which, is there any way to modify Mailman so that when it
puts a mail message in the mbox, it pre-escapes the ^From lines in
the message? Mailman knows the message boundaries at that point,
Paul Tomblin wrote:
Quoting Barry Warsaw ([EMAIL PROTECTED]):
It already does escape From lines in the body of the message. It
does this by way of the email package's Generator class, which is
instantiated with mangle_from_=True.
Must be a newer version than the one in Debian stable.
I'm running Mailman 2.1.6 is there a script you can run to automatically
remove all archive messages from a list?
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ:
38 matches
Mail list logo
