From owner-freebsd-questions Fri Dec 3 8:28:29 1999 Delivered-To: freebsd-questions@freebsd.org Received: from flashburn.parview.com (flashburn.parview.com [209.241.50.57]) by hub.freebsd.org (Postfix) with ESMTP id 0435A151CC for ; Fri, 3 Dec 1999 08:28:26 -0800 (PST) (envelope-from hg@parview.com) Received: from slice.parview.com (slice [192.168.2.26]) by flashburn.parview.com (Postfix) with ESMTP id D0AC31171A; Fri, 3 Dec 1999 11:27:51 -0500 (EST) Received: by slice.parview.com (Postfix, from userid 1001) id 3082110EE1; Fri, 3 Dec 1999 11:27:51 -0500 (EST) To: blake@pyramus.com, freebsd-questions@freebsd.org Subject: Re: Weird POPPER Problems In-Reply-To: <3.0.16.19991203080218.2e9752be@phil.pyramus.com> From: hgoldste@mpcs.com Reply-To: hgoldste@bbs.mpcs.com Message-Id: <19991203162751.3082110EE1@slice.parview.com> Date: Fri, 3 Dec 1999 11:27:51 -0500 (EST) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In mpc.lists.freebsd.questions, you wrote: : Any brainstorm on this issue would be appreciated. I realize it's not directly responsive to your problem however you may want to consider trying a different POP server. We had similar problems in an ISP environment keeping qpopper happy while dodging its idiosyncracies. All of these went away with migration to either cucipop or cyrus. The former would be a much more straightforward replacement for [q]popper, practically a drop-in. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message