Re: Problems with gnus-registry

[Ted Zlatanov <tzz@lifelogs.com>]

On Mon, 04 Feb 2008 08:38:31 -0500 Jake Colman <colman@ppllc.com> wrote: 

>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> this looks OK.  Can you send me your registry contents for a
TZ> particular message that didn't get split properly, and the message
TZ> itself?  Also the stuff in *messages* (make sure you increase
TZ> gnus-verbose before you run it) printed by the registry would be
TZ> helpful.

Jake> I apologize for following up my own email.

Jake> I just ran a controlled test.  I manually moved the incorrectly filed email
Jake> into its correct group.  That resulted in the following entry made to
Jake> .gnus.registry.eld:

Jake> ("<0B72769B5EA61E45BFDAB9B849923FE703359839@hamilton.ppllc.com>" ((mtime 18343 4695 975321)) "INBOX/Principia/PM-295-296")))

Jake> I replied to that email and waited for a reply to come back.  When it did, my
Jake> Message-Log shows:

Jake> nnimap: Fetching (part of) article 850672 from INBOX...
Jake> nnimap: Fetching (part of) article 850672 from nil...done
Jake> gnus-registry-split-fancy-with-parent traced nil to group nil
Jake> IMAP split moved hamilton:INBOX:850672 to INBOX/Principia

Jake> That is the email that should have been traced to
Jake> "INBOX/Principia/PM-295-296".

The parent message is known, then.  By the way, you can always run

M-: (gnus-registry-split-fancy-with-parent)

in a buffer showing the original article (I forget, you may have to hit
`t' to show all the headers).  The result of that command is what the
registry will say at splitting time, so you don't have to wait for a
mail reply to arrive to test things :) Right now it's probably returning
nil (which passes control to the next splitting rule); please test if
that's true.

Next, try running

M-: (message-fetch-field "references")
M-: (message-fetch-field "in-reply-to")

in a buffer showing the article you mention.  That will show the
references we know in this article.  It should return something.  Those
references are what we use to track the parent of the article (in
addition to the subject and the sender, if you turn those on in the
registry settings; see gnus-registry-track-extra).  Without references
we can't do anything, so if they are missing we need to fix that.

Next, if there are references, do

M-: (gnus-extract-references (message-fetch-field "references"))

which should give you the list of referenced message IDs.  Is one of
them in the registry?

It would be great if you could attach the message itself.  Send it to me
privately if you prefer.

Ted