Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!kth!sunic!chalmers!cs.chalmers.se!lindberg From: lindberg@cs.chalmers.se (Gunnar Lindberg) Newsgroups: comp.mail.uucp Subject: Re: Odd happenings with Tahoe UUCP Message-ID: <3141@fnatte.cs.chalmers.se> Date: 21 Jul 89 09:25:38 GMT References: <77544@pyramid.pyramid.com> <623@lakart.UUCP> Sender: news@cs.chalmers.se Organization: Chalmers University of Technology, Sweden Lines: 27 I'm sorry to send this as a Followup, but I tried to use the address from the article (AKA: dg%lakart.uucp@xait.xerox.com) and got back 554 ... unknown mailer error 255 Well, well... In article <623@lakart.UUCP> dg@lakart.UUCP (David Goodenough) writes: >I must beg to differ, for two reasons. > >1. They call _US_ and get through (about 15% of the time). Now as far as I >know, most Un*x systems won't call someone else that doesn't have a line >in their L.sys > >2. I called from my machine pallio at home, who is most definitely not in >their L.sys, and it gets the ^PRyou are unknown to me^@ _EVERY_ _TIME_ Could it be that your call now passes trough a device that uses/adds parity? We've had problems going through such devices since the version of uucp we use (no, don't ask me) did not strip off the 8:th bit of it's input characters (as I guess you know, the initial processing is done in raw mode, although comparision to L.sys names assume that the 8:th bit is 0). When we used "tip" to test manually, *it* did strip the 8:th bit off, so then everything seemed OK. Have you tried to actually call them by hand, using tip or kermit, and given them the correct (uucp)name? What's the reply then? Gunnar Lindberg