From owner-freebsd-questions@FreeBSD.ORG Tue Oct 5 14:56:55 2004 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 9BE0416A4CE for ; Tue, 5 Oct 2004 14:56:55 +0000 (GMT) Received: from smtp2.nblnetworks.fi (smtp2.nblnetworks.fi [217.30.182.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0F8343D45 for ; Tue, 5 Oct 2004 14:56:54 +0000 (GMT) (envelope-from pepe@kahvipannu.com) Received: from ssl.nebula.fi (webmail.nebula.fi [217.30.180.120]) by smtp2.nblnetworks.fi (8.12.8/8.12.8) with SMTP id i95EuqAq025821 for ; Tue, 5 Oct 2004 17:56:52 +0300 Received: from 62.183.166.174 (SquirrelMail authenticated user kahvi1) by ssl.nebula.fi with HTTP; Tue, 5 Oct 2004 17:56:52 +0300 (EEST) Message-ID: <1478.62.183.166.174.1096988212.squirrel@ssl.nebula.fi> In-Reply-To: <1096987863.1096.56.camel@prophecy.dyndns.org> References: <4759.62.183.166.174.1096955953.squirrel@ssl.nebula.fi> <1096986652.1096.48.camel@prophecy.dyndns.org> <1450.62.183.166.174.1096987234.squirrel@ssl.nebula.fi> <1096987863.1096.56.camel@prophecy.dyndns.org> Date: Tue, 5 Oct 2004 17:56:52 +0300 (EEST) From: "Perttu Laine" To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: imapd problem. 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: Tue, 05 Oct 2004 14:56:55 -0000 > Something running under the name of 'inetd' is binding to port 143 on > all inet4 addresses. Either that, or there's a bug in sockstat or the > kernel structures that it manipulates, though I've not seen mention of > that anywhere. Maybe it's an old instance of inetd from a changed > configuration? Perhaps you changed its configuration but forgot to > restart it? Funny. "killall -HUP inetd" helped. I didn't even need to do changes in inetd.conf. I should've just tried to restart it instead of checking config. No idea what I've been doing. Too much vodka perhaps - I'm from Finland you know. ;P Regards, Perttu Laine