From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: GMail injects fake Message-IDs
Date: Tue, 19 Jul 2011 17:54:52 -0400 [thread overview]
Message-ID: <m2ipqyx7f7.fsf@boostpro.com> (raw)
In-Reply-To: <m3d3h6p5sn.fsf@quimbies.gnus.org>
on Tue Jul 19 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> In attempting to figure out why `gnus-summary-refer-parent-article' was
>> so often failing to find the root article of my mail threads, I looked
>> carefully and saw that GMail generates some kind of fake message-ID. These
>> headers appeared in the 2nd message of a thread:
>> In-Reply-To: <CAEOvpkmO5SGPdbqUrUgyi0LSPZyCQU2JfJpwUDq0EEuZn6B8OQ@mail.gmail.com>
>> References: <m2d3ho45ip.fsf@pluto.luannocracy.com>
>> <CAEOvpkmO5SGPdbqUrUgyi0LSPZyCQU2JfJpwUDq0EEuZn6B8OQ@mail.gmail.com>
>> Message-ID: <CAEOvpknPA15TgaGXTSb-pHK7amvX8Jr9WrjFZ=bv8upAxdBBWA@mail.gmail.com>
>> The first message of the thread was
>> <m2d3ho45ip.fsf@pluto.luannocracy.com>. As far as the thread
>> participants are concerned,
>> <CAEOvpkmO5SGPdbqUrUgyi0LSPZyCQU2JfJpwUDq0EEuZn6B8OQ@mail.gmail.com>
>> never existed. Is there something Gnus can do to work around this oddity?
>
> Gmail inserted a Message-ID that never existed into the References
> header? That sounds very odd.
Perhaps this is a result of Bcc'ing myself?
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-07-19 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 4:53 Dave Abrahams
2011-07-19 16:57 ` Lars Magne Ingebrigtsen
2011-07-19 21:54 ` Dave Abrahams [this message]
2011-07-19 22:18 ` Lars Magne Ingebrigtsen
2011-07-23 15:32 ` Dave Abrahams
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=m2ipqyx7f7.fsf@boostpro.com \
--to=dave@boostpro.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).