From owner-freebsd-current  Sat Sep 28 20:19:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA02383
          for current-outgoing; Sat, 28 Sep 1996 20:19:51 -0700 (PDT)
Received: from gandalf.ec.camitel.com (174.ec.camitel.com [206.231.123.174])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA02266
          for <freebsd-current@FreeBSD.ORG>; Sat, 28 Sep 1996 20:19:33 -0700 (PDT)
Received: (from ccote@localhost) by gandalf.ec.camitel.com (8.7.6/8.7.3) id XAA06124; Sat, 28 Sep 1996 23:22:22 -0400 (EDT)
Date: Sat, 28 Sep 1996 23:22:22 -0400 (EDT)
Message-Id: <199609290322.XAA06124@gandalf.ec.camitel.com>
From: Claude Cote <ccote@gandalf.ec.camitel.com>
To: freebsd-current@FreeBSD.ORG
Subject: Problems with mail-aliasing using NIS
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

I have some problems with mail-aliasing using NIS. Here's the setup:

    - All the machines on the network shared the same /var/mail via NFS
      (but the mail is processed locally);
    - The NIS master holds the real (complete) /etc/aliases file;
    - I have commented out the keyword "aliases" in /var/yp/Makefile
      so the map mail.aliases get created when I type 'make' in /var/yp;
    - On the client side, I changed the following line in /etc/sendmail.cf:

            # location of alias file
            O AliasFile=/etc/aliases,nis:mail.aliases

      and run newaliases;
    - I rebooted everyone to be sure...

Now, if I add the alias "toto" and do a "mail toto" on the server,
it's ok. But if I do a "mail toto" on the client I got the following
message:

      toto... User unknown

Here's the output of "ypcat mail.aliases":

      # ypcat mail.aliases
      root
      @
      root
      root
      root
      postmaster
      root
      root
      root
      root
      root
      root
      ccote

is it ok?

BTW, the NIS master server is running -current of last Monday (23 sep)
and the clients are running 2.2-960801-SNAP. All the others NIS databases
(passwd, group, hosts, ...) are working just fine.

I have checked all the manpages, FAQ and handbook (the NIS section is
empty) without success :-(

Anybody have a clue?

Thanks,

Claude Cote (ccote@ec.camitel.com)