[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reply to list [was: Different key maps in different dired buffers]

From: Dmitry Alexandrov
Subject: Re: Reply to list [was: Different key maps in different dired buffers]
Date: Sun, 5 Jun 2016 15:44:36 +0300
User-agent: Mozilla/5.0 (X11; GNU x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0

On 04/06/16 22:41, Bob Proulx wrote:
Yes.  I have tried to determine why this is before.  I don't think it
is on Emanuel's end.

I did not imply it either, of course.  However, if the problematic
software or service might be avoided, it’d better be avoided, I believe.
But it have to be found first, of course.

Details follow

Good investigation. :-)

There is no In-Reply-To on the follow-up.  Only the References header
can be used for threading.  Checking through the references in the
place of my message address@hidden I see
address@hidden instead.  That
appears to be the point where threading gets broken.  Something
appears to have converted one message id into another one.


Again Gnus and News.  Can't tell.

Ah!  Here is one.  Another example of a broken mail link.


  From: Eli Zaretskii <address@hidden>
  Message-Id: <address@hidden>
  References: <address@hidden>


  From: Vladimir Panteleev <address@hidden>
  Message-ID: <address@hidden>
  References: <address@hidden>
  In-Reply-To: <address@hidden>
  User-Agent: G2/1.0

What User-Agent is represented by "G2/1.0"?

From the ‘Path’ header I can guess that this is Google Groups web
interface [0].


Since that isn't Gnus it would seem to let Gnus off the hook.  The
commonality is the Stanford news gateway.  The converted message id is
of the same form.  Looks to be the same problem.  Does not include
Gnus so seems to implicate the Stanford newsgroup gateway.

I’ll try to post this message to ‘‘ via a proper news
server ( and not with Gnus, let see what will happen.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]