Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: Re: registry subject tracking problem
Date: Fri, 15 Feb 2008 16:01:56 -0500	[thread overview]
Message-ID: <76pruygchn.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <86tzka3rcs.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 15 Feb 2008 14:19:15 -0600")

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

   TZ> On Fri, 08 Feb 2008 11:09:43 -0500 Jake Colman <colman@ppllc.com> wrote: 

   Jake> The initial message's headers are as follows:
   Jake> Subject: Build Issue with XRT Licensing
   Jake> I find the following entry is .gnus.registry.eld:
   Jake> ("<76zluc8sqv.fsf@dev-d01.ppllc.com>" ((mtime 18347 34824 532917)
   Jake> (sender . "Jake Colman <colman@ppllc.com>") (subject . "Build Issue
   Jake> with XRT Licensing")) "INBOX/Principia/IS_Issues")

   Jake> The email sent in reply, has the following headers:
   Jake> Subject: RE: Build Issue with XRT Licensing

   Jake> I manually moved this email where I had hoped the registry would file
   Jake> it.  I now find the following entry in .gnus.registry.eld (which,
   Jake> incidentally, appears earlier in the list than the first one):

   Jake> ("<0B72769B5EA61E45BFDAB9B849923FE703359C09@hamilton.ppllc.com>"
   Jake> ((mtime 18348 30274 550938) (sender . "Mark Vosteen
   Jake> <vosteen@ppllc.com>") (subject . "Build Issue with XRT Licensing"))
   Jake> "INBOX/Principia/IS_Issues")

   Jake> The problem is that if I execute (message-fetch-field "subject") on
   Jake> these two messages, I get different results.

   Jake> For the first message I get:

   Jake> "Build Issue with XRT Licensing"

   Jake> For the second message I get:

   Jake> "RE: Build Issue with XRT Licensing, Build Issue with XRT Licensing"

   TZ> Strange, I get only the original subject (with RE:, but that's removed
   TZ> in the registry by gnus-simplify-subject).  I don't know why the subject
   TZ> is not retrieved properly from the second e-mail.  You must have called
   TZ> message-fetch-field in a strange context.

   TZ> In any case, note that the subject was extracted properly for the second
   TZ> message since the registry entry has the right subject.  So from now on,
   TZ> messages with that subject should go to "INBOX/Principia/IS_Issues".

   TZ> Can you grep the registry file for "Build Issue with XRT Licensing" and
   TZ> see if it shows up in any other groups?  That would be a reason why the
   TZ> followup didn't go to the right place.

   TZ> I'll do the logging improvements we discussed earlier.  Sorry for the
   TZ> delay, but I've been too busy with a new baby :)

   TZ> Ted

Ted,

I grepped the registry and all relevant entries contain the correct
subject and the correct target group.  And I agree that the registry got
it right yet it didn't trace it correct anyway!

Let me know when the new logging improvements are ready and I'll try
them out.  For my purposes, since so many messages don't get filed
correctly, a debug option that shows me what you know about the message
and how you traced it would be very helpful.

Thanks.

...Jake

P.S. Congrats on the new baby.  We have 6 of our own!

-- 
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-15 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 16:09 Jake Colman
2008-02-15 20:19 ` Ted Zlatanov
2008-02-15 21:01   ` Jake Colman [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=76pruygchn.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).