From: Bakul Shah <bakul@bitblocks.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] off-topic list
Date: Mon, 25 Jun 2018 00:27:42 -0700 [thread overview]
Message-ID: <20180625072751.47D0F156E7DB@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 25 Jun 2018 00:15:42 -0600." <201806250615.w5P6FgHA018820@freefriends.org>
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 likely
> > vulnerabilities (it believes user-supplied headers and runs shell commands
> > 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
$ <run spam filtering script>
$ 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!
next prev parent reply other threads:[~2018-06-25 7:28 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 22:44 [TUHS] core Nelson H. F. Beebe
2018-06-21 23:07 ` Grant Taylor via TUHS
2018-06-21 23:38 ` Toby Thain
2018-06-21 23:47 ` [TUHS] off-topic list Warren Toomey
2018-06-22 1:11 ` Grant Taylor via TUHS
2018-06-22 3:53 ` Robert Brockway
2018-06-22 4:18 ` Dave Horsfall
2018-06-22 11:44 ` Arthur Krewat
2018-06-22 14:28 ` Larry McVoy
2018-06-22 14:46 ` Tim Bradshaw
2018-06-22 14:54 ` Larry McVoy
2018-06-22 15:17 ` Steffen Nurpmeso
2018-06-22 17:27 ` Grant Taylor via TUHS
2018-06-22 19:25 ` Steffen Nurpmeso
2018-06-22 21:04 ` Grant Taylor via TUHS
2018-06-23 14:49 ` Steffen Nurpmeso
2018-06-23 15:25 ` Toby Thain
2018-06-23 18:49 ` Grant Taylor via TUHS
2018-06-23 21:05 ` Tom Ivar Helbekkmo via TUHS
2018-06-23 21:21 ` Michael Parson
2018-06-23 23:31 ` Grant Taylor via TUHS
2018-06-23 23:36 ` Larry McVoy
2018-06-23 23:37 ` Larry McVoy
2018-06-24 0:20 ` Grant Taylor via TUHS
2018-06-25 2:53 ` Dave Horsfall
2018-06-25 5:40 ` Grant Taylor via TUHS
2018-06-25 6:15 ` arnold
2018-06-25 7:27 ` Bakul Shah [this message]
2018-06-25 12:52 ` Michael Parson
2018-06-25 13:41 ` arnold
2018-06-25 13:56 ` arnold
2018-06-25 13:59 ` Adam Sampson
2018-06-25 15:05 ` Grant Taylor via TUHS
2018-06-26 9:05 ` Derek Fawcus
2018-06-28 14:25 ` [TUHS] email filtering (was Re: off-topic list) Perry E. Metzger
2018-06-23 22:38 ` [TUHS] off-topic list Steffen Nurpmeso
2018-06-24 0:18 ` Grant Taylor via TUHS
2018-06-24 10:04 ` Michael Kjörling
2018-06-25 16:10 ` Steffen Nurpmeso
2018-06-25 18:48 ` Grant Taylor via TUHS
2018-06-25 0:43 ` [TUHS] mail (Re: " Bakul Shah
2018-06-25 1:15 ` Lyndon Nerenberg
2018-06-25 2:44 ` George Michaelson
2018-06-25 3:04 ` Larry McVoy
2018-06-25 3:15 ` Bakul Shah
2018-06-25 16:26 ` Steffen Nurpmeso
2018-06-25 18:59 ` Grant Taylor via TUHS
2018-06-25 14:18 ` [TUHS] " Clem Cole
2018-06-25 15:28 ` [TUHS] off-topic list [ really mh ] Jon Steinhart
2018-06-26 7:49 ` Ralph Corderoy
2018-06-25 15:51 ` [TUHS] off-topic list Steffen Nurpmeso
2018-06-25 18:21 ` Grant Taylor via TUHS
2018-06-26 20:38 ` Steffen Nurpmeso
2018-06-22 16:07 ` Tim Bradshaw
2018-06-22 16:36 ` Steve Johnson
2018-06-22 20:55 ` Bakul Shah
2018-06-22 14:52 ` Ralph Corderoy
2018-06-22 15:13 ` SPC
2018-06-22 16:45 ` Larry McVoy
2018-06-22 15:28 ` Clem Cole
2018-06-22 17:17 ` Grant Taylor via TUHS
2018-06-22 18:00 ` Dan Cross
2018-06-22 17:29 ` Cág
2018-06-22 2:21 Noel Chiappa
2018-06-22 22:23 Doug McIlroy
2018-06-22 23:20 ` John P. Linderman
2018-06-23 0:22 ` Warren Toomey
2018-06-24 3:08 Norman Wilson
2018-06-24 13:14 Noel Chiappa
2018-06-25 1:38 ` Dave Horsfall
2018-06-25 1:46 ` Grant Taylor via TUHS
2018-06-25 16:44 ` Steffen Nurpmeso
2018-06-25 12:45 ` Tony Finch
2018-06-25 16:41 ` Steffen Nurpmeso
2018-06-25 14:44 Noel Chiappa
2018-06-25 15:44 ` Clem Cole
2018-06-25 16:03 ` Paul Winalski
2018-06-25 17:22 ` Clem Cole
2018-06-25 16:10 Noel Chiappa
2018-06-25 17:37 ` Clem Cole
2018-06-25 19:35 ` Grant Taylor via TUHS
2018-06-25 20:09 ` Clem Cole
2018-06-25 20:47 ` Grant Taylor via TUHS
2018-06-25 21:15 ` Clem Cole
2018-06-26 7:01 ` arnold
2018-06-26 8:57 ` Derek Fawcus
2018-06-26 11:29 ` Tim Bradshaw
2018-06-26 13:09 ` Tony Finch
2018-06-26 18:04 ` Warner Losh
2018-06-26 21:16 ` Clem Cole
2018-06-27 21:33 ` Michael Parson
2018-06-27 22:27 ` Clem cole
2018-06-28 5:57 ` arnold
2018-06-28 18:36 ` Michael Parson
2018-06-26 15:57 ` Michael Kjörling
2018-06-26 21:09 ` Steffen Nurpmeso
2018-06-26 21:18 ` Clem Cole
2018-06-26 23:45 ` George Michaelson
2018-06-25 20:15 ` Lyndon Nerenberg
2018-06-26 8:27 ` Tony Finch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180625072751.47D0F156E7DB@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=arnold@skeeve.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).