[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Email forwarding on RaQ3
- Subject: Re: [cobalt-users] Email forwarding on RaQ3
- From: "Steven Werby" <steven-lists@xxxxxxxxxxxx>
- Date: Sat Aug 19 13:19:00 2000
Jeff Lasman <jblists@xxxxxxxxxxxxx> wrote:
> Steven Werby wrote:
>
> > If you want to do it the right way add records to /etc/aliases like below,
then
> > run "newaliases".
> >
> > username1: username2, username3, alias1@xxxxxxxxxxx, alias2@xxxxxxxxxxx
>
> Have you ever before come across my suggestion to create a new file
> called something like /etc/aliases.local and use it, so as to keep your
> own changes separate from Cobalt's?
I sure have. It's a good idea in order to keep records organized, but by no
means necessary. I've been maintain separate alias files for each instance of
Majordomo and for each external email customer since before I heard of Cobalt.
<snip>
> It does require a one-time/one-line change to sendmail.cf. I added the
> line:
>
> O AliasFile=/etc/aliases.local
<snip>
> And then you need to restart sendmail.
Is this true? Isn't it sufficient simply to run 'newaliases'?
> After that one time, though, you
> make all your own additions/changes to /etc/aliases.local, and can
> always see just what you've added (vs what the Cobalt gui has added) at
> a glance.
>
> > Or add recipients one per line to a text file and add records to
/etc/aliases
> > like:
> >
> > username1: :include:/path_to/my_distribution_list
>
> Probably a good idea to, after this, point out that the person then must
> run:
>
> # newaliases
Correct. I didn't mention that b/c I assumed the reader would be able to make
that leap after reading my comment to run 'newaliases' at the top of my post.
--
Steven Werby {steven-lists@xxxxxxxxxxxx}