Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel@rubyforge.org
Subject: [sup-devel]  importing your sup email into heliotrope
Date: Sun, 08 Jan 2012 20:50:02 +0000	[thread overview]
Message-ID: <1326055774-sup-6620@stapelberg.de> (raw)
In-Reply-To: <1325277038-sup-3185@tw-mbp-wmorgan.local>

Hi William,

(Re-sent message due to missing sendmail hook and thus wrong from address.)

Excerpts from William Morgan's message of 2011-12-30 20:31:24 +0000:
> 3. Import your mail sources into heliotrope. Mbox and maildir sources
>    should go pretty quick; IMAP, as usual, will be very slow. For each
>    source you can do this:
> 
>      $HELIOTROPE_DIR> ruby -Ilib bin/heliotrope-import --dir <mailstore dir> --sup-dumpfile <dumpfile> --mbox <mbox file>
I think you meant --sup-label-file, or you did not push some commits yet :).

>    Or replace "--mbox <mbox file>" with the corresponding argument to
>    your source (use --help to see them all).
FYI: I used the following command to get all my sources in one command line:
$ grep uri .sup/sources.yaml | sed 's/^[ \t]*uri: maildir://g' | tr '\n' ' '

The total time for importing was:
; scanned 133872, indexed 122314, skipped 9485 bad and 2073 seen messages in 12484.5s = 10.7 m/s

Which is awfully long. I took a look at the process list and saw lots of
html2text process running. Why are they run at all? Are they also run for
plain-text emails? Most of my emails surely are plain-text, without any need to
convert HTML.

> 5. Finally, reorder the index so that messages appear in order:
> 
>      $HELIOTROPE_DIR> ruby -Ilib bin/heliotrope-reindex --reorder --dir <mailstore dir>
>      $HELIOTROPE_DIR> mv <mailstore dir>/index <mailstore dir>/index-old
>      $HELIOTROPE_DIR> mv <mailstore dir>/index-reindexed <mailstore dir>/index
Ugh, this took a lot of time, too:
; reindexed 120451 messages, skipped 0 spam and 1863 deleted in 9509.3s = 12.7 m/s

Also, the numbers don’t add up. This is a bit confusing. Is there maybe no
printing of the *final* status? Or is this intended?

Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  parent reply	other threads:[~2012-01-08 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 20:31 William Morgan
2012-01-08 20:37 ` Michael Stapelberg
2012-01-08 20:50 ` Michael Stapelberg [this message]
2012-01-09 22:30   ` William Morgan

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=1326055774-sup-6620@stapelberg.de \
    --to=michael+sup@stapelberg.de \
    --cc=sup-devel@rubyforge.org \
    /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