lwv@n8emr.UUCP (Larry W. Virden) (12/17/87)
I am in search of modifications to rn which would ENSURE that the address which appears in the To: field will work, barring outside factors (such as a machine in the uucp link being down due to hardware problems, etc.) A sample of the kind of bounce that I see quite often is appended. I typed an 'r' while reading the comp.sources.d group article in reference and and the To: field was generated. I have fought and fought with mailx/Mail and rn to try to figure out how to convince them that the site that I am trying to talk to exists. In other cases, since this location uses smail, I have tried just providing site!user and so often get a bounced msg for my troubles. Isnt there SOME algorithm that could be used to GUARANTEE mail delivery? I have heard stories of folks getting physical mail delivered with PICTURES, PUZZLES, wrong spellings, etc. on the envelope; of course a HUMAN enters the picture for that type of mail. It surely seems funny that we cannot at least get mail addressing working properly when computers are generating the addresses! From uucp Wed Dec 16 05:06 EST 1987 >From rebel!gatech!rutgers!umix!itivax!mailer-daemon Wed Dec 16 05:06:03 1987 remote from dkstar Received: by n8emr.UUCP (smail2.5) id AA01812; 16 Dec 87 05:06:03 EST (Wed) Received: by dkstar.UUCP (5.9/5.17) id AA10348; Wed, 16 Dec 87 04:13:18 PST Received: by rebel.TOLERANT (5.1/4.13) id AA80226; Tue, 15 Dec 87 16:14:24 est Received: from rutgers.UUCP by gatech.edu with UUCP (5.58/7.3.GT) id AA28460; Tue, 15 Dec 87 15:47:19 EST Received: by RUTGERS.EDU (5.54/1.15) with UUCP id AA10410; Tue, 15 Dec 87 15:18:58 EST Received: by umix.cc.umich.edu (5.54/umix-2.0) id AA09782; Tue, 15 Dec 87 13:21:15 EST Received: by itivax.iti (5.51/1.0) id AA06348; Tue, 15 Dec 87 12:58:21 EST Date: Tue, 15 Dec 87 12:58:21 EST From: dkstar!rebel!gatech!rutgers!umix!itivax!mailer-daemon (Mail Delivery Subsystem) Subject: Returned mail: Host unknown Message-Id: <8712151758.AA06348@itivax.iti> To: n8emr!lwv Status: RO ----- Transcript of session follows ----- bad system name: chinet uux failed. code 68 550 chinet!dag... Host unknown ----- Unsent message follows ----- Received: by itivax.iti (5.51/1.0) id AA06343; Tue, 15 Dec 87 12:58:21 EST Received: by umix.cc.umich.edu (5.54/umix-2.0) id AA01746; Tue, 15 Dec 87 03:57:50 EST Received: by RUTGERS.EDU (5.54/1.15) with UUCP id AA19969; Tue, 15 Dec 87 03:07:23 EST Received: by mtune.ATT.COM (smail2.5) id AA29749; 13 Dec 87 19:40:48 EST (Sun) Received: by mtune.ATT.COM (smail2.5) id AA29737; 13 Dec 87 19:40:39 EST (Sun) Received: by cbosgd.MIS.OH.ATT.COM (smail2.1) id AA13271; 13 Dec 87 18:23:40 EST (Sun) Received: by n8emr.UUCP (smail2.5) id AA03298; 13 Dec 87 17:06:32 EST (Sun) To: umix!itivax!chinet!dag Subject: Re: File headers on shar files Newsgroups: comp.sources.d In-Reply-To: <1955@chinet.UUCP> References: <393@ddsw1.UUCP> <10908@sri-spam.istc.sri.com> Organization: N8EMR's Ham BBS (HBBS), Columbus,Ohio Cc: Message-Id: <8712131706.AA03298@n8emr.UUCP> Date: 13 Dec 87 17:06:32 EST (Sun) >From: umix!rutgers!gatech!rebel!dkstar!n8emr!lwv (Larry W. Virden) -- Larry W. Virden 75046,606 (CIS) 674 Falls Place, Reynoldsburg, OH 43068 (614) 864-8817 cbosgd!n8emr!lwv (UUCP) cbosgd!n8emr!lwv@PSUVAX1 (BITNET) We haven't inherited the world from our parents, but borrowed it from our children.
hyc@starbarlounge.cc.umich.edu (Howard Chu) (12/24/87)
In article <376@n8emr.UUCP> lwv@n8emr.UUCP (Larry W. Virden) writes: > >I am in search of modifications to rn which would ENSURE that the address >which appears in the To: field will work, barring outside factors (such >as a machine in the uucp link being down due to hardware problems, etc.) > >A sample of the kind of bounce that I see quite often is appended. I typed Unfortunately, what you're asking for can't be done by a program at your end. The problem is one (or both) of two things: 1. itivax isn't set up to recognize chinet as a valid uucp host 2. you're seeing a Usenet news path and assuming that a corresponding UUCP mail path exists. Usenet and UUCP aren't idempotent; you can't always assume that the route used by a news article will also work for UUCP mail, nor vice versa. You'll probably wind up having to post a news article if you want to get in touch with this person... Or send mail to itivax!postmaster and get on their case to set up a real UUCP mail link to chinet... / University of Michigan /_ , ,_. Computing Center / /(_/(__ Unix Project / '