Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Peter Davis <pd@world.std.com>
Subject: Re: Merging many different MH and mbox mail archives
Date: 17 Mar 2003 15:49:02 -0500	[thread overview]
Message-ID: <znntwwg1.fsf@bitstream.com> (raw)
In-Reply-To: <m3of4aysg2.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Peter Davis <pd@world.std.com> writes:
> 
> > 1) I'm assuming I would have to open each existing mbox of MH folder
> >    and respool all the messages to get them all filtered according to
> >    my split-fancy rules.  Is there any way to automate that, so I can
> >    just point to a top level directory and go away for a few hours
> >    (days?), and have all the mail in that tree get re-spooled?
> 
> Hm...  I don't think so.  Perhaps the, er, easiest way would be to
> write a shell script that copies all the files from the entire
> hierarchy into one biiiig directory, where you name the files with
> numerical names that increase with the date.  (That is, sort the
> files by date first.)  And then open that directory as an nnmh group,
> and then respool.

Hmm.  Interesting possibility.  The regular MH 'refile' command should
work for moving the messages, keeping numbers in sequence, etc.  I'd
really like to get the message numbers sorted by message date, but I
don't think refile can do that.

> > 2) When I respool messages, will messages with duplicate message IDs
> >    get eliminated?  I would be respooling into nnml groups.  Will new
> >    messages being split into a group be checked for matching ID
> >    against messages already in that group?
> 
> You can set `nnmail-treat-duplicates' to control that.  You should
> also probably increase `nnmail-message-id-cache-length'.
> 
> Hm...  but when respooling, those variables aren't really heeded.
> 
> Ok, scratch that.  Instead of respooling, use something like this:
> 
> (setq mail-sources
>       '((directory :path "/home/pd/that-directory-where-all-the-messages-are/"
>                    :suffix "")))
> 
> and just press `g' to fetch the mail as if it were new, which will
> lead to it getting run through the splitting methods, with duplicate
> suppression, etc.

Interesting idea.  Thanks!

> > 3) For some high-volume groups, I'd like to automatically split into
> >    different sub-groups by year ... nnml:this.that.1979,
> >    nnml:this.that.1980, etc.  Is there a way to set that up, and to
> >    have gnus create the groups automatically as needed?
> 
> There is no pre-defined functionality in Gnus for doing this.

I didn't think so.  Anyone have some lisp code that will do this?

Thanks very much!

-pd


-- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
                 The artwork formerly shown as prints
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html


      reply	other threads:[~2003-03-17 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E75CBB1.10301@world.std.com>
2003-03-17 14:32 ` Lars Magne Ingebrigtsen
2003-03-17 20:49   ` Peter Davis [this message]

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=znntwwg1.fsf@bitstream.com \
    --to=pd@world.std.com \
    /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).