From owner-freebsd-questions Thu Oct 22 09:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18651 for freebsd-questions-outgoing; Thu, 22 Oct 1998 09:39:28 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18642 for ; Thu, 22 Oct 1998 09:39:25 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA24887; Thu, 22 Oct 1998 09:38:24 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Oct 1998 09:38:23 -0700 (PDT) From: Doug White To: Andrew McNaughton cc: questions@FreeBSD.ORG Subject: Re: Mail client program reccomendations? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Andrew McNaughton wrote: > I'm interested to know what other people consider to be the better client > programs for handling large ammounts of email. I've been using Pine and > it just doesn't do what I need. I recieve copies of every item going > through our newswires, as well as mailing lists and more personal > discussion and need to be able to archive, manage and quickly access many > thousands of email messages. I need to have important stuff brought to my > attention, and have less important stuff quietly archived. I'm interested > to hear about commercial packages as well as free ones. You need to discover procmail. I use it to split out all of my mailing lists into separate folders, ie questions mail goes into a questions folder, current into current, and so forth. My main inbox stays fairly clean. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message