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.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27853 invoked from network); 19 May 2021 15:57:17 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 19 May 2021 15:57:17 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1ljOZO-003lej-Pd for ml@inbox.vuxu.org; Wed, 19 May 2021 10:57:14 -0500 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94) (envelope-from ) id 1ljOZO-00F3iE-84 for ml@inbox.vuxu.org; Wed, 19 May 2021 10:57:14 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1ljOZM-00F3i6-2f for ding@lists.math.uh.edu; Wed, 19 May 2021 10:57:12 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1ljOZK-002i4p-1A for ding@lists.math.uh.edu; Wed, 19 May 2021 10:57:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References :Message-ID:Date:Subject:From:To:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=1kJG9BuYsXqwUh6EqiQDifEdY7hoJcHgq4FIU0Mezjg=; b=NKfjbUSmyr9GB/3fHHhQxk3OXd xKODsuR+oi2JZD4VdL2PSFt5QkmGOR0t1tyMlj9xMOzbIr9e1BIzfvZNkND6qIntLX5+0gTGl6naQ nOEmiAoo3PVigDw9RMSqhLLot6W4FY2HJ55EfvXciCT4Pmc38MECR0lrighXrvKXwFu8=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ljOZC-00068s-R9 for ding@gnus.org; Wed, 19 May 2021 17:57:05 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1ljOZB-0001Y9-Kz for ding@gnus.org; Wed, 19 May 2021 17:57:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: How to view sent mails in a threaded conversation (IMAP)? Date: Wed, 19 May 2021 08:56:38 -0700 Message-ID: <87wnruu37t.fsf@ericabrahamsen.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cancel-Lock: sha1:f67slrwWqXDDUSeGCW7u37ujQcM= List-ID: Precedence: bulk Pankaj Jangid writes: > Some mail providers give control to us. But some of them keep sent > emails in a separate folder, often called ‘Sent Items’. > > In the first case, we can configure the ‘Gcc’ header via gcc-self > gnus-parameter. > > In the 2nd case, where sent-emails are already stored in ‘Sent Items’, > if I don’t want to store a redundant copy, what is the proper way to > keep threads intact, at least in view? > > Some mail providers are even more notorious. Even if I keep a redundant > copy of a sent-email in my folder of choice (‘Inbox’), they remove it > from there after sometime; probably after matching Message-ID etc. > > I want to know what do Gnus users generally do to solve this. I > understand that it is not necessary to keep it that way > i.e. threaded. And my basic problem is not threaded conversations. The > main problem is search and looking messages in context. So, if I can > view all the messages in an ephemeral group then that would also solve > my problem. In fact, that would encourage me to keep sent emails in a > different folder instead of ‘Inbox’. If you're willing to use ephemeral/search groups as a solution, the easiest thing by far would be to use an nnselect group. You could either mark INBOX and Sent and do a search like "since:2w", or not go the search route and just have the group hold all messages from both source groups -- I don't think there should be any particular performance penalty for doing that, so long as you're displaying a subset of articles, like usual.