From owner-freebsd-isp Thu May 9 18:37:41 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA28360 for isp-outgoing; Thu, 9 May 1996 18:37:41 -0700 (PDT) Received: from gallup.cia-g.com (root@gallup.cia-g.com [206.206.162.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA28353 for ; Thu, 9 May 1996 18:37:39 -0700 (PDT) Received: from gallup.cia-g.com (gallup.cia-g.com [206.206.162.10]) by gallup.cia-g.com (8.6.11/8.6.9) with SMTP id TAA03525; Thu, 9 May 1996 19:38:03 -0600 Date: Thu, 9 May 1996 19:38:01 -0600 (MDT) From: Stephen Fisher To: Patrick Ferguson cc: Jason Fesler , freebsd-isp@freebsd.org, Bruce Bauman Subject: Re: POP timeout In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, that's good to know, now how do we fix it? Switch to another popd? Change something in qpopper? On Thu, 9 May 1996, Patrick Ferguson wrote: > On Tue Apr 30 20:01:34 1996 Jason Fesler wrote: > >>At 08:59 AM 4/30/96 -0400, you wrote: > >>We are running FreeBSD 2.1 at our small ISP. Customers have occasionally > >>been complaining about being unable to communicate with our mail server > >>via POP. If I check our log files, I see messages like the following: > > > >One thing to check is the *size* of the mailbox being checked. > >qpopper's major weak point is with large mailboxes, as every time > >someone checks their mail, qpopper has to scan the entire mailbox > >file. > > > >Leave it to the local wArEz kiddies to try and trade via email to > >prove this particularly weak point in qpopper, by sending each other > >10-20 megabyte email messages..