From owner-freebsd-security Thu Jul 30 07:28:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09675 for freebsd-security-outgoing; Thu, 30 Jul 1998 07:28:01 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from socrates.i-pi.com (socrates.i-pi.com [198.49.217.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09647 for ; Thu, 30 Jul 1998 07:27:57 -0700 (PDT) (envelope-from ingham@i-pi.com) Received: (from ingham@localhost) by socrates.i-pi.com (8.8.8/8.8.7) id IAA09952; Thu, 30 Jul 1998 08:17:28 -0600 (MDT) (envelope-from ingham) Message-ID: <19980730081728.46269@i-pi.com> Date: Thu, 30 Jul 1998 08:17:28 -0600 From: Kenneth Ingham To: Brett Glass , freebsd-security@FreeBSD.ORG Subject: Re: procmail workaround for MIME filename overflow exploit References: <199807291946.NAA14449@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199807291946.NAA14449@lariat.lariat.org>; from Brett Glass on Wed, Jul 29, 1998 at 01:46:14PM -0600 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got one problem with using procmail to solve the MIME problem. My users regularly send each other >5MB email messages. When I was using procmail as the local delivery agent, it died on large messages, sometimes taking all the swap space on the machine (284MB) with it. Changing back to the standard local mail delivery agent solved the problems. This is on a 2.2.6-RELEASE machine. Kenneth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message