Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.unix.internals
Subject: Re: How to reply a uucp mail?
Keywords: UUCP
Message-ID: <202@raysnec.UUCP>
Date: 14 Jan 91 21:50:00 GMT
References: <1991Jan6.034113.3308@ncsuvx.ncsu.edu> <1991Jan11.141750.4947@ncsuvx.ncsu.edu>
Distribution: usa
Organization: IRS/CI - Technical Solutions Branch
Lines: 25

sagemma@eos.ncsu.edu (STEVEN ANTHONY GEMMA) writes:

>I am having the same problem.  It must be our system here at NCSU, 
>because I've never had the problem anywhere else I've tried from.
>If some kind soul would send me the answer, too, it would be greatly
>appreciated.  A friend of mine told me to try this form:

>ccicpg!cci632!sjfc!username@uunet.uu.net

	If I might rephrase your problem, mail which reached your system
via a UUCP channel contains a header or return address information which
can't be recognized by your user interface. Alternatively, your mail 
transfer agent is unable to transform a specific address into a form
recognizable by UUCP.

	The proposed construct shown above is not universally recognized,
and even where legal contains at least TWO potential routings, viz:
1) Go to site sjfc via ccicpg and ccit32, and from there follow any recognized
route to uunet.uu.net; 2) Follow any recognized route to uunet.uu.net, and
from there route to sjfc via ccicpg and cci632. FXmail's sdaemon and
alternative rmail support the latter approach. Yet more complex hackerisms
are supported in some implementations.

----------------
uunet!media!ka3ovk!raysnec!shwake				shwake@rsxtech