From owner-freebsd-questions  Sat Jun 28 10:48:49 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA28674
          for questions-outgoing; Sat, 28 Jun 1997 10:48:49 -0700 (PDT)
Received: from super-g.inch.com (super-g.inch.com [207.240.140.161])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28668
          for <freebsd-questions@FreeBSD.ORG>; Sat, 28 Jun 1997 10:48:47 -0700 (PDT)
Received: from localhost (spork@localhost)
	by super-g.inch.com (8.8.5/8.8.5) with SMTP id NAA10314;
	Sat, 28 Jun 1997 13:57:07 GMT
Date: Sat, 28 Jun 1997 13:57:06 +0000 (GMT)
From: spork <spork@super-g.com>
X-Sender: spork@super-g.inch.com
To: Nathan Dorfman <nathan@senate.org>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Majordomo Port
In-Reply-To: <199706281715.NAA11184@limbo.senate.org>
Message-ID: <Pine.BSF.3.95q.970628135512.10293A-100000@super-g.inch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I'm not sure what's causing your error, but I'm sure it's easily fixed...
One thing you should check before you fire it up is whether it's been
patched for a little bug that was posted to Bugtraq last week.  There's a
patch available; you should be able to find it on the archives at
www.geek-girl.com...

Charles

On Sat, 28 Jun 1997, Nathan Dorfman wrote:

> Hi! I downloaded the majordomo port from ftp.FreeBSD.org in the ports-2.2.1
> directory (I'm running 2.2.1-RELEASE). I did a make install. It downloaded
> the source and patched it and all, and this is the error I'm getting:
> 
> ===>  Configuring for majordomo-1.94.1
> majordom user using uid 54
> majordom user using gid 54
> chpass: corrupted entry
> 
> Majordomo user not found - aborting!
> 
> *** Error code 1
> 
> Stop.
> *** Error code 1
> 
> Stop.
> *** Error code 1
> 
> Stop.
> 
> 
> I tried adding this entry:
> majordom:*:54:54:Majordomo pseudo-user:/usr/local/majordomo:/nonexistent
> 
> to both /etc/passwd and /etc/master.passwd, with the exact same results.
> Changing the user name in these files to majordomo doesn't help either. Has
> anyone had any luck compiling Majordomo on a 2.2.1 system? Should I run
> listserv instead, in which case, what has this port done already that I need
> to undo :-)
>