From owner-freebsd-questions Sun Feb 2 7:14:56 2003 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 ACCEE37B401 for ; Sun, 2 Feb 2003 07:14:55 -0800 (PST) Received: from hardesty.saintaardvarkthecarpeted.com (h24-76-91-242.vc.shawcable.net [24.76.91.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E91E43E4A for ; Sun, 2 Feb 2003 07:14:54 -0800 (PST) (envelope-from aardvark@hardesty.saintaardvarkthecarpeted.com) Received: from hardesty.saintaardvarkthecarpeted.com (localhost.localdomain [127.0.0.1]) by hardesty.saintaardvarkthecarpeted.com (8.12.5/8.12.5) with ESMTP id h12FBf6Z027193; Sun, 2 Feb 2003 07:11:41 -0800 Received: (from aardvark@localhost) by hardesty.saintaardvarkthecarpeted.com (8.12.5/8.12.5/Submit) id h12FBeqk027191; Sun, 2 Feb 2003 07:11:40 -0800 Date: Sun, 2 Feb 2003 07:11:40 -0800 From: Saint Aardvark the Carpeted To: Dragoncrest Cc: freebsd-questions@freebsd.org Subject: Re: Fetchmail slow? (was Re: Can't install fetchmail - HELP!) Message-ID: <20030202151140.GH20409@hardesty.saintaardvarkthecarpeted.com> References: <4.2.0.58.20030201181602.00993b40@pop.voyager.net> <4.2.0.58.20030201194438.0096de90@pop.voyager.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.2.0.58.20030201194438.0096de90@pop.voyager.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dragoncrest disturbed my sleep to write: > Now, on to the next bit of fun. Fetchmail is being dog slow. Yet > it's being silent and won't tell me why. Fetchmail was doing the same to me. It turned out that the POP server (one I run myself) was running the identd daemon, and was trying to query the computer that was running fetchmail to verify my identity. I had my firewall set up to drop these packets -- but this just makes the identd daemon try harder, until finally it times out. I read somewhere that the Right Way to take care of this was to send reset packets back, rather than silently drop them; the identd daemon gives up right away (or nearly so). Try using ipfw like so: reset tcp from any 113 to any in recv where is set to whatever your external interface, and see if that makes a difference. Hope this helps, Hugh -- Saint Aardvark the Carpeted aardvark@saintaardvarkthecarpeted.com Because the plural of Anecdote is Myth. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message