From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FORGED_GMAIL_RCVD,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25558 invoked from network); 20 May 2022 22:01:26 -0000 Received: from lists.gnu.org (209.51.188.17) by inbox.vuxu.org with ESMTPUTF8; 20 May 2022 22:01:26 -0000 Received: from localhost ([::1]:59580 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nsAgW-0002di-0K for ml@inbox.vuxu.org; Fri, 20 May 2022 18:01:24 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45942) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsAgM-0002cC-To for info-gnus-english@gnu.org; Fri, 20 May 2022 18:01:16 -0400 Received: from ciao.gmane.io ([116.202.254.214]:54044) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsAgL-0004Mr-Ax for info-gnus-english@gnu.org; Fri, 20 May 2022 18:01:14 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nsAgI-0009jj-4l for info-gnus-english@gnu.org; Sat, 21 May 2022 00:01:10 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: info-gnus-english@gnu.org From: JibStyle Subject: Re: nnimap gmail "A T" and "^" not working Date: Fri, 20 May 2022 15:01:00 -0700 Message-ID: References: <877d6ire2k.fsf@ericabrahamsen.net> <87r14qo9hi.fsf@ericabrahamsen.net> <87r14qmlwj.fsf@ust.hk> <878rqym5y5.fsf@ust.hk> <87pmk9f4om.fsf@ust.hk> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (cygwin) Cancel-Lock: sha1:3jihyz2vlQ3AW9LHAWTs2L/HPW8= Received-SPF: pass client-ip=116.202.254.214; envelope-from=gegu-info-gnus-english@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 5 X-Spam_score: 0.5 X-Spam_bar: / X-Spam_report: (0.5 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: info-gnus-english-bounces+ml=inbox.vuxu.org@gnu.org Sender: "info-gnus-english" Andrew Cohen writes: >>>>>> "J" == JibStyle 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: --8<---------------cut here---------------end--------------->8--- ChildArticle (this is where I initiate search from) --8<---------------cut here---------------start------------->8--- References: In-Reply-To: Message-ID: --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: --8<---------------cut here---------------end--------------->8--- ChildA (this is where I initiate search from) --8<---------------cut here---------------start------------->8--- References: In-Reply-To: Message-ID: --8<---------------cut here---------------end--------------->8--- GrandchildA (not found) --8<---------------cut here---------------start------------->8--- References: In-Reply-To: Message-ID: --8<---------------cut here---------------end--------------->8--- ChildB (not found) --8<---------------cut here---------------start------------->8--- References: In-Reply-To: Message-ID: --8<---------------cut here---------------end--------------->8--- GrandchildB (not found) --8<---------------cut here---------------start------------->8--- References: In-Reply-To: Message-ID: --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.