Subject: delete/undelete key behaviour

From: Andrew Daviel <[email-masked]>
Date: Wed, 27 Mar 2002 10:04:13 -0800 (PST)

I seem to often be in the situation where a lot of mail in
a particular folder is junk, but there are some good ones (I filter into
multiple inboxes with procmail). For instance, spam folders, postmaster
folders and cron folders.

So, holding down the "D" key in the index page is a quick way to
delete a block of junk mail.
If there are only a few hundred messages messages, there is no problem.
But with more than that, Pine lags behind the keyboard. Again, not usually
a problem. If I over-run and there are a few good messages I can quickly 
back up and undelete the good ones.

I just had a situation (it's happened a few times before) where I've had
5000 junk messages with blocks of hundreds of good ones interspersed.
The best thing, I guess, would for me to have written a better filter in 
the first place, or to intelligently re-filter the folder after the fact.

To cut a long story short (or not, as the case may be), I'd like the
"U" key to behave like the "D" key so that I can quickly undelete
deleted blocks of messages

(BTW, anyone know of a post-filter program, preferably something that
will feed procmail or use procmail rules ?)

-- 
Andrew Daviel, TRIUMF, Canada
Tel. +1 (604) 222-7376
[email-masked]

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Terry Gray <[email-masked]>
Date: Wed, 27 Mar 2002 10:12:15 -0800 (Pacific Standard Time)

A workaround would be to use the single message Select cmd ":", which does
advance to the next msg... then Apply Undelete.

-teg

---

From: daniel lance herrick <[email-masked]>
Date: Wed, 27 Mar 2002 13:49:17 -0500 (EST)

You can use formail, part of the procmail package,
to separate a box into individual messages and
then process them one by one, such as by feeding
them into procmail (specifying a different
.procmailrc on the command line or using the main
one which has presumably just become smarter).

(As they go by, formail is willing to mung the
headers in interesting ways.)

If "man procmail" works, so should "man formail".

dan