Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id C10F46DE0948 for ; Sat, 13 Jun 2015 21:00:38 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.568 X-Spam-Level: X-Spam-Status: No, score=-0.568 tagged_above=-999 required=5 tests=[AWL=-0.017, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHrX6tGJwXxk for ; Sat, 13 Jun 2015 21:00:36 -0700 (PDT) Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) by arlo.cworth.org (Postfix) with ESMTPS id 7A4A76DE0350 for ; Sat, 13 Jun 2015 21:00:36 -0700 (PDT) Received: by oiha141 with SMTP id a141so41342979oih.0 for ; Sat, 13 Jun 2015 21:00:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=of166Ipb8UbhC4WLbCOO4rZNdZMbTujMfDuoYTq+Y28=; b=j0/A4immRngwmi+nxmIiXja2/rYJugoHUNX7+2J6pqQssXVNF2G2vC6qPrhTHdYgBt s8cu/Xx5ZVJojcZJC+KyHQOGqqW49f/UVr0ZEyR+lw9w6edeSH7JkXa/VgVtZ5OYx/ay l20fh+aZx5Ukdp8HsymHvdPCFfCKOc0OO0JYtrVXs0ylrw50VEHehCM/3zIXWesJXYj/ Fj7trapJwSZR6S9cv5IKAGzRlvOiDa6RKdssg8V1Hk+tKA+RqdvujrO6mF+8J0SY+pOl lTy0MpwgkPm9mosSbJzeX7UmjNahgCsmcWPyO+8QTmjzNhfBas74L57STrkOxsie9aoU towg== MIME-Version: 1.0 X-Received: by 10.182.181.103 with SMTP id dv7mr18326964obc.25.1434254435575; Sat, 13 Jun 2015 21:00:35 -0700 (PDT) Received: by 10.182.241.167 with HTTP; Sat, 13 Jun 2015 21:00:35 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Jun 2015 00:00:35 -0400 Message-ID: Subject: Re: Understanding the "replied" tag From: Xu Wang To: notmuch@notmuchmail.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jun 2015 04:00:38 -0000 Dear Suvayu and Austin, Thank you for your attempts to understand my goals. I apologize for the lack in the clarity of my previous messages. Thank you kindly for your persistence and thank you to Suvayu for suggestions on adding more information. I am indeed using mutt-kz, along with offlineimap, on Ubuntu 15.04. I have written the following information the other email thread I started (perhaps I should have added it as a reply here, but I thought it might be sufficiently a different topic). I will copy the information I gave there on my goal here: My goal is to do something like the following: notmuch search tag:reply-required and not tag:replied which was discussed here: http://notmuchmail.org/pipermail/notmuch/2010/002558.html However, instead of conditioning on tag:reply-required, I would like to look at this for a specific message. For example, if I write an important message, I can do the following: save the message id, and then in 5 days set a cron script to check whether my message was responded to. If it was not responded to I will take some action to notify myself (haven't decided what yet). It is the "If it was not responded to" part that this email thread is about. I am now realizing that I cannot use mutt's tag "replied" because I often send and read email from gmail or other IMap clients (e.g. phone). Because of this (I believe), the reply tag does not get set when it should (well not "should" but rather "when I want it to"). For example, I often have abc ->def -> ghi where the message def does not have the "replied" tag, even though it was replied to (ghi replied to it). I think the reason is what I suggested above. Yes, indeed Austin was correct about where my misunderstanding was. I do indeed want to see if *any* reply was to a certain message id, but the "replied" tag is apparently for my own replying. Because I cannot use the "replied" tag (unless I have misunderstood), I thought I could just check using the message id with 'notmuch search repliedto:', but Suvayu points out that searching for this is not supported. Kind regards, Xu On Sat, Jun 13, 2015 at 7:12 PM, Austin Clements wrote: > Hi Xu. I may be misunderstanding your email, but it sounds like you want = to know if a message has *any* reply message. That's not what the replied t= ag indicates. The replied tag indicates that *you* have sent a reply to a m= essage. Mechanically, when you hit, say, r to start a reply and then send t= hat message, notmuch tags the message you hit r on as "replied". That's the= only time notmuch automatically sets this tag. > > On June 11, 2015 10:25:44 AM PDT, Xu Wang wrote: >>Dear all, >> >>First, I am extremely excited to be a part of this list now. notmuch >>has really helped me. Thank you go all individuals working to improve >>it and to help others to know how to use it. >> >>I would really like to know if a message has been replied to (e.g. >>using a certain message id). It seems that all I need to do is check >>for the "replied" tag. But often this tag is not there, even when >>there has been a reply (I have confirmed this through the thread >>display and checking the message that replied to the message to make >>sure it indeed has header "replied-to:"). >> >>I have looked in mutt, and also I see many situations where there is >>no 'r' flag, especially for emails sent from me. >> >>The following returns true: >>notmuch config get maildir.synchronize_flags >> >>So at least both are giving same answer, but I'm not sure why not >>saying "replied" thread is correct. >> >>What is incorrect for my way of thinking about "replied"? Do I >>misunderstand what it is supposed to do or am I not updating the flags >>correctly? >> >>Kind regards, >> >>Xu >>_______________________________________________ >>notmuch mailing list >>notmuch@notmuchmail.org >>http://notmuchmail.org/mailman/listinfo/notmuch >