From owner-freebsd-isp  Thu Mar 20 05:14:19 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA13048
          for isp-outgoing; Thu, 20 Mar 1997 05:14:19 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA13042
          for <freebsd-isp@freebsd.org>; Thu, 20 Mar 1997 05:14:11 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA00776; Thu, 20 Mar 1997 05:13:40 -0800 (PST)
To: Bradley Dunn <bradley@dunn.org>
cc: freebsd-isp@freebsd.org
Subject: Re: poppassd 
In-reply-to: Your message of "Thu, 20 Mar 1997 05:40:15 EST."
             <Pine.BSF.3.95q.970320053501.22639A-100000@ns2.harborcom.net> 
Date: Thu, 20 Mar 1997 05:13:40 -0800
Message-ID: <773.858863620@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Is anyone using the poppassd from the ports collection with 2.2? It was
> working fine under 2.1 and after we upgraded it broke. It goes through the
> 'user' and 'pass' phases fine, then invariably on the 'newpass' it exits
> with an "Unable to change password." The logs are not helpful. I
> pkg_delete'd it and recompiled it but that didn't change anything.
> 
> Just wondering if the port broke and no one noticed or if it is just our
> system that is broken. :)

Yes. :-)

More specifically, something about the port broke with 2.2.  It's a
known problem, but it appears that none of its users feel like fixing
it too badly since it's been broken for some time now. :-)

					Jordan