Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!bu.edu!wang!fitz From: fitz@wang.com (Tom Fitzgerald) Newsgroups: comp.mail.uucp Subject: Re: internet/uucp mail Message-ID: Date: 20 Nov 90 02:24:30 GMT References: <1990Nov15.033214.27771@beach.csulb.edu> <1990Nov15.205028.4567@beach.csulb.edu> <658804371.13790@proa.sv.dg.com> Organization: Wang Labs, Lowell MA, USA Lines: 33 > ericp@beach.csulb.edu (Eric Pederson CSE) writes: >> My only problem now is that mail I recieve from UUCP sites here >> have a From: header like dest!user@bigcorp.com, which if I try to 'r'eply >> to, give the uux 101 unknown mailer error again. gary@proa.sv.dg.com (Gary Bridgewater) writes: > Of course it is no help to you, but, "bigcorp" has a broken .cf file if they > are abusing addresses like this. Their outgoing "From:" address rewriter > should not be blindly appending their domain address - it should check to > see if the current addresses is in "!" form and, if so, either 1) leave it > alone, or 2) PRE-pend their UUCP address if they have one. If bigcorp was sending the message over a UUCP link, yes; but in this case the message is going over SMTP to beach.csulb.edu and bigcorp.com has to make it RFC822 compliant before sending it. The easiest way to do this is by appending @bigcorp.com to it. The only way bigcorp could avoid this is if the message arrived with "From: dest.dom.ain!user", in which case bigcorp could rewrite it to "From: user@dest.dom.ain" before passing it on. If there isn't already a domain somewhere in the From: line, bigcorp has to append one. > A UUCP onlu site, when presented with uucpdest!user@knownhost.com address, > has to punt this to its smart upstream forwarder via > smart!knownhost.com!uucpdest!user. Not if it has a set of maps, and the maps contain knownhost.com. In that case it might find a better path to knownhost that doesn't go through 'smart'. --- Tom Fitzgerald Wang Labs fitz@wang.com 1-508-967-5278 Lowell MA, USA ...!uunet!wang!fitz