Commit graph

3009 commits

Author SHA1 Message Date
Carl Worth
0e777a8f80 notmuch: Switch from gmime to custom, ad-hoc parsing of headers.
Since we're currently just trying to stitch together In-Reply-To
and References headers we don't need that much sophistication.
It's when we later add full-text searching that GMime will be
useful.

So for now, even though my own code here is surely very buggy
compared to GMime it's also a lot faster. And speed is what
we're after for the initial index creation.
2009-10-19 13:00:43 -07:00
Carl Worth
9bc4253fa8 notmuch: Ignore .notmuch when counting files.
We were correctly ignoring this when adding files, but not when
doing the initial count. Clearly we need better code sharing
here.
2009-10-19 12:52:46 -07:00
Carl Worth
10c176ba0e notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).

The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).

The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.)  We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).

The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-18 20:56:30 -07:00
Carl Worth
512f7bb0f6 xapian-dump: Rewrite to generate C code as output.
This was for some time testing, (to see how fast xapian could be
if we were strictly adding documents and not doing any other IO
or computation). The answer is that xapian is quite fast, (on
the order of 1000 documents per second).
2009-10-18 20:49:43 -07:00
Carl Worth
36640b303e Start a new top-level executable: notmuch.
Of course, there's not much that this program does yet. It's got
some structure for some sub-commands that don't do anything. And
it has a main command that prints some explanatory text and then
counts all the regular files in your mail archive.
2009-10-17 08:26:58 -07:00
Carl Worth
9c3807e688 Fix more memory leaks.
These were more significant than the previous leak because these were
in the loop and leaking memory for every message being parsed. It
turns out that g_hash_table_new should probably be named
g_hash_table_new_and_leak_memory_please. The actually useful function
is g_hash_table_new_full which lets us pass a free function, (to free
keys when inserting duplicates into the hash table). And after all,
weeding out duplicates is the only reason we are using this hash table
in the first place.

It almost goes without saying, valgrind found these leaks.
2009-10-16 13:45:17 -07:00
Carl Worth
28c0691ab9 Fix a one-time memory leak.
This was a single object in main outside any loops, so there was
no impact on performance or anything, but obviously we still want
to patch this.

Of course, valgrind gets the credit for seeing this.
2009-10-16 13:41:37 -07:00
Carl Worth
dcebf35ec9 Avoid reading a byte just before our allocated buffer.
When looking for a trailing ':' to introduce a quotation we peek at
the last character before a newline. But for blank lines, that's not
where we want to look. And when the first line in our buffer is a
blank line, we're underrunning our buffer. The fix is easy---just
bail early on blank lines since they have no terms anyway.

Thanks to valgrind for pointing out this error.
2009-10-16 13:38:43 -07:00
Carl Worth
387a28281c Generate random thread IDs instead of using an arbitrary Message-ID.
Previously, we used as the thread-id the message-id of the first
message in the thread that we happened to find. In fact, this is a
totally arbitrary identifier, so it might as well be random. And an
advantage of actually using a random identifier is that we now have
fixed-length thead identifiers, (and the way is open to even allow
abbreviated identifiers like git does---though we're less likely to
show these identifiers to actual users).
2009-10-16 13:33:39 -07:00
Carl Worth
5fbdbeb333 Change progress report to show "instantaneous" rate. Also print total time.
Instead of always showing the overall rate, we wait until the end
to show that. Then, on incremental updates we show the rate over the
last increment. This makes it much easier to actually watch what's
happening, (and it's easy to see the efect of xapian's internal
10,000 document flush).
2009-10-15 09:04:31 -07:00
Keith Packard
a2c467242a Protect against missing message id while indexing files 2009-10-14 21:46:54 -07:00
Keith Packard
8f3ccda00f Walk address groups and parse each address separately
Signed-off-by: Keith Packard <keithp@keithp.com>
2009-10-14 21:17:39 -07:00
Carl Worth
5166406bef Reduce the verbosity of the progress indicator.
It's fast enough that we can wait for 1000 messages before updating.
2009-10-14 17:26:28 -07:00
Carl Worth
a5865d0574 Add support for message-part mime parts.
We could (and probably should) reparse and index all the headers from
the embedded message, but I'm not choosing to do that now---I'm just
indexing the body of the embedded message.
2009-10-14 17:25:20 -07:00
Carl Worth
914df660c4 Avoid segfault on message with no subject.
It's fun how turning a program loose on 500,000 messages will find
lots of littel corner cases.
2009-10-14 17:24:28 -07:00
Carl Worth
d643f7d776 Add some sort of progress indicator.
It's nice to let the user know that something is happening.
2009-10-14 17:10:14 -07:00
Carl Worth
71bd250cb6 Avoid complaints about messages with empty mime parts. 2009-10-14 17:09:56 -07:00
Carl Worth
48d2e2dc44 Avoid complaints about empty address lists. 2009-10-14 17:09:30 -07:00
Carl Worth
bae1ce09a3 Document the little details separating the sup and notmuch indexes.
As can be seen here, there are not a lot of differences. I've verified
this by using sup-sync to import a month of mail from the sup mailing
list, and comparing the database term-by-term, value-by-value, and
data-by-data with that created by notmuch. There are no differences
other than those documented here.
2009-10-14 16:49:26 -07:00
Carl Worth
784779fb67 Avoid trimming initial whitespace while looking for signatures.
I ran into a message with an indented stack trace that my indexer
was mistaking for a signature.
2009-10-14 16:38:21 -07:00
Carl Worth
30ed705fda Index an attachment's filename extension as well.
I hadn't realized that sup used a special term for this. But there
you go.
2009-10-14 16:35:03 -07:00
Carl Worth
29974af08f Index the filename of any attachment. 2009-10-14 16:28:07 -07:00
Carl Worth
653ff260f5 [sup-compat] Don't index mime parts with content-disposition of attachment
Here's another change which I'm making for sup compatibility against
my better judgment. It seems that sup never indexes content from
mime parts with content-disposition of attachment. But these
attachments are often very indexable, (for example, the first one
I encountered was a small shell script).

