From owner-freebsd-ports@FreeBSD.ORG Wed Nov 16 13:03:12 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CB231065670 for ; Wed, 16 Nov 2011 13:03:12 +0000 (UTC) (envelope-from wietse@porcupine.org) Received: from spike.porcupine.org (spike.porcupine.org [IPv6:2604:8d00:189::2]) by mx1.freebsd.org (Postfix) with ESMTP id 34B038FC13 for ; Wed, 16 Nov 2011 13:03:12 +0000 (UTC) Received: by spike.porcupine.org (Postfix, from userid 1001) id 3Sk5Nt4sX9zk2RT; Wed, 16 Nov 2011 08:03:10 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=porcupine.org; s=dktest; t=1321448590; bh=/ww3u6UkYSq9jEu8XqaaOchTBFJxjowCeTISK1zPEuw=; h=Subject:In-Reply-To:To:Date:Sender:From:CC:MIME-Version: Content-Transfer-Encoding:Content-Type:Message-Id; b=N9apcv9vL/KmGUzxZxDQvnU0DeLY2xWHJwbKI/yRMJUlrHTup7Tq85JJhgBDlokBL fj7OivUut9xhQKSXLt7/AlAUJEe4FhlQH8puYhEkuCHcmf1Dmh5GVrwT2D5yK0RV1q l68XQOGFB5toL8k8rI7VwAU6a7Ci7hmrqP50rAMo= In-Reply-To: <20111116125242.GH68080@home.opsec.eu> To: Kurt Jaeger Date: Wed, 16 Nov 2011 08:03:10 -0500 (EST) Sender: wietse@porcupine.org From: Wietse Venema X-Mailer: ELM [version 2.4ME+ PL124d (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: <3Sk5Nt4sX9zk2RT@spike.porcupine.org> Cc: wietse@porcupine.org, freebsd-ports@freebsd.org Subject: Re: "postfix-current" broken on amd64 platform X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2011 13:03:12 -0000 Kurt Jaeger: > Hi! > > > > > Postconf opens a socket to determine the mynetworks value (it > > > > determines the local interfaces and their netmasks). > > [quote > http://archives.neohapsis.com/archives/postfix/2011-11/0385.html] > > > > I have heard about bizarre errors on FreeBSD (jail) systems where > > > > the user-land library was out of sync with kernel-land, resulting > > > > in data structure mis-matches and system calls returning > > > > nonsensical results. > > > > Is it a clever idea to hardcode local interfaces on build machine > > > into a package that will then be redistributed to other machines? > > No. Postfix does none of that. Can someone please explain what socket call is failing, and what the reasons for that might be? I tend to believe that network-less build environments are not representative for the environment where an Internet MTA would run, but hey, what do I know. Wietse