martin@lakesys.UUCP (Martin Wiedmeyer) (08/02/88)
We at netlib@lakesys.UUCP are very happy to see that we are fufilling a need on the net for an ST file server. Traffic is growing daily and the complaints of not being reachable are diminishing. We have two requests of those who utilize netlib: 1) Please restrict yourself to no more than 5 file parts per request per day. Some have been requesting 20 or 30 file parts and it slows down the response time for others. It also strains our limited resources here. We have the capability to limit the number of file parts sent to any account per day with our software, but we'd prefer to rely upon your integrity. If there is no cooperation in this matter, then we will be forced to implement the limit in the netlib software. 2) Please be sure that you are using the correct syntax for file requests. If the file is in a volume, e.g. volume1. The volume # MUST be specified as part of the pathname for the file part in your request. Also be sure to put "from archives.atari" at the end of every file part in your request, otherwise the line is not parsed correctly and your request subsequently fails. Thank you to all those who have been contributing to our archives, you have helped to make the netlib file server one of the best. We appreciate your cooperation. Marty Wiedmeyer martin@lakesys.UUCP -- | Marty Wiedmeyer | | Lake Systems, Milwaukee, WI | | UUCP: uwvax!uwmcsd1!lakesys!martin | | Disclaimer: I take the heat for my own (mis)statements..... |
martin@lakesys.UUCP (Martin Wiedmeyer) (12/20/88)
Hello everyone! lakesys is back to normal & now we're working on the netlib software. When all is ready I will post to this newsgroup. NETLIB IS NOT AVAILABLE YET. For now I'm answering mail to netlib by hand. A number of requests still show up every day. PLEASE be patient. I have been receiving a number of requests from the Continent which have julian in their bang path. When they get here they have mangled addressses & when I reply *every* one gets bounced back from the site in Toronto. See below for details.... Hopefully netlib will be better than before when it is functional once again. Marty Wiedmeyer uunet!marque!lakesys!martin uwvax!uwmcsd1!lakesys!martin ================== This is a condensation of a number of mail error messages which I have received in the past month. They are really the *only* ones I got, everything else seems to have gone through OK. They were generated by my replies to requests for files from netlib. ================== From marque!uunet!utai!postmaster Fri Dec 9 10:18:26 1988 Received: by lakesys.UUCP (smail2.5) id AA00121; 9 Dec 88 10:18:26 CST (Fri) Received: by marque.mu.edu (smail2.5) id AA06439; 9 Dec 88 10:20:45 EST (Fri) Received: from utai.UUCP by uunet.UU.NET (5.59/1.14) with UUCP id AA12992; Fri, 9 Dec 88 08:12:56 EST Received: by neat.ai.toronto.edu id 6363; Fri, 9 Dec 88 06:52:55 EST To: marque!lakesys!martin From: The Post Office <uunet!ai.toronto.edu!postmaster> Subject: Invalid message envelope information Cc: The Postmaster <postmaster@ai.toronto.edu> Message-Id: <88Dec9.065255est.6363@neat.ai.toronto.edu> Date: Fri, 9 Dec 88 06:52:09 EST The following message arrived with illegal envelope data, typically a mangled address that doesn't obey the RFC822/976 protocol specification. If you do not recognize the source of the bad header, perhaps you should ask a postmaster at your site, or even the postmaster here if your postmaster can't figure out why the mail was rejected. The following annotated envelope headers illustrate the error(s): Error in "To" envelope address: mletzko@julian!ds0mpa51.bitnet ^-missing end of address Error in "To" envelope address: WUNSCH@julian!CERNVM.BITNET ^-missing end of address Error in "To" envelope address: OR916@julian!DBNUOR1.BITNET ^-missing end of address Error in "To" envelope address: VOERG@julian!DHDIHEP1.BITNET ^-missing end of address Error in "To" envelope address: GERHARD@julian!DBNUAMA1.BITNET ^-missing end of address Error in "To" envelope address: mletzko@julian!ds0mpa51.bitnet ^-missing end of address