Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Andrew Cohen <acohen@ust.hk>
To: info-gnus-english@gnu.org
Subject: Re: nnimap gmail "A T" and "^" not working
Date: Thu, 19 May 2022 13:45:06 +0800	[thread overview]
Message-ID: <878rqym5y5.fsf@ust.hk> (raw)
In-Reply-To: <vriuleuyxmzh.fsf@gmail.com>

>>>>> "J" == JibStyle  <jibstyle209@gmail.com> writes:

    J> Andrew Cohen <acohen@ust.hk> writes:
    >> gmail's imap implementation is non-standard and the standard
    >> thread-referral search doesn't seem to work properly (I never
    >> noticed this before since most of email activity is not in
    >> gmail).

[...]

    J> Thanks for clarifying :) I am glad I did not shoot myself in the
    J> foot, as the manual specified is possible.

I tried poking around a bit more and maybe I was too hasty in blaming
gmail :)

For me, the failure of "A T" is arising because the 'references header
in the emails within a thread are not right. In particular, this header
is supposed to include most of the message-ids in the thread that the
message is aware of (e.g. if its the 4th message in a chain of replies
this header should contain the message-ids of all the prior messages; if
this list of prior messages is extremely long the spec allows dropping
part of it). But for the cases where "A T" fails this header contains
only a /single/ message-id, that of the immediate prior email. This
prevents the full thread from being found.

The most likely explanation is that the mailer used by the sender is not
adding the full references header. I assumed it was gmail that was
responsible, but a closer look at the messages on which "A T" fails
shows that they were all sent by the iphone mailer. So while I haven't
done any exhaustive testing, this is my current culprit.  But I am
curious if others are seeing the same thing. 

So  jibstyle maybe you can help with some testing? First, for the
purposes of the test can you
1. Set 'gnus-refer-thread-use-search to 'nil,
2. Enter the "[Gmail]/All Mail" group and find an article late in the
thread on which you know thread referral fails to find the full thread.
Examine the headers of this article (by typing C-g when point is on the
article in the summary buffer) and see what is in the  References
header? And what mailer was used to send the message?

For example when I do this I find the headers contain

In-Reply-To: <CAKfuin7MPjj5m@mail.gmail.com>
References: <CAKfuin7MPjj5m@mail.gmail.com>
X-Mailer: iPhone Mail (19E258)

which shows that the References header only contains the immediately
prior email's message-id but not that of any of the other messages.

Best,
Andy
-- 
Andrew Cohen



  reply	other threads:[~2022-05-19  5:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  6:14 JibStyle
2022-05-18  7:37 ` Byung-Hee HWANG
2022-05-18 19:49   ` JibStyle
2022-05-18 21:54     ` Byung-Hee HWANG
2022-05-18 16:38 ` Eric Abrahamsen
2022-05-18 20:15   ` JibStyle
2022-05-18 20:45     ` Eric Abrahamsen
2022-05-19  0:00       ` Andrew Cohen
2022-05-19  2:41         ` JibStyle
2022-05-19  5:45           ` Andrew Cohen [this message]
2022-05-19 23:19             ` JibStyle
2022-05-20  0:06               ` Andrew Cohen
2022-05-20 22:01                 ` JibStyle

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=878rqym5y5.fsf@ust.hk \
    --to=acohen@ust.hk \
    --cc=info-gnus-english@gnu.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).