Hi David,
First, you should reply to all, including the mailman list, because I do
not have the answer.
I explained in a previous mail what I'd do : I'd write shell (/bin/sh)
scripts to :
- get the lists of list, and for each list get the subscribers (using
$prefix/bin/* utils), from the
Hello,
I suggested this solution because :
- they had the same problem with mailman after upgrading (and not
reinstalling with a newer version)
- personnally, I don't really like upgrades, and I ususally prefer to
reinstall from scratch. Some experiences (and this one ?) show that
When I upgraded from 2.0.1 to 2.0.2 (I think those were the versions),
the install found my lists and upgraded them (including the html
associated with the templates).
Kinda painless...
Steve
--
Steve Pirk
[EMAIL PROTECTED] . deathcon.com . pirk.com . webops.com . t2servers.com
On Wed, 18 Apr
On Wed, 18 Apr 2001, josh koenig wrote:
>
> Yeah... I could see how this would work.
Nice !
> A sort of failsafe backup/migration system.
Yes.
> I think I can puzzle out how to get all the data
> out manually, but any such script you write would be more than welcome by
> me. I'm not experien
Yeah... I could see how this would work. A sort of failsafe
backup/migration system. I think I can puzzle out how to get all the data
out manually, but any such script you write would be more than welcome by
me. I'm not experienced with python.
> I have no scripts (yet) do to that, but my idea i
On Wed, 18 Apr 2001, josh koenig wrote:
> > Did you try to install Mailman 2.0.3 from scratch ? I'm a new user of
> > mailman, and everything is OK for me with it, no problems at the moment.
> >
> > With a few scripts, you'll be able to keep you lists&archives from your
> > "old" installation.
On Wed, 18 Apr 2001, Philippe Rodriguez wrote:
>
> Did you try to install Mailman 2.0.3 from scratch ? I'm a new user of
> mailman, and everything is OK for me with it, no problems at the moment.
Actually, no. I upgraded from 2.0.1 if I'm not mistaken. My only
worry about reinstalli
> Did you try to install Mailman 2.0.3 from scratch ? I'm a new user of
> mailman, and everything is OK for me with it, no problems at the moment.
>
> With a few scripts, you'll be able to keep you lists&archives from your
> "old" installation.
By this do you mean with a few extra shell script
Did you try to install Mailman 2.0.3 from scratch ? I'm a new user of
mailman, and everything is OK for me with it, no problems at the moment.
With a few scripts, you'll be able to keep you lists&archives from your
"old" installation.
I usually do not like "upgrade" options. Is the mailman on
> "jk" == josh koenig <[EMAIL PROTECTED]> writes:
jk> That's what's so baffling.
Indeed!
jk> The apache error log gives me the useless "premature end of
jk> script headers" and nothing comes up in the mailman or
jk> syslogs. I'll keep looking, though
Okay, thanks.
> jk> First of all, whenever I try to use /admin/listname I get a
> jk> generic 500 script error. The web log reports "premature end
> jk> of script headers" I know this isn't a permissions problem as
> jk> check_perms gives me an all clear.
>
> Are you using Apache? Do you see n
> "jk" == josh koenig <[EMAIL PROTECTED]> writes:
jk> First of all, whenever I try to use /admin/listname I get a
jk> generic 500 script error. The web log reports "premature end
jk> of script headers" I know this isn't a permissions problem as
jk> check_perms gives me an all
I was about to compose an email about the very same thing. I've
been fighting with the Admin part of the interface for a few weeks now. I
can get in to see the emails that are pending approval, but at the bottom
of that same page, there is usually the "We're sorry, we've hit a bug!".
Aft
Hi, I've been using Mailman with some success for a while, but I've just
started having some serious problems with admin functions after upgrading
to version 2.0.3
First of all, whenever I try to use /admin/listname I get a generic 500
script error. The web log reports "premature end of script h
14 matches
Mail list logo