From owner-freebsd-current@freebsd.org Fri Sep 11 06:16:30 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F209A02281 for ; Fri, 11 Sep 2015 06:16:30 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5DFD1AFB for ; Fri, 11 Sep 2015 06:16:29 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1ZaHdK-00047q-LJ; Fri, 11 Sep 2015 08:16:26 +0200 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1ZaHdK-0000X7-Km; Fri, 11 Sep 2015 08:16:26 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Fri, 11 Sep 2015 06:16:26 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "jbtakk" CC: "freebsd-current" Subject: Re: sendmail errors upon partial upgrade [SOLVED] Date: Thu, 10 Sep 2015 23:16:26 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2015 06:16:30 -0000 On Thu, 10 Sep 2015 21:38:40 -0700 (PDT), "Jeffrey Bouquet" wrote: > On Thu, 10 Sep 2015 18:04:52 -0700, Claus Assmann wrote: >=20 > > On Thu, Sep 10, 2015, Jeffrey Bouquet wrote: > > > opendaemonsocket: daemon Daemon0: cannot find: Can't assign requested= address > >=20 > > What's your mc file? > > What's the output of: > > fgrep Daemon0 /etc/mail/sen*.cf > > and maybe > > grep '^O DaemonPortOptions' /etc/mail/sen*.cf > >=20 > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 >=20 > Hmmm... three times I've composed a half page and the webmail erases it a= ll upon > attempting to paste in any file. > So short snippets... until I learn webmail better >=20 > relevant parts freebsd.mc > 2009 > mailertable, `hash -o /etc/mail/mailtertable` > smat host is defined > MAILER(local) > MAILER(smtp) >=20 > rc.conf > sendmail_enable=3D"NO" > sendmail_flags=3D"-q1m" >=20 > I've run mailq, verbose sendmail, mtree, rebuilt base sendmail and the /= etc/mail rebuild/resinstalls... >=20 > Perhaps a recent change requires the network active before sendmail sta= rts or > ipv6 defined somewhere or some other recent development in CURRENT, or > smtp somehow was configured back in 2004 and this week overwritten someho= w... >=20 > I've /var/log/maillog, attached as files, parts of when it was working and > now when it isnt... >=20 >=20 > Sorry to not proivde more information and not having the time right now t= o do a buildworld cycle > instead... >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Found an old pdf describing buildworld on v7. noticed m4 - mtree run as th= e last step. Rebooted to single-user On a hunch, I=20 found files in /usr/src/etc that had not been updated along with the=20 /usr/src/etc/rc.d which had (one or two or three files... network.subr etc) copied those few over, Maybe another fix or two... similar... reinstalled sendmail single user for good measure, Upon reboot all is back to as it was before, save a few errant not importan= t=20 misconfigurations which crept in that should resolve during the next year or so during usual port upgrades and buildworld cycles. Immediately logged on here, although it is late, so no one wastes anymore t= ime on this problem...=20=