So I'll have to think a bit about whether or not I want to revert
this commit. To do this properly we would really want to distinguish
between attachments that are indexable, (such as text), and those
that aren't, (such as binaries). I know the mime-type alone isn't
alwas sufficient here as even this little plaintext shell script
was attached as octet-stream.

And if we wanted to get really fancy we could run things like antiword
to generate text from non-text attachments and index their output.
2009-10-14 16:20:45 -07:00
Carl Worth
7c9dbbad40 Add label "attachment" when an attachment is seen. 2009-10-14 16:20:26 -07:00
Carl Worth
870b398726 Split thread_id value on commas before inserting into hash.
One thread_id value may have multiple thread IDs in it so we need
to separate them out before inserting into our hash.
2009-10-14 16:04:25 -07:00
Carl Worth
27c01802c8 Add missing null terminator before using byte-array contents as string.
Thanks to valgrind for spotting this one.
2009-10-14 15:55:07 -07:00
Carl Worth
7878175ed9 notmuch-index-message: Add explicit support for multipart mime.
Instead of using the recursive "foreach" method, we implement our
own recursive function. This allows us to ignore the signature
component of a multipart/signed message, (which we certainly
don't need to index).
2009-10-14 15:36:13 -07:00
Carl Worth
6363ab32ea [sup-compat] Don't trim trailing whitespace on line introducing quotation.
Ignoring this whitespace seems like a good idea to me, but it's
interfering with my comparisons with sup since sup doesn't do this.

This might be a commit worth dropping in the future since it exists
only for pedantic consistency with sup and not for any reason of its
own.
2009-10-14 14:06:06 -07:00
Carl Worth
736bad40ac notmuch-index-message: Fix handling of thread_id terms.
We now emit one term per thread_id, rather than the comma-separated
super-term we were doing previously.
2009-10-14 14:00:10 -07:00
Carl Worth
535b14dcba notmuch-index-message: Use local-part of email addres in lieu of name.
If there's no name given, take the portion of the email addres
before the '@' sign.

One step closer to matching sup's terms in the database.
2009-10-14 13:47:18 -07:00
Carl Worth
be72bf3070 Use gmime's own reference-parsing code.
Here's another instance where I "knew" gmime must have support for
some functionality, but not finding it, I rolled my own. Now that
I found g_mime_references_decode I'm glad to drop my ugly code.
2009-10-14 13:30:33 -07:00
Carl Worth
1c63ec7031 notmuch-index-message: Correctly parse and index encoded mime parts.
This cleans up some old code that was very ugly, (separately opening
the mail file and seeking to the end of the headers to parse the
body). I knew gmime must have had support for transparently decoding
mime content, but I just couldn't find it previously.

Note: Multipart and MultipartSigned parts are not handled yet.

Things are quite happy now. The few differences I see with sup are:

1. sup forces email address domains to lowercase, (I don't think I care)

2. sup and notmuch disagree on ordering of multiple thread_id values
   (another thing that's of no concern)

We are still doing one thing wrong when a message belongs to multiple
threads. We've got a nice comma-separated thread-value just like sup,
but then we're also putting in a comma-separated thread-term where
sup does multiple thread terms. That should be an easy fix.

Beyond that, sup and notmuch are still disagreeing on the term lists
for some messages, (I think attachment vs. inline content-disposition
is at least one piece of this). But there are likley still differences
in the heuristics for which chunks of the message body to index. I'll
be looking into this more.
2009-10-14 13:29:52 -07:00
Carl Worth
9ab2447e89 notmuch-index-message: Lookup children for thread_id as well.
This provides the thread_id linkage for when a child message is
indexed before the parent.
2009-10-14 10:34:05 -07:00
Carl Worth
ed320cb45b notmuch-index-message: Use more meaningful variable names.
The abuse of the generic "value" name was getting very hard to read.
2009-10-14 09:57:59 -07:00
Carl Worth
7d1227c4a8 notmuch-index-message: Start generating correct thread_id values.
Currently we're looking up all parents (based on In-reply-to and
References header) and using the list of all thread_id values
from those as our thread_id value. We're missing one step which
sup does which is to also look up any children in the database
that have reference our message ID. So we'll need to do that next.
2009-10-14 09:54:05 -07:00
Carl Worth
5cbdcbbec5 Factor out parsing of reference-header values and pickup In-reply-to.
This is in preparation for doing a couple of passes over the references,
(one to add terms to the database, and a second to find the thread_id).

We also now parse the In-reply-to header which we were missing before.
We treat it identically to the References header.
2009-10-14 08:02:27 -07:00
Carl Worth
09f765ce18 notmuch-index-message: Ignore more signature patterns.
Getting more sup-compatible all the time.
2009-10-14 07:24:28 -07:00
Carl Worth
c0da89a8e0 notmuch-index-message: Avoid crashing when a message has no references.
It's obviously an innocent-enough message, and the right thing is
so easy to do.
2009-10-13 21:15:12 -07:00
Carl Worth
3922bb4cfd notmuch-index-message: Read message filenames from stdin
This allows for indexing an arbitrary number of messages with a
single invocation rather than just a single message on the command
line.
2009-10-13 21:15:07 -07:00
Carl Worth
3253954233 Move index_file out from main() into its own function.
This is a step toward having a program that will index many messages
with a single invocation.
2009-10-13 21:15:06 -07:00
Carl Worth
c4812dae16 notmuch-index-message: Index References as well.
We're basically matching sup now! (As long as one uses sup with my
special notmuch_index.rb file).
2009-10-13 21:15:01 -07:00
Carl Worth
dceb501e44 Minor code re-ordering for clarity.
Pull the "constant" source_id value out from among several calls
that set a value based on the Message ID.
2009-10-13 21:15:00 -07:00
Carl Worth
1479b99b50 notmuch-index-message: Don't index the "re:" prefix in subjects.
Getting closer to sup results all the time.
2009-10-13 21:14:55 -07:00
Carl Worth
9bf3cda34c notmuch-index-message: Don't index the line introducing a quote.
We identify it based on a trailing ':' on the line before a quote
begins.

At this point the database-dump diff between sup and notmuch is
getting very, very small, (at least for our one test message).
2009-10-13 21:14:50 -07:00
Carl Worth
048b8aec11 notmuch-index-message: Don't index quoted lines and signatures.
At this point, we're achieving a result that is *very* close to
what sup does. The only difference is that we are still indexing
the "excerpts from message ..." line, and we are not yet indexing
references.
2009-10-13 21:14:44 -07:00
Carl Worth
9dbb1facfb notmuch-index-message: Separate gen_terms_body into its own function
This one is complex enough to deserve its own treament.
2009-10-13 21:14:33 -07:00
Carl Worth
f69215d41f notmuch-index-message: Add code to actually create a Xapian index
Most of this code is fairly clean and works well. One part is
fairly painful---namely extracting the body of an email message
from libgmime. Currently, I'm just extracting the offset to
the end of the headers, and then separately opening the message.
Surely there's a better way.

Anyway, with that the results are looking very similar to sup-sync
now, (as verified by xapian-dump). The only substantial difference
I'm seeing now is that sup does not seem to index quoted portions
of messages nor signatures. I'm not actually sure whether I want
to follow sup's lead in that or not.
2009-10-13 15:59:57 -07:00
Carl Worth
c55c34f4a0 Rename g_mime_test to notmuch-index-message
In preparation for actually creating a Xapian index from the
message, (not that we're doing that quite yet).
2009-10-13 13:31:17 -07:00
Carl Worth
a68a023d47 xapian-dump: Add a little mor indentation
Just to make it easier to visually identify where one document ends
and the next begins.
2009-10-13 13:21:47 -07:00
Carl Worth
1a6d88697b Include document data in the dump.
At the same time, I've started hacking up sup with a new NotmuchIndex
class in the place of the previous XapianIndex class. The new class
stores only the source_info field in the document data, (rather than
a serialized ruby hash with a bunch of data that can be found in the
original message).

Eventually, I plan to replace source_info with a relative filename for
the message, (or even a list of filenames for when multiple messages
in the database share a common message ID).
2009-10-13 13:18:32 -07:00