From owner-freebsd-questions Mon Dec 4 00:43:53 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA09946 for questions-outgoing; Mon, 4 Dec 1995 00:43:53 -0800 Received: from onyx.southwind.net (root@onyx.southwind.net [204.95.83.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA09939 ; Mon, 4 Dec 1995 00:43:48 -0800 Received: (from Ucomplet@localhost) by onyx.southwind.net (8.6.12/8.6.12) with UUCP id CAA01888; Mon, 4 Dec 1995 02:25:06 -0600 Received: from complete.org (complete.org [127.0.0.1]) by complete.org (8.7.2/8.7.2) with SMTP id BAA00524; Mon, 4 Dec 1995 01:40:05 -0600 (CST) Message-Id: <199512040740.BAA00524@complete.org> X-Authentication-Warning: complete.org: Host complete.org [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.4 10/10/95 To: Rob Snow cc: dwhite@resnet.uoregon.edu, Donald Burr , "Jonathan M. Bresler" , questions@freebsd.org, "Jonathan M. Bresler" Subject: Re: pop client In-reply-to: Your message of "Sun, 03 Dec 1995 00:47:40 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Dec 1995 01:40:03 -0600 From: John Goerzen Sender: owner-questions@freebsd.org Precedence: bulk > Actually I believe that the pop implementation in pine is broken. I > followed some threads earlier this year about Pine's pop implement > before I ported popclient. I don't remember what the errors were but > I believe it'll fail in use. Rob, you are quite correct. Pine failed completely while popclient worked with no problems. -- John Goerzen, programmer and owner | MICRO$oft only exists because some Communications Centre & Complete BBS | people are too dumb to get something E-mail jgoerzen@complete.org | better, such as FreeBSD.