From owner-freebsd-pkg@FreeBSD.ORG Mon Oct 27 13:35:50 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DF049275 for ; Mon, 27 Oct 2014 13:35:50 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B0440890 for ; Mon, 27 Oct 2014 13:35:50 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 8CDA620B06 for ; Mon, 27 Oct 2014 09:35:49 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Mon, 27 Oct 2014 09:35:49 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=uvZIZ/xxrI7dnDyLSWk0Zh5y NdA=; b=el8gtBIQLXjxEYX1GCEPxMGeD9BGS9iSPGNLAaMJG/P4v+eD/ZvoSDzQ XGyHc4GOLFOrYvLLUHoLycBfMmQTf2gCwz6rdsis+nipXF0aXcx5RN0Qo+BSsJ0n MHG+0/VwEZNdXpnkWgU3bTukoHCpGwn1CO/znpI7810sZE97oio= Received: by web3.nyi.internal (Postfix, from userid 99) id 6DAA910F33A; Mon, 27 Oct 2014 09:35:49 -0400 (EDT) Message-Id: <1414416949.1808860.183749333.1363C933@webmail.messagingengine.com> X-Sasl-Enc: Ak6FjkOrwutjxBouLndwd2qcJg9Gjh/7W/pxMeSScWOl 1414416949 From: Mark Felder To: freebsd-pkg@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-c51dec4f In-Reply-To: References: Subject: Re: more pkg woes Date: Mon, 27 Oct 2014 08:35:49 -0500 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 13:35:51 -0000 On Sat, Oct 25, 2014, at 15:52, Paul Beard wrote: > It doesn=E2=80=99t do much good to select options that aren=E2=80=99t the= re.=20 >=20 > Oct 25 13:50:24 www postfix/smtp[84641]: warning: smtp_sasl_auth_enable > is true, but SASL support is not compiled in > Oct 25 13:50:24 www postfix/smtp[84641]: warning: TLS has been selected, > but TLS support is not compiled in >=20 > Not sure how many hours I still have to go before I fix this but it was a > damn site easier before pkgng.=20 > So the package you installed has=20 smtp_sasl_auth_enable =3D true but it's not compiled into the package? I just verified that both SASL and TLS port options are off by default. How does this compare to other OSes? Do they offer those out of the box? I wonder what upstream Postfix provides as well. My personal opinion here is that TLS should be enabled by default -- these days we should not be adding additional hurdles before users can implement best practices. FYI, the default configuration is not dynamically generated. It would take a significant amount of work to produce a config that matches the port's default build options. I do think we have an obvious problem here though if SASL and TLS are in the config by default but not built by default.