anderson@uwmacc.UUCP (12/11/86)
A number of correspondents are telling me their e-mail is being returned to them by a daemon at ihnp4, with words to the effect that ihnp4 cannot contact uwvax. The problem has arisen within the past few days, as near as I can tell. uwvax is directly connected to seismo, as I understand it, which may present the best alternative. I've added "(avoid ihnp4)" to my signature file, which was otherwise as you see it here. As I am not expert in UUCP matters, I have no idea what's happening or what would be the most effective remedy. E-mailed suggestions would be welcome. Thanks. -- ==ARPA:====================anderson@unix.macc.wisc.edu===Jess Anderson====== | UUCP: {harvard,seismo,topaz, (avoid ihnp4!) 1210 W. Dayton | | akgua,allegra,usbvax}!uwvax!uwmacc!anderson Madison, WI 53706 | ==BITNET:============================anderson@wiscmacc===608/263-6988=======
dhp@ihlpa.UUCP (12/12/86)
> A number of correspondents are telling me their e-mail is > being returned to them by a daemon at ihnp4, with words to > the effect that ihnp4 cannot contact uwvax. > ==ARPA:====================anderson@unix.macc.wisc.edu===Jess Anderson====== > | UUCP: {harvard,seismo,topaz, (avoid ihnp4!) 1210 W. Dayton | > | akgua,allegra,usbvax}!uwvax!uwmacc!anderson Madison, WI 53706 | > ==BITNET:============================anderson@wiscmacc===608/263-6988======= Calls from ihnp4 to uwvax are limited to 2am to 6am every day. Ihnp4 has, on the average, about 400 sites that it wants to talk to at any particular moment. This means of course that it is somewhat problematical whether np4 will attempt to call in the appropriate window. I suggest that the administrators of uwvax poll ihnp4 at least once a day to alleviate this bottleneck. I am not familiar with the history of the 2am to 6am limitation, but I assume it is a request from Madison. -- Douglas H. Price Analysts International Corp. @ AT&T Bell Laboratories ..!ihnp4!ihlpa!dhp