Subject: Re: PC-Pine, Exchange IMAP Server, & Message-ID problem

From: Nancy McGough <[email-masked]>
Date: Wed, 10 Jan 2001 22:52:40 +0000 (GMT)

On 10 Jan 2001, Nancy McGough ([email-masked]) wrote:
> On 10 Jan 2001, Nancy McGough ([email-masked]) wrote:
> > I'm going to demonstrate a problem with PC-Pine, an Exchange IMAP
> > server, and the Message-ID header by sending this message and
> > then responding to it. I'll then explain the problem...
>
> The message that I'm replying to, which is excerpted above, is
> sitting in a folder on an MS Exchange IMAP server. The message
> was moved into the folder by a Pine filter.
>
> In the next message I'll describe the problem (assuming it
> happens).

The problem did happen so you won't all think I'm nuts! Message 1
included these headers:

 Message-Id: <Pine.WNT.4.31.9.0101102135320.-245525@no>
 Date: Wed, 10 Jan 2001 21:40:42 +0000 (GMT)
 From: Nancy McGough <[email-masked]>
 To: Pine Discussion Forum <[email-masked]>
 Subject: PC-Pine, Exchange IMAP Server, & Message-ID problem

Message 2, which was my reply to Message 1, included these
headers:

 Message-Id: <Pine.WNT.4.31.9.0101102205550.-245525@no>
 Date: Wed, 10 Jan 2001 22:13:46 +0000 (GMT)
 From: Nancy McGough <[email-masked]>
 To: Pine Discussion Forum <[email-masked]>
 Subject: Re: PC-Pine, Exchange IMAP Server, & Message-ID problem
 In-Reply-To: <[email-masked]>

The problem is the In-Reply-To header in Message 2 -- it *should*
say:

 In-Reply-To: <Pine.WNT.4.31.9.0101102135320.-245525@no>

where this part ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is the Message-ID of Message 1 but instead it has a Message-ID
that seems to have been generated by ICEX6 (Imperial College
Exchange Server). This is a problem for people who are trying to
follow a thread using a threaded newsreader (which Pine can do
now too thanks to the new $H sort-by-thread command).

I posted some more details about this bug back in November in
comp.mail.pine. You can read that thread here:

http://x64.deja.com/%5BST_rn=ap%5D/viewthread.xp?AN=695100007&search=thread&svcclass=dnserver&ST=PS&CONTEXT=979166439.286392416&HIT_CONTEXT=979166439.286392416&HIT_NUM=10&recnum=%3cPine.WNT.4.30.9.0011181433100.-361455@no%3e%231/1&group=comp.mail.pine&frpage=viewthread.xp&back=clarinet

It would be great if this could be fixed in the next release of
Pine.

Thanks,
Nancy

-- 
For Pine links, see http://www.ii.com/internet/messaging/pine/

Nancy McGough          http://www.ii.com          Infinite Ink
=-- Sent via PINE 4.31: Internet News & Email for Win/Unix --=

---

From: Eduardo Chappa <[email-masked]>
Date: Wed, 10 Jan 2001 17:12:31 -0800 (PST)

*** Nancy McGough ([email-masked]) wrote in the...:

:) It would be great if this could be fixed in the next release of
:) Pine.

It's not clear to me why you think it is a problem with Pine. Pine gets
the value of the headers from the server, so I do not see what Pine can do
about it. The message-id in the in-reply-to header was certainly not
generated by Pine. I certainly don't have that problem with the same
version of Pine. In my opinion you are reporting the bug in the wrong
place. Maybe you should report it to the imap mailing list or
comp.mail.imap or the designer of the IMAP server you are using.

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/