From owner-freebsd-isp Sat Jan 6 12:18:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA13878 for isp-outgoing; Sat, 6 Jan 1996 12:18:53 -0800 (PST) Received: from cabal.io.org (cabal.io.org [198.133.36.103]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA13871 for ; Sat, 6 Jan 1996 12:18:50 -0800 (PST) Received: (from taob@localhost) by cabal.io.org (8.6.12/8.6.12) id PAA00803; Sat, 6 Jan 1996 15:15:31 -0500 Date: Sat, 6 Jan 1996 15:15:31 -0500 (EST) From: Brian Tao To: Joe Greco cc: Bruce Bauman , freebsd-isp@FreeBSD.ORG, boot@itchy.mosquito.com Subject: Re: limiting mailbox size? In-Reply-To: <199511271700.LAA11217@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG Precedence: bulk On Mon, 27 Nov 1995, Joe Greco wrote: > > No clean solutions that I've seen. :-) We have an additional problem in that excessively large mailboxes will cause some IMAP and POP clients to timeout their connections to the mail server. 99% of calls to support about "your mail server isn't working" can be attributed to someone with huge mailbox. I used to be nice and extract/delete out the big messages (file transmissions), but now I just move the entire mailbox into the home directory and instruct the user to download it back to their home machine and find a way of dealing with it from there. Our mail spool is closing in on 1.5 gigabytes (9891 mailboxes), on a 1.7-gig /var partition. Luckily, only on one occasion did the filesystem fill up *completely* (i.e., 109% capacity) and that was when a broken Unixware mail host repeatedly bounced 9-meg messages to one of our users (who had addressed to the wrong host in the first place). :-/ -- Brian Tao (BT300, taob@io.org) Systems Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"