From owner-freebsd-isp Tue Apr 30 10:14:59 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22293 for isp-outgoing; Tue, 30 Apr 1996 10:14:59 -0700 (PDT) Received: from mail.calweb.com (mail.calweb.com [165.90.138.20]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA22288 for ; Tue, 30 Apr 1996 10:14:57 -0700 (PDT) Received: from devnull.calweb.com (devnull.calweb.com [165.90.138.92]) by mail.calweb.com (8.7.5/8.7.3) with SMTP id KAA13291; Tue, 30 Apr 1996 10:11:01 -0700 (PDT) Message-Id: <2.2.32.19960430171457.00872294@pop.calweb.com> X-Sender: jfesler@pop.calweb.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 30 Apr 1996 10:14:57 -0700 To: Bruce Bauman From: Jason Fesler Subject: Re: POP timeout Cc: freebsd-isp@FreeBSD.ORG Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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.. -- 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.