From owner-freebsd-stable Wed Mar 1 12:52: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id AB08137BA9B for ; Wed, 1 Mar 2000 12:51:53 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.3/8.9.3) with ESMTP id PAA23243; Wed, 1 Mar 2000 15:51:42 -0500 (EST) (envelope-from melange@yip.org) Date: Wed, 1 Mar 2000 15:51:41 -0500 (EST) From: Bob K X-Sender: melange@localhost To: freebsd-stable@freebsd.org Cc: pine@freebsd.ady.ro Subject: rewrite: map mxserved not found Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just wanted to share an experience upgrading from 3.3-RELEASE to 3.4-STABLE cvsup'ed about a week ago. FreeBSD pi.yip.org 3.4-STABLE FreeBSD 3.4-STABLE #2: Mon Feb 28 01:11:37 EST 2000 melange@pi.yip.org:/usr/src/sys/compile/PI i386 Everything went smoothly except for the sendmail upgrade - anytime Pine 4.05 and later Pine-ssl 4.21.1.4 tried to send something to a non-local address, sendmail would barf with the error rewrite: map mxserved not found This appeared to be due to the following lines in sendmail.cf: # MX map (to allow relaying to hosts that we MX for) Kresolve host -a -T # Default was: #Kmxserved bestmx -z: -T Uncommenting the Kmxserved line fixed it. Fodder for the /usr/src/UPDATING file, perhaps? (Note: This only happened when Pine would attempt to send mail to a remote host - it did not affect incoming mail, majordomo 1.9.94, or anything else as far as I could tell) The maintainer for pine4 has been cc:'d. Bob "Life is like a video game with no chance to win" - Atari Teenage Riot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message