From: JibStyle <jibstyle209@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: nnimap gmail "A T" and "^" not working
Date: Fri, 20 May 2022 15:01:00 -0700 [thread overview]
Message-ID: <vriubkvr3lur.fsf@gmail.com> (raw)
In-Reply-To: <87pmk9f4om.fsf@ust.hk>
Andrew Cohen <acohen@ust.hk> writes:
>>>>>> "J" == JibStyle <jibstyle209@gmail.com> writes:
>
> J> - Issue1: Grandparent not found when only one "References" entry.
>
> There is little we can do about this---if the references header doesn't
> contain the right information we can't know what messages to fetch
> (while we could "walk" up the tree this isn't practical, since we would
> have to construct a separate search and a new network connection for
> each step). And not adding the references is broken behavior and should
> be fixed by the mailer.
Fair enough. In this case, I can walk up the tree manually.
> J> - Issue2: Parent from different group not found.
>
> This is the intended behavior. If you want messages from different
> groups to be found you need to set 'gnus-refer-thread-use-search to 't.
I set 'gnus-refer-thread-use-search to 't but still encounter the issue.
ParentArticle (this is the article not found)
--8<---------------cut here---------------start------------->8---
Message-ID: <vriuk0ahi2g9.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
ChildArticle (this is where I initiate search from)
--8<---------------cut here---------------start------------->8---
References: <vriuk0ahi2g9.fsf@gmail.com>
In-Reply-To: <vriuk0ahi2g9.fsf@gmail.com>
Message-ID: <vriuczg9i2dz.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
> J> - Issue3: Siblings and descendants not found.
>
> This doesn't happen for me. As far as I can tell "A T" search is working
> correctly in gmail when the references header is correct. The gnus
> strategy is simple: when you type "A T" on a message the message-id of
> that message and ALL message-ids in the references header are used as
> search keys. The search asks for all messages whose references header
> contains any one of those keys. For mailers that adhere to the standard
> this will find all articles in the thread, future and past.
See my below email header data. For this test, I initiated search from
the "[Gmail]/All Mail", in which all the emails exist. These results are
with 'gnus-refer-thread-use-search nil -- alarmingly, when the variable
is t, "A T" does not find any articles at all.
RootArticle (successfully found)
--8<---------------cut here---------------start------------->8---
Message-ID: <vriuk0ahi2g9.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
ChildA (this is where I initiate search from)
--8<---------------cut here---------------start------------->8---
References: <vriuk0ahi2g9.fsf@gmail.com>
In-Reply-To: <vriuk0ahi2g9.fsf@gmail.com>
Message-ID: <vriuczg9i2dz.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
GrandchildA (not found)
--8<---------------cut here---------------start------------->8---
References: <vriuk0ahi2g9.fsf@gmail.com> <vriuczg9i2dz.fsf@gmail.com>
In-Reply-To: <vriuczg9i2dz.fsf@gmail.com>
Message-ID: <vriu4k1li2cn.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
ChildB (not found)
--8<---------------cut here---------------start------------->8---
References: <vriuk0ahi2g9.fsf@gmail.com>
In-Reply-To: <vriuk0ahi2g9.fsf@gmail.com>
Message-ID: <vriu8rqxi2dl.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
GrandchildB (not found)
--8<---------------cut here---------------start------------->8---
References: <vriuk0ahi2g9.fsf@gmail.com> <vriu8rqxi2dl.fsf@gmail.com>
In-Reply-To: <vriu8rqxi2dl.fsf@gmail.com>
Message-ID: <vriuzgjdgnrs.fsf@gmail.com>
--8<---------------cut here---------------end--------------->8---
> To diagnose further you will need to do what I asked you earlier: find
> the references header, the in-reply header, and the original message-id
> header for the initiating article and for the article that wasn't found.
Thanks for your help. It sounds like I'm the only one experiencing these
issues, and I wonder if I may have incorrectly configured
something. Please let me know if any suggestions come to mind, and I'll
continue referencing the manual, emacswiki, and experimenting. Best
regards.
prev parent reply other threads:[~2022-05-20 22:01 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
2022-05-19 23:19 ` JibStyle
2022-05-20 0:06 ` Andrew Cohen
2022-05-20 22:01 ` JibStyle [this message]
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=vriubkvr3lur.fsf@gmail.com \
--to=jibstyle209@gmail.com \
--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).