🚀 go-pugleaf

In article <7094@xanth.cs.odu.edu> wisner@xanth.cs.odu.edu (Bill Wisner) writes:

>In article <412@execu.UUCP> dewey@execu.UUCP (Dewey Henize) writes:

>>Our alias file is, as Sun recommends, of the form
>>fred:	fred@execu
>>joe:	joe@prickleypear
>>...etc...

>Sounds bogus to me. If fred and joe are real accounts that want to receive
>mail on another machine, give them .forward files. If they're not real
>accounts and you're setting up forwarding addresses, disregard this
>paragraph.

As far as I can tell, .forward files don't really fit into a LAN environment.
In my case, I have about four or five YP domains, a corresponding number of
networks, and need to maintain complete interconnectability, for everybody's
convenience. But I can't mount everybody's home directory everywhere, that's
unnecessary and crude - that's what /usr/lib/aliases is for.

When I find .forward files in the LAN - usually as a result of receiving 
mail that looped round and round, before ending up in my mailbox as a problem
report from MAILER-DAEMON - I cat /dev/null into them and chown them to root
and chmod the sucker to 444 and that's that.

Always use /usr/lib/aliases, and concentrate all your network problems into
one place. .forward is an obsolete mechanism from a decade ago.

>Bill, the man from Xanth

What happened to Kent ? You guys merge ?	(-:

-- richard


-- 
 *                     Bismillah hir-Rahman nir-Rahim                         *
 *                                                                            *
 *      ..{amdahl|decwrl|octopus|pyramid|ucbvax}!avsd.UUCP!childers@tycho     *
 *          AMPEX Corporation - Audio-Visual Systems Division, R & D          *