mml@srhqla.UUCP (Michael Levin) (05/16/89)
Since this group seems well underway, and the access has begun to be a problem for NON-Usenet sites, it seems appropriate to post some suggested ways to provide these sites with the ability to receive articles via e-mail. Here, then, are my suggestions: 1). For OUTBOUND copying (gateway'ing) a non-Usenet site with all articles posted to this group, said non-Usenet sites (fooo) should contact the SA's at adjacent (Usenet) sites, and request that the SA's add the following entry to their 'sys' file: fooo:world,na,usa,ca,la,!ca.all,!la.all,comp.mail.mush::mail logname@fooo ^^^^ ^^ ^^^ ^^ ^^ ^^^^^^ ^^^^^^ ^^^^^^^^^^^^ | | | | | | | | | | | | | | | | 1 2 3 4 5 6 7 8 1- The name of the non-Usenet site who wishes to be copied. 2- Continent part of sys file entries. Here in North America (na), we have to make sure that we pass news that is grouped for distribution in North America. 3- Country. Same idea as (2) above. 4- State. The only thing is that there is both statewide distribution, which is what field 4 here refers to, but there is also a seperate heirarchy of news groups such as 'ca.wanted', etc. Because of this, it is necessary to PASS through 'ca' distribution, but to SUPPRESS the 'ca.foo' heirarchy. 5- Local. Same ideas as (4) above. 6- Suppress state heirarchy; see (4) above. 7- Suppress local heirarchy; see (4) above. 8- Email address of the person to send the 'comp.mail.mush' stuff. This is VERY EASY for any usenet site to accomplish. Furthermore, if MIT.EDU (the site which presently does all the forwarding) wanted to, they could simply create the entry to email to the list, and then all the distribution could continue from there. NO PROBLEM. 2). Gatewaying INBOUND mush-users stuff to Usenet. This one is a bit trickier, but still no big deal. There is a standard utility which comes with the B-news distribution called "recnews", which takes inbound mail (usually sent to an alias) and packs it up into an article, and posts it to a group. I would once again recommend that garp.MIT.EDU be the clearing point for this, although if folks are going to go to more local Usenet sites for the OUTBOUND forwarding, it might be more logical to have them also handle the INBOUND. If the site getting the INBOUND stuff has sendmail, it's VERY simple. If anybody has any comments, or suggestions, please: 1). If it is non-general, email me directly. 2). If it is a general question or comment, please post it to comp.mail.mush, so that it can get the benefit of a whole bunch of folks out there knowing about it. Mike Levin -- _ _ | | ___ ___ |_| ___ Michael Levin SilentRadio Headquarters- Los Angeles | |/ ._\| | || || \ 20732 Lassen Street, Chatsworth CA 91311 U.S.A. |_|\___/ \_/ |_||_|_| {pacbell|pyramid|csun}!srhqla!levin - levin@srhqla.UUCP
sewilco@datapg.MN.ORG (Scot E Wilcoxon) (05/16/89)
In article <614@srhqla.UUCP> mml@srhqla.UUCP (Michael Levin) writes: > 1). For OUTBOUND copying (gateway'ing) a non-Usenet site with all > articles posted to this group, said non-Usenet sites (fooo) should > contact the SA's at adjacent (Usenet) sites, and request that the SA's > add the following entry to their 'sys' file: > >fooo:world,na,usa,ca,la,!ca.all,!la.all,comp.mail.mush::mail logname@fooo If mail cannot be delivered to logname@fooo it may be bounced to the poster of the article. Not all comp.mail.mush writers should get their articles echoing back to them. -- Scot E. Wilcoxon sewilco@DataPg.MN.ORG {amdahl|hpda}!bungia!datapg!sewilco Data Progress UNIX masts & rigging +1 612-825-2607 uunet!datapg!sewilco I'm just reversing entropy while waiting for the Big Crunch.