From owner-freebsd-isp  Fri Apr 18 14:26:30 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA04611
          for isp-outgoing; Fri, 18 Apr 1997 14:26:30 -0700 (PDT)
Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA04554
          for <freebsd-isp@freebsd.org>; Fri, 18 Apr 1997 14:26:23 -0700 (PDT)
Received: from localhost (bradley@localhost)
          by ns2.harborcom.net (8.8.5/8.8.4) with SMTP
	  id RAA27900; Fri, 18 Apr 1997 17:26:06 -0400 (EDT)
Date: Fri, 18 Apr 1997 17:26:06 -0400 (EDT)
From: Bradley Dunn <bradley@dunn.org>
X-Sender: bradley@ns2.harborcom.net
To: Travis Mikalson <bofh@TerraNova.net>
cc: freebsd-isp@freebsd.org
Subject: Re: ERR POP EOF console errors
In-Reply-To: <3357E2E7.42F2@TerraNova.net>
Message-ID: <Pine.BSF.3.96.970418171633.23746A-100000@ns2.harborcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 18 Apr 1997, Travis Mikalson wrote:

> Ok, then why does qpopper 2.2 not like it?
> MS Internet Mail used to do _something_ wrong with the auth command
> according to that particular error message qpopper generates..

Because if you would read the RFC you would see that it is an optional
command. The authors of qpopper chose not to implement it.

> Is one of the most popular POP3 servers in use today not RFC1734
> compliant or was MS Internet Mail wocked?

One of the most popular POP3 servers in use today is not RFC1734
compliant (nor is it required to be).

pbd