From owner-freebsd-questions@FreeBSD.ORG Sun Aug 24 05:56:10 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15A1116A4BF for ; Sun, 24 Aug 2003 05:56:10 -0700 (PDT) Received: from kira.epconline.net (kira.epconline.net [207.206.185.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25ABB43F3F for ; Sun, 24 Aug 2003 05:56:09 -0700 (PDT) (envelope-from carock@epcusa.com) Received: from kira.epconline.net (root@localhost) by kira.epconline.net (8.12.9/8.12.6) with SMTP id h7OCu8bc066788 for ; Sun, 24 Aug 2003 07:56:08 -0500 (CDT) (envelope-from carock@epcusa.com) Received: from kira.epconline.net (localhost [127.0.0.1]) by kira.epconline.net (8.12.9/8.12.6) with ESMTP id h7OCu7Bd066778 for ; Sun, 24 Aug 2003 07:56:07 -0500 (CDT) (envelope-from carock@epcusa.com) Received: from localhost (carock@localhost)h7OCu7Jh066775 for ; Sun, 24 Aug 2003 07:56:07 -0500 (CDT) X-Authentication-Warning: kira.epconline.net: carock owned process doing -bs Date: Sun, 24 Aug 2003 07:56:07 -0500 (CDT) From: Chuck Rock X-X-Sender: carock@kira.epconline.net To: freebsd-questions@freebsd.org Message-ID: <20030824074911.O58919@kira.epconline.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: manage mbox files... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2003 12:56:10 -0000 Does anyone know of a utility similar to newsyslog that will handle mbox format files? I have Procmail sending messages to a file for some of my users, but I would like something "automatic" to keep the file from growing to fill my disk. I tried using newsyslog, but it just chops the file up when it hits it's limit, breaking the mbox format. This makes the file unreadable with Pine or other mail clients. I've been thinking about some kind of list archiving software, but it doesn't seem to fit the application. The best result I could hope for would be to have this file grow to a size limit I determine, then start throwing messages out as new one's come in, FIFO, and just keep the same file. I think that's asking a little much, so something like newsyslog would be second best, just keep two files around, the live on receiving messages, and the old one at it's limit, then when the new one hits it's limit, the old one is gone. Thanks, Chuck