From owner-freebsd-isp Fri May 10 13:27:06 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20953 for isp-outgoing; Fri, 10 May 1996 13:27:06 -0700 (PDT) Received: from digital.netvoyage.net (root@digital.netvoyage.net [205.162.154.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA20946 for ; Fri, 10 May 1996 13:27:03 -0700 (PDT) Received: from localhost (bogawa@localhost) by digital.netvoyage.net (8.6.13/8.6.9) with SMTP id NAA13346; Fri, 10 May 1996 13:22:24 -0700 Date: Fri, 10 May 1996 13:22:23 -0700 (PDT) From: Bryan Ogawa at Work 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 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.. What's even worse, though, are little old ladies who have 10 megabytes of SMALL mail, who set their Eudora to: (1) check mail every five minutes, and (2) LEAVE MAIL ON SERVER!!!! Recently, our machine has been dog slow, and I've been trying to figure out why. I thought it was a not enough RAM problem, but it turns out that one of our customers is doing the above. Our pop server (popper?) reads AND WRITES the mail for people who ask to leave mail on server. The above situation leads to disk thrashing as a simple (and reasonably fast, on their end, as the pop client only sends new mail) check new mail every 4 minutes generates huge disk bandwidth. Other than telling customers DON'T DO THAT, do you guys have any other suggestions? > > > >-- > > Jason Fesler jfesler@calweb.com > > Admin, CalWeb Internet Services jfroot@calweb.com > > I like my Usenet over ice, please. http://www.gigo.com > > Disclaimer: My /dev/null can beat your /dev/null any day. > > > > ------------------------------------------------------------------------------ > Patrick Ferguson - Systems Administrator patrick@dmv.com > DelMarVa OnLine! - Salisbury, MD > > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: 2.6.2 > > mQBNAzGBrOQAAAECALpR8GMUAXnKbr9LeXVv18Q8y/n1NM1+YS8ffP/5HvM0gyso > F1T9+gcGvb3L2nFwj+wnig0UQY93vXqhXPoFN4UABRG0IlBhdHJpY2sgRmVyZ3Vz > b24gPHBhdHJpY2tAZG12LmNvbT4= > =AgnQ > -----END PGP PUBLIC KEY BLOCK----- > > Bryan K. Ogawa Questions or Problems with NetVoyage? help@netvoyage.net Check out the NetVoyage HelpWeb at..