allbery@ncoast.UUCP (Brandon Allbery) (01/17/88)
[We haven't seen the line-eater since we sent Minnifield and Dixon after it!] [This is redirected to news.sysadmin in case anyone wants to respond. ++bsa] As quoted from <12948@necntc.NEC.COM> by jeff@necntc.NEC.COM (Jeff Janock): +--------------- | In article <7072@ncoast.UUCP> allbery@ncoast.UUCP (Brandon S. Allbery) writes: | > WARNING!!! Site "necntc" apparently is no longer a mail feed for ncoast! | | I take this quip as a minor blow to necntc's reputation :-) | | necntc has been providing ncoast with reliable email service as well | as an east coast distribution point for comp.sources.misc for some time. +--------------- Okay, I thought you had lost patience with the mailing lists. TO ALL SITES SENDING MAILING LIST TRAFFIC TO NCOAST VIA NECNTC: I have sent mail to as many of you as possible, but I'm not sure it got through in all cases, so... When I signed ncoast up for various mailing lists, the ncoast!necntc link did not exist. When it came into existence, most of the mailing lists immediately rerouted themselves (via smail, I assume) through necntc. Please note that the necntc link is NOT intended for high volume mail! The link will be severed if the mail volume gets too large -- which it has in the case of some mailing lists. To summarize: Please do NOT use smail/pathalias routing data to send to ncoast via a mailing list! The proper link for high volume mail is the path cbosgd!mandrill!hal!ncoast Do NOT use the other links (necntc, mandrill, uccba, hnsurg3, hoptoad, or the direct cbosgd connection)! None of these sites wishes to carry a high volume of mail traffic to ncoast. Thank you for your compliance with these guidelines. -- Brandon S. Allbery, moderator of comp.sources.misc {well!hoptoad,uunet!hnsurg3,cbosgd,sun!mandrill}!ncoast!allbery PS/2: Half a computer. OS/2: Half an operating system for half a computer. ------------------------------------------------------------------------------- ATTENTION!! Please do not send mail to ncoast through necntc. This applies to all mailing lists and all mail not directed to comp.sources.misc. Thank you. (This message provided by myself and Jeff Janock <necntc!jj>.)
mason@tmsoft.UUCP (Dave Mason) (01/19/88)
In article <7088@ncoast.UUCP> allbery@ncoast.UUCP writes: >... >Please note that the necntc link is NOT intended for high volume mail! The >link will be severed if the mail volume gets too large -- which it has in the >case of some mailing lists. >... > >To summarize: Please do NOT use smail/pathalias routing data to send to >ncoast via a mailing list! The proper link for high volume mail is the path > > cbosgd!mandrill!hal!ncoast Well then, change the PUBLISHED map information to show necntc<-->ncoast as expensive, and no one (or at least no smart mailer) WILL use it. Your private (Path.local) can show the real info for low traffic transfers. It is unreasonable to expect people to hard code paths when the map gets as large as it is now, and changes from week to week. Fudge the data to get the results you want :-). In our local area this is quite a popular game. Site x notices a lot of traffic going over a fast long distance link, so changes the map entry.... lo and behold, next week all the traffic has switched to site y, so they change their map entry.... great fun :-) ../Dave
jeff@necntc.nec.com (Jeff Janock) (01/21/88)
In article <268@tmsoft.UUCP> mason@tmsoft.UUCP (Dave Mason) writes: > >Well then, change the PUBLISHED map information to show >necntc<-->ncoast as expensive, and no one (or at least no smart mailer) >WILL use it. Your private (Path.local) can show the real info for low >traffic transfers. It is unreasonable to expect people to hard code >paths when the map gets as large as it is now, and changes from week >to week. Fudge the data to get the results you want :-). > >In our local area this is quite a popular game. Site x notices a lot >of traffic going over a fast long distance link, so changes the map >entry.... lo and behold, next week all the traffic has switched to >site y, so they change their map entry.... great fun :-) > ../Dave This is an interesting observation - I would like to point out in this case, necntc made the ncoast cost WEEKLY*8 for a period of time - email still flowed to ncoast via necntc, but only when hardcoded to do so... The changes made to the path database was also interesting as routing changed as expected! Keeping a Path.Local is also a good idea as link info changes rather dramically sometimes and the admins of each site know best what is happening to the neighboring sites (most of the time :-) Map updates now can go out quite swiftly, so admins should not hesitate to update their map entries WHENEVER needed... -jj -- Jeff Janock - UUCP Project New England Map Coordinator {decvax,harvard,mit-eddie,linus,adelie, etc}!necntc!nemap