Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!csd4.milw.wisc.edu!uwmcsd1!lakesys!martin From: martin@lakesys.UUCP (Martin Wiedmeyer) Newsgroups: comp.sys.atari.st Subject: netlib@lakesys Keywords: file-server UUCP netlib lakesys Message-ID: <231@lakesys.UUCP> Date: 20 Dec 88 13:59:14 GMT Organization: Lake Systems - Milwaukee, Wisconsin Lines: 85 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 Subject: Invalid message envelope information Cc: The Postmaster 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