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. <br>
<br>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.<br>
<br>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.<br>
<br>m<br><br clear="all"> <br>--<br><br>Michael Herman<br>Michael Herman Associates<br><br><a href="http://MichaelHerman.com">http://MichaelHerman.com</a><br><a href="http://RonanParkTrail.com">http://RonanParkTrail.com</a><br>
<a href="http://ManorNeighbors.com">http://ManorNeighbors.com</a><br><a href="http://ChicagoConservationCorps.org">http://ChicagoConservationCorps.org</a><br><a href="http://OpenSpaceWorld.org">http://OpenSpaceWorld.org</a><br>
<br>312-280-7838 (mobile)<br>
<br><br><div class="gmail_quote">On Wed, Dec 1, 2010 at 5:50 PM, Harold Shinsato <span dir="ltr"><<a href="mailto:harold@shinsato.com">harold@shinsato.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Michael,<br>
<br>
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.<br>
<br>
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.<br><font color="#888888">
<br>
Harold<br>
</font><br>
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.<div class="im"><br>
<br>
<br>
On 12/1/10 2:16 PM, Michael Herman wrote:
<blockquote type="cite">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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
m<br>
</blockquote>
<br>
<br>
</div><div>-- <br><div class="im">
Harold Shinsato<br>
<a href="mailto:harold@shinsato.com" target="_blank">harold@shinsato.com</a><br>
<a href="http://shinsato.com" target="_blank">http://shinsato.com</a><br>
twitter: <a href="http://twitter.com/hajush" target="_blank">@hajush</a></div></div>
</div>
</blockquote></div><br>
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist