From owner-freebsd-stable@FreeBSD.ORG Wed Apr 16 20:16:58 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 500A437B401 for ; Wed, 16 Apr 2003 20:16:58 -0700 (PDT) Received: from zardoc.esmtp.org (adsl-63-195-85-27.dsl.snfc21.pacbell.net [63.195.85.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A1CA43F75 for ; Wed, 16 Apr 2003 20:16:57 -0700 (PDT) (envelope-from ca@zardoc.esmtp.org) Received: from zardoc.esmtp.org (localhost [127.0.0.1])h3H3H5To008428 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 16 Apr 2003 20:17:05 -0700 (PDT) Received: (from ca@localhost) by zardoc.esmtp.org (8.12.7/8.12.0.Beta12) id h3H3H5FP022130 for freebsd-stable@freebsd.org; Wed, 16 Apr 2003 20:17:05 -0700 (PDT) Date: Wed, 16 Apr 2003 20:17:04 -0700 From: Claus Assmann To: freebsd-stable@freebsd.org Message-ID: <20030416201704.A28970@zardoc.esmtp.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <200304170312.h3H3C7M2032490@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200304170312.h3H3C7M2032490@drugs.dv.isc.org>; from Mark.Andrews@isc.org on Thu, Apr 17, 2003 at 01:12:07PM +1000 Subject: Re: post last sendmail upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 03:16:58 -0000 On Thu, Apr 17, 2003, Mark.Andrews@isc.org wrote: > > I've noticed email corruption post the last upgrade to sendmail > committed to stable. Is anyone else experiencing this? What kind of corruption? You may want to follow the advise in the last sentence: To provide partial protection for internal, unpatched MTAs that may be performing 7->8 or 8->7 bit MIME conversions, the default for MaxMimeHeaderLength has been changed to 2048/1024. Note: this does have a performance impact, and it only protects against frontal attacks from the outside. To disable the checks and return to pre-8.12.9 defaults, set MaxMimeHeaderLength to -1/-1. It seems that the MaxMimeHeaderLength checks remove '\0' under certain circumstances.