From owner-freebsd-isp  Thu Jun 13 23:28:06 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA11186
          for isp-outgoing; Thu, 13 Jun 1996 23:28:06 -0700 (PDT)
Received: from lynx.its.unimelb.edu.au (lynx.its.unimelb.EDU.AU [128.250.20.151])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA11177
          for <freebsd-isp@FreeBSD.ORG>; Thu, 13 Jun 1996 23:28:00 -0700 (PDT)
Received: (from danny@localhost) by lynx.its.unimelb.edu.au (8.6.11/8.6.9) id QAA01942; Fri, 14 Jun 1996 16:27:41 +1000
Date: Fri, 14 Jun 1996 16:27:41 +1000 (EST)
From: "Daniel O'Callaghan" <danny@lynx.its.unimelb.edu.au>
To: Troy Arie Cobb <troy@circle.net>
cc: freebsd-isp@FreeBSD.ORG
Subject: Re: Poppassd
In-Reply-To: <Pine.BSF.3.91.960613235546.17166A-100000@demeter.circle.net>
Message-ID: <Pine.BSI.3.91.960614162627.1703B-100000@lynx.its.unimelb.edu.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Fri, 14 Jun 1996, Troy Arie Cobb wrote:

> 
> Has anyone managed to get poppassd to work?
> 
> For those who've never heard of it, poppassd 
> implements the POP password changing protocol
> used by Eudora among others.  Compiles fine.
> Having some problems with the funky virtual
> tty things it is doing.  It just drops 
> connection after getting the new password, 
> but doesn't change anything.
> 
> *shrug*
> 
> any help would be appreciated.

Well, passwd itself has code in it to prevent being used from a pty.
The simplest thing to do is to recompile passwd without that test in it.


Danny