kendall shaw <kshaw(_at_)plight(_dot_)lbin(_dot_)com> writes:
I've read a bit about setting up filtering in procmail, but I still
don't see how to resolve my situation. If I were to setup procmail,
how would I know where mail has gone? After a weekend I typically
will have about 1000 messages waiting to be included (I use MH). I've
seen references to mailstat, but this would be pretty difficult for
me to use:
1. Run mailstat through less.
2. Visually scan for messages I wish to read, or which my filters missed.
3. Scan the corresponding folder with mh to find the message
4. Operate on the file
5. go to step 2
Are there any other options for me? I usually use MH through mh-e.
I also use MH, and to avoid having mail refiled into some place I'll
forget about it, I decided that:
1) Mail directly refiled into MH folders will only go under one
particular 'branch' of my folder tree, namely +Lists. For
example, all mail from this list is refiled in +Lists/procmail
2) Everything else will be left in $DEFAULT from which I'll 'inc' it
into my inbox.
Since I keep the folders underneath +Lists empty or almost empty
(+Lists/procmail has 10 messages in it right now, yours being the
10th), I can easily see when new mail has arrived from a list by just
saying "folders +Lists". By requiring a conscious action on my part to
put mail in +inbox, I make sure that I have at least that chance to see
what's come in. Furthermore, I use the "unseen" sequence, as created
by 'inc' to keep track of what I haven't read yet. Ta da, no
(accidentally) lost mail.
Philip Guenther