From: Ted Zlatanov <tzz@lifelogs.com>
To: Jake Colman <colman@ppllc.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Problems with gnus-registry
Date: Tue, 05 Feb 2008 09:15:03 -0600 [thread overview]
Message-ID: <86abmfv3ig.fsf@lifelogs.com> (raw)
In-Reply-To: <764pconmz4.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Mon, 04 Feb 2008 21:41:51 -0500")
On Mon, 04 Feb 2008 21:41:51 -0500 Jake Colman <colman@ppllc.com> wrote:
Jake> I believe that my correspondent's email is processed via a really old version
Jake> of MS Exchange Server. I'm wondering if the old Exchange Servers did not act
Jake> as a proper MUA. We'll be upgrading our Exchange Server in the next few
Jake> weeks so we'll see if that helps.
I don't know how Exchange does references, sorry... You see the
problem: only sender/subject tracking can help you if there are no
references. I think Exchange has some sort of thread ID mechanism, but
I didn't see it in the message you forwarded. cc-ing ding in case
someone has ideas.
Ted
next prev parent reply other threads:[~2008-02-05 15:15 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
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 [this message]
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=86abmfv3ig.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=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).