Mike explains: |> ...if it ever arrives at all. oh - guess I live a sheltered life. Here inside SGI, usenet news group are very reliable. |> By private, I don't mean restricted, of course. |> It's still publicly available, but it isn't connected to USENET. ah - then how about we have a dedicated server, just for the zope group, but keep it in the usenet hierarchy, so that some other portion of the universe (apparently not including yourself ') that has reliable usenet feeds will gain greater and more convenient access to that same group. This could include the "dual news/list solution" that I see Alexander Staubo suggesting in another response. I'm fine with such, so long as someone else does the work. Such dual solutions are certainly _heavily_ used inside SGI, where I work. |> If you're really eager to get a comp.sys.zope, great ... Ah -- there's a key point. My going off and getting a comp.*.zope accepted would be a useless waste of time (or worse - some sort of information pollution) unless the Zope masters (likely starting with someone from Digital Creations, such as Paul Everitt, Michel Pelletier, Jim Fulton, Brian Lloyd, Rob Page or Ken Manheimer, based on how often I see their names in my email archive) backs this, and a Zope community concensus forms to motivate the shift from the email list to the news group for most activity. Otherwise, I'm just pissing in the wind. (And not "comp.sys.zope", I hope. "comp.sys" seems to be for computer system (sw+hw) vendors, not web server software). ======================================================================= I won't rest till it's the best ... Software Production Engineer Paul Jackson (pj@sgi.com; pj@usa.net) 3x1373 http://sam.engr.sgi.com/pj