From owner-freebsd-stable@FreeBSD.ORG Mon Jun 15 02:39:43 2015 Return-Path: Delivered-To: freebsd-stable@hub.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 18F5855A for ; Mon, 15 Jun 2015 02:39:43 +0000 (UTC) (envelope-from frank_s@bellsouth.net) Received: from fmailhost02.isp.att.net (fmailhost02.isp.att.net [204.127.217.102]) by mx1.freebsd.org (Postfix) with ESMTP id 0407EBA for ; Mon, 15 Jun 2015 02:39:42 +0000 (UTC) (envelope-from frank_s@bellsouth.net) Received: from ace.nina.org (adsl-74-178-59-239.gnv.bellsouth.net[74.178.59.239]) by isp.att.net (frfwmhc02) with SMTP id <20150615024028H02004pv3oe>; Mon, 15 Jun 2015 02:40:28 +0000 X-Originating-IP: [74.178.59.239] Date: Sun, 14 Jun 2015 22:39:41 -0400 (EDT) From: Frank Seltzer X-X-Sender: frank_s@Ace.nina.org To: Gregory Shapiro cc: freebsd-stable@freebsd.org Subject: Re: Sendmail problem after upgrade to r284296 In-Reply-To: <20150615013517.GA19755@minime.local> Message-ID: References: <20150614165507.GD95564@minime.local> <20150614180142.GE95564@minime.local> <20150615013517.GA19755@minime.local> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2015 02:39:43 -0000 On Sun, 14 Jun 2015, Gregory Shapiro wrote: >> After the update I got your email and followed your instructions, except for >> moving dh.param because it didn't exist, and sendmail is happy now. > > Happy to hear sendmail is happy. > >> I checked and there is still no mention of this in /usr/src/UPDATING so my >> question is, when and how is dh.param supposed to be created? Since I'm not >> the only one with this problem it doesn't seem to be something I did or >> didn't do. What could have caused dh.param to not be generated? > > That is a good question. If you didn't create it, I don't know what did -- it's not part of the base build (checked on a newly installed snapshot). Are you sure you didn't create it at some point? Not even the mail/sendmail port creates it. I created it per your instructions. See above about it not existing previously.