From owner-freebsd-questions@FreeBSD.ORG Tue Sep 16 21:06:18 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D24016A4B3 for ; Tue, 16 Sep 2003 21:06:18 -0700 (PDT) Received: from skywalker.rogness.net (skywalker.rogness.net [64.251.173.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AC6E43FAF for ; Tue, 16 Sep 2003 21:06:17 -0700 (PDT) (envelope-from nick@rogness.net) Received: from skywalker.rogness.net (localhost [127.0.0.1]) by skywalker.rogness.net (8.12.5/8.12.5) with ESMTP id h8H4CbVs092788; Tue, 16 Sep 2003 22:12:37 -0600 (MDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost)h8H4CaiH092785; Tue, 16 Sep 2003 22:12:37 -0600 (MDT) X-Authentication-Warning: skywalker.rogness.net: nick owned process doing -bs Date: Tue, 16 Sep 2003 22:12:34 -0600 (MDT) From: Nick Rogness To: "Jason L. Schwab" In-Reply-To: <20030916175514.V28688@brittney.jlschwab.com> Message-ID: <20030916220209.R92689-100000@skywalker.rogness.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: Re: Courier IMAPd and UW IMAPd Very Slow X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 04:06:18 -0000 On Tue, 16 Sep 2003, Jason L. Schwab wrote: > Heya Folks; > > I've been looking into setting up IMAPd support > on my mail servers, and i got it working with > both UW and Courier, but both seem to take way > to long (upwards of minutes) to login and fetch > my mail. (like 10 messages) on the test acct. I would not blame the software so quickly. We run imap-uw on very heavily loaded boxes and rarely see problems with it. Sure it's not the fastest but minutes of wait? No. I would suggest looking at: 1) DNS issues (resolution issues) 2) If it's login related checking into PAM issues (DB issues) 3) Check network problems (Duplex mismatch? Congestion?) 4) Check hardware problems (Disk especially) Nick Rogness - How many people here have telekenetic powers? Raise my hand. -Emo Philips