From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: tuhs-bounces@minnie.tuhs.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.1 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 4ecad868 for ; Mon, 25 Jun 2018 07:28:16 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 6F7559E5C0; Mon, 25 Jun 2018 17:28:15 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5D4299E5BE; Mon, 25 Jun 2018 17:28:00 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id BC61C9E5BE; Mon, 25 Jun 2018 17:27:58 +1000 (AEST) Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8]) by minnie.tuhs.org (Postfix) with ESMTP id 7632C9E5BD for ; Mon, 25 Jun 2018 17:27:58 +1000 (AEST) Received: from bitblocks.com (localhost [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 47D0F156E7DB; Mon, 25 Jun 2018 00:27:42 -0700 (PDT) From: Bakul Shah To: arnold@skeeve.com In-reply-to: Your message of "Mon, 25 Jun 2018 00:15:42 -0600." <201806250615.w5P6FgHA018820@freefriends.org> References: <20180621234706.GA23316@minnie.tuhs.org> <20180622142846.GS21272@mcvoy.com> <20180622145402.GT21272@mcvoy.com> <20180622151751.BEK9i%steffen@sdaoden.eu> <20180622192505.mfig_%steffen@sdaoden.eu> <89e5ae21-ccc0-5c84-837b-120a1a7d9e26@spamtrap.tnetconsulting.net> <20180623144959.M9byU%steffen@sdaoden.eu> <201806250615.w5P6FgHA018820@freefriends.org> Comments: In-reply-to arnold@skeeve.com message dated "Mon, 25 Jun 2018 00:15:42 -0600." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22033.1529911662.1@bitblocks.com> Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jun 2018 00:27:42 -0700 Message-Id: <20180625072751.47D0F156E7DB@mail.bitblocks.com> Subject: Re: [TUHS] off-topic list X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: tuhs@tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On Mon, 25 Jun 2018 00:15:42 -0600 arnold@skeeve.com wrote: > = > > On Sat, 23 Jun 2018, Michael Parson wrote: > > > > > The first rule in my .procmailrc does this with formail: > > > > Anyone with any concept of security will not be running Procmail; it's= not = > > even supported by its author any more, due to its opaque syntax and li= kely = > > vulnerabilities (it believes user-supplied headers and runs shell comm= ands = > > based upon them). > > > > -- Dave VK2KFU > = > So what is the alternative? I've been using it for years with > a pretty static setup to route incoming mail to different places. > I need *something* to do what it does. My crude method has worked better than anything else for me. [in used for over two decades] As I read only a subset of messages from mailing lists, if I directly filed such messages into their own folders, I would either have to waste more time scanning much larger mail folders &/or miss paying attention to some messages even once[1]. Fortunately, in MH one can use named sequences (that map to set of picked messages). In essence, I use sequences as "work space" and other folders as storage space. For example $ $ pick -seq me -to bakul -or -cc bakul -or -bcc bakul = $ pick -seq tuhs -to tuhs@tuhs -or -cc tuhs@tuhs ... When I have some idle time, I type $ inc # to incorporate new messages into inbox $ pickall # my script for creating sequences Next I scan these sequences in a priority order to see if anything seems interesting and then process these messages. Once done, I file them into their own folders and move on to the next sequence. The whole process takes a few minutes at most[2] and at the end the inbox is "zeroed"! By zeroing it each time, I ensure that the next time I will be processing only new messages, and typically spend less than a second per message summary line. [1] This happens to me on Apple Mail. [2] Unless I decide to reply!