dent@unocss.UUCP (Dave Caplinger) (05/27/88)
Many thanks to those of you who have posted here or sent me mail about
the problem of forwarding mail to an "alias" (without an actual account)
from outside sites. The "correct" solution seems to be:
(with SYSNAM priv)
MAIL> set forward/user=help manager
So now I suppose I can "reveal" the whole point behind this. Several of the
consultants employed by Campus Computing here at UNO cannot receive BITNET
mail because of the 8 character username limit imposed by BITNET. So, our
intent was to create mail "aliases" for them of the form CONSLT## which they
would claim as their BITNET return address instead of their actual account
names, CONSULT##.
The only problem that now remains is the fact that consultants will not be
able to receive network files, since no search is done through the MAILUAF
file by the JNET software. Thus, any BITNET network file sent to (for
example) CONSULT31 will get sent to our machine, but notify all of the
CONSULT3[0-9] accounts of the file until any one of them RECEIVEs it.
Likewise, any interactive messages (listservers and the like) will hang out
in limbo for the same reason.
So, is there any way to fix /this/ little problem? Should I talk with the
company that wrote the JNET software? (Sorry, I forgot their exact name.)
Or should we simply give in and change the CONSULT## accounts permanently
to CONSLT## (The whole nine yards: change their UIC, directory names, etc)?
Again, many thanks to those who responded to my previous question, and thanks
in advance to anyone that might have a suggestion regarding this latest one!
-/ Dave Caplinger /--------------+--------------------------------------------
Microcomputer Specialist | Internet: UNOCC07%ZEUS.DNET@FERGVAX.UNL.EDU
Campus Computing | UUCP: {ihnp4}!unocss!dent
University of Nebraska at Omaha | Bitnet: UNOCC07@UNOMA1
Omaha, NE 68182 | or dc3a+@andrew.cmu.edu