Hi Michael,
I hope you've been enjoying the holidays. As you can tell, I've
managed to do the test with just the one file you uploaded and it's
shown that the conversion script works quite well. The folks at
DreamHost will take one single mbox file for the list and upload it
to the correct location in Mailman - and bingo our archives will all
be in one place back to 1996 (including Peggy's archives) - with
full search capability and no strange archive mail format codes like
you see in the raw files.
It would be great if I could get the current archives through the
end of 2010 or whatever cutoff date you want and I can go through
the files and check for gross date errors like we found in the one
file you uploaded and get ready for the transition. Then just before
the transition hopefully BSU will be able to send the rest of the
messages much more quickly so we can limit the transition period.
According to the ListServ manuals online (http://www.lsoft.com/manuals/1.8e/owner/owner.html#_Toc128536946)
there is a way to fetch the archive file by sending an email with
the "GET" command to [email protected]. But I got a
reply saying I wasn't authorized. Maybe the BSU folks would be
willing to do that for us and fetch the final email messages (and
membership list) via email rather than snail mail.
What do you think?
Cheers,
Harold
On 12/1/10 5:03 PM, Michael Herman wrote:
oh, okay, harold. that's fine. i thought your
previous message said listserv to listserv was still the better
option. i'm all for dumping it and going open source. as an
ordinary participant in this world, simply posting the 150 monthly
logs with and index/search page would be enough.
so it seems the best way to go is the mailman route. now i also
remember seeing (and trading some emails with) a guy named anthony
thompson, who's posted steps for convernting listserv to mailman.
he might be a resource for you to tap. he was very willing to
help and i don't recall there was any huge cost associated with
that help.
as for getting the log files, the total package is 277MB (as of
this morning) and 75MB if it's all zipped. logs go back monthly
to 1999. it'll have to come by pony express on a CD. right now,
i have only the one month's file, link posted in my earlier
message. can you do what you need to with that one, for testing?
or with several copies of it? if i get bsu to send a dump of the
thing now, i suppose i could get them to send the rest later. can
you do this migration in batches like that? anyway, tell me what
you think works best and i'll do it.
m
--
Michael Herman
Michael Herman Associates
http://MichaelHerman.com
http://RonanParkTrail.com
http://ManorNeighbors.com
http://ChicagoConservationCorps.org
http://OpenSpaceWorld.org
312-280-7838 (mobile)
On Wed, Dec 1, 2010 at 5:50 PM, Harold
Shinsato <[email protected]>
wrote:
Michael,
Just a few clarifications - switching to Mailman would keep
our archives as seamlessly integrated as they are now. It
would be pretty similar to a straight ListServe to ListServe
port. The advantage is that MailMan is free, has a strong
user/developer base, and we would have full control over the
webhosting - so it is less likely we would have to face this
issue again of worrying about being homeless.
For OSList - we don't really need technical support after
the port. We'd just need whatever support is getting done
now on OSList to moderate the list membership. I don't know
of any email list software that can protect you completely
from trolls and spammers without a human being involved. If
there are others willing to help with that task - it would
be straightforward to explain how to do that - even if
they're not technically oriented.
Harold
P.S. About porting archives to Mailman from Listserve - many
people have posted articles about how to do this. I'd be
interested in testing the porting process for the archives
if you'd send me a link to the zip file of the archive files
I could test the porting process and host the results so
folks could compare. As convenient as it might be just to go
from ListServe at Boise to some other benefactor, it's not
clear to me that's necessarily the best option.
On 12/1/10 2:16 PM, Michael Herman wrote:
looking back at what harold sent
earlier, it seems that the option he's proposing is one
way to go forward with a new, manageable, cost-free and
ad-free(!) conversation. the archive part is included,
but only as a separate part, meaning the new messages
won't hit the old archive. we'd have an old archive and
then start growing a new one, nearby. so the best
option is still to find another "listserv" user/customer
to host our list. harold's option, as he's noted, is a
second choice -- but i'd say it's an excellent one.
if we find another listserv host, we'll do pretty much
nothing. the old guys will send all our stuff to the
new guys, or maybe i'll be in teh middle of that, doing
very complicated things like opening the envelope,
repackaging and mailing to the new guys. if we go with
harold's solution, we'll need him and perhaps others to
do some techie things to make the archive work as an
add-on (stand beside, i think) to the new list.
as for harold's question about my continuing to support,
i am glad to help get this set up, but i'm not likely
qualified to do anything very technical. and going
forward, i'd prefer to have others step into the list
sheparding tasks (small as they might be). i have one
query out to a possible host, and if that host
materializes, then i will stay on to support that
connection. otherwise, i hope others will take this on.
m
*
*
==========================================================
[email protected]
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of [email protected]:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist
|
