Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Problems with gnus-registry
Date: Mon, 04 Feb 2008 08:38:31 -0500	[thread overview]
Message-ID: <76tzkoq1t4.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <86k5loxulw.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 01 Feb 2008 14:57:47 -0600")

>>>>> "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.

I apologize for following up my own email.

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

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

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

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

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

What other information can I provide you?

...Jake

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com



  reply	other threads:[~2008-02-04 13:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:21 Jake Colman
2008-02-01 20:57 ` Ted Zlatanov
2008-02-04 13:38   ` Jake Colman [this message]
2008-02-04 21:03     ` Ted Zlatanov
     [not found]       ` <76y7a0nyo3.fsf@dev-d01.ppllc.com>
     [not found]         ` <86lk60uwwq.fsf@lifelogs.com>
     [not found]           ` <764pconmz4.fsf@dev-d01.ppllc.com>
2008-02-05 15:15             ` Ted Zlatanov
2008-02-05 21:51               ` Jake Colman
2008-02-05 22:15                 ` Ted Zlatanov
2008-02-05 22:24                   ` Jake Colman
2008-02-06 14:21                     ` Ted Zlatanov
2008-02-06 16:54                       ` Jake Colman
2008-02-06 17:31                         ` Ted Zlatanov
2008-02-07 15:42                           ` Jake Colman
2008-02-06 20:05                       ` Reiner Steib
2008-02-07 15:43                         ` Ted Zlatanov
2008-02-07 17:29                           ` Reiner Steib
2008-02-08 11:58                             ` David
2008-02-14 17:51                               ` Ted Zlatanov
2008-02-28 15:01                                 ` Ted Zlatanov
2008-02-28 15:53                                   ` David
2008-02-14 17:45                             ` Ted Zlatanov
2008-02-28 15:03                               ` Ted Zlatanov

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=76tzkoq1t4.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.com \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.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).