🚀 go-pugleaf

The answer to this one may be in the manual, but I haven't found it, so I
will prevail upon your collective wisdom:

From time to time, I get requests to forward copies of messages I have
received.  The number of messages involved is sometimes quite large.  My
usual approach is to use one or more pick commands to identify the messages
I wish to forward and pipe that into mail -f.  The problem with this approach
is that after the first few messages, the attempts to forward these messages
fail because of insufficient memory.  Apparently, each forwarded message is
initiated with a separate invocation of sendmail (?), and the machine runs out
of memory when I try to send too many at a time.  Is there a way I can either
get mush to wait for the earlier messages to quit before trying to send more
or a way I can conveniently break the list of messages into shorter lists that
I can manually space out?

Please note that I do not do the mush maintenance around here, so options in
the source do me no good.

Note also that the disk space occupied by the list of messages is sufficiently
large that I prefer not to save a second copy of all the messages in a scratch
mail folder in order to break up the forwarding that way.

Thank you for consideration.
-- 
Kurt W. Hirchert     hirchert@ncsa.uiuc.edu
National Center for Supercomputing Applications