Brian Salter-Duke <b_duke@xxxxxxxxxxxxxxxxx> [2003:09:18:11:27:17+0930] scribed: > On Tue, Sep 16, 2003 at 01:08:03PM -0500, Michael D Schleif wrote: > > - --iq/fWD14IMVFWBCD > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > > > > Sometime earlier this year, I saw some solution to this, whether here, > > or in procmail, or wherever. > > > > Some mailing lists allow get requests to retrieve ranges of prior > > messages. When I receive them, they are in the form of a main body, and > > each individual message is an individual attachment to that main body. > > > > Yes, I can manually view-attachments, and manually save each to its > > place. > > > > How can I automate this? I have several hundred to break out, and I > > want some automation ;> > > > > What do you think? > > This has been discussed before. I use this all the time as I get the > mutt lists in digest form. Essentially you just pipe the digest to > "metamutt -D". This opens a new mutt window using a temporary mail > directory and a temporary muttrc file created by metamutt. You then have > all the separate messages in the mutt window. You could easily modify > this to create a new mailbox. Some digests are a bit mixed up, so I > first pipe the digest to a samll script I call premutt to clean them up > before piping them to metamutt. You should find all this in the archives > of the mutt list. What is `metamutt'? I searched the archives, and came up with three (3) hits, none of which tell me anything about metamutt . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --
Attachment:
pgpteEP37L6hB.pgp
Description: PGP signature