From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: registry subject tracking problem
Date: Fri, 08 Feb 2008 11:09:43 -0500 [thread overview]
Message-ID: <76prv7v394.fsf@dev-d01.ppllc.com> (raw)
I've referenced this problem already elsewhere but it was buried inside
of a much larger thread. I'm raising it again in its own thread and
providing more data.
I just upgraded to No Gnus 0.7 so I am using the latest code as of this
week.
I sent an email from a folder with gcc-self specified. I received a
reply to that email but the reply was not filed correctly by the
registry. Ted has already help me determine that the emails that I am
getting are missing the typical headers used by the registry (they are
coming through an old version MS Exchange Server which is probably
stripping the headers) which is why I need to work harder to get the
message traced properly. So I have turned on the registry's extra
tracking by subject.
The initial message's headers are as follows:
===========================================================
To: is@ppllc.com
Subject: Build Issue with XRT Licensing
X-Attribution: Jake
X-URL: http://www.ppllc.com
X-Draft-From: ("nnimap+hamilton:INBOX/Principia/IS_Issues" "")
From: Jake Colman <colman@ppllc.com>
Date: Thu, 07 Feb 2008 14:35:20 -0500
Message-ID: <76zluc8sqv.fsf@dev-d01.ppllc.com>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.17 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
===========================================================
I find the following entry is .gnus.registry.eld:
("<76zluc8sqv.fsf@dev-d01.ppllc.com>" ((mtime 18347 34824 532917) (sender . "Jake Colman <colman@ppllc.com>") (subject . "Build Issue with XRT Licensing")) "INBOX/Principia/IS_Issues")
The email sent in reply, has the following headers:
===========================================================
Received: by hamilton.ppllc.com
id <01C86A60.3AF26D30@hamilton.ppllc.com>; Fri, 8 Feb 2008 09:38:11 -0500
Message-ID: <0B72769B5EA61E45BFDAB9B849923FE703359C09@hamilton.ppllc.com>
From: Mark Vosteen <vosteen@ppllc.com>
To: Jacob Colman <colman@ppllc.com>
Subject: RE: Build Issue with XRT Licensing
Date: Fri, 8 Feb 2008 09:38:11 -0500
MIME-Version: 1.0
Content-Type: text/plain
===========================================================
I manually moved this email where I had hoped the registry would file
it. I now find the following entry in .gnus.registry.eld (which,
incidentally, appears earlier in the list than the first one):
("<0B72769B5EA61E45BFDAB9B849923FE703359C09@hamilton.ppllc.com>" ((mtime 18348 30274 550938) (sender . "Mark Vosteen <vosteen@ppllc.com>") (subject . "Build Issue with XRT Licensing")) "INBOX/Principia/IS_Issues")
The problem is that if I execute (message-fetch-field "subject") on
these two messages, I get different results.
For the first message I get:
"Build Issue with XRT Licensing"
For the second message I get:
"RE: Build Issue with XRT Licensing, Build Issue with XRT Licensing"
Would this discrepency explain why my message did not get filed
correctly?
TIA!
...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
next reply other threads:[~2008-02-08 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:09 Jake Colman [this message]
2008-02-15 20:19 ` Ted Zlatanov
2008-02-15 21:01 ` Jake Colman
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=76prv7v394.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).