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 F2DC66DE0AF8 for ; Sat, 13 Jun 2015 16:17:54 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.276 X-Spam-Level: X-Spam-Status: No, score=0.276 tagged_above=-999 required=5 tests=[AWL=2.173, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.55, SPF_SOFTFAIL=0.972, UNPARSEABLE_RELAY=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 T4CoTR2pXMqa for ; Sat, 13 Jun 2015 16:17:51 -0700 (PDT) X-Greylist: delayed 300 seconds by postgrey-1.35 at arlo; Sat, 13 Jun 2015 16:17:51 PDT Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) by arlo.cworth.org (Postfix) with ESMTP id 70CB96DE0948 for ; Sat, 13 Jun 2015 16:17:51 -0700 (PDT) X-AuditID: 12074422-f79c36d000000db3-83-557cb8f0c1f2 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id C6.D5.03507.1F8BC755; Sat, 13 Jun 2015 19:12:49 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id t5DNCmYC005926; Sat, 13 Jun 2015 19:12:48 -0400 Received: from android-a7de331e64905891.n2vi.com (c-73-15-188-162.hsd1.ca.comcast.net [73.15.188.162]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t5DNCjqk025002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 13 Jun 2015 19:12:47 -0400 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: Understanding the "replied" tag From: Austin Clements Date: Sat, 13 Jun 2015 16:12:43 -0700 To: Xu Wang , notmuch@notmuchmail.org Message-ID: X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDIsWRmVeSWpSXmKPExsUixCmqrPtxR02owfO17BbXb85ktmh6uovF gclj56y77B7PVt1iDmCK4rJJSc3JLEst0rdL4MpYMucMW8EV3oqbcxYwNjB2cHcxcnJICJhI dO/bxAxhi0lcuLeerYuRi0NIYDGTxJZtu9lAEkICGxklOrZUQCSeMknM/7aEHSQhKqAgMW/y REYQm1MgUKL131wWiIYAiSv7t4A18woISpyc+QQsziwgL9G8dTYzhK0pce34FrA5wgI6EpvO fQGLswnoS6xYO4kVxGYRUJU4NvsKWI2IgJXEqesvWCFmOkj0317EOoFRYBaSFbOQrJiFZMUC RuZVjLIpuVW6uYmZOcWpybrFyYl5ealFuqZ6uZkleqkppZsYQYHK7qK0g/HnQaVDjAIcjEo8 vA4ba0KFWBPLiitzDzFKcjApifJG7qkOFeJLyk+pzEgszogvKs1JLT7EKMHBrCTC+6IXqJw3 JbGyKrUoHyYlzcGiJM676QdfiJBAemJJanZqakFqEUxWhoNDSYL34HagRsGi1PTUirTMnBKE NBMHJ8hwHqDhUjtAhhcXJOYWZ6ZD5E8xKkqJ864GaRYASWSU5sH1whLJK0ZxoFeEeVeCVPEA kxBc9yugwUxAg9t7qkAGlyQipKQaGBcIPq1u/zhNXYLvh8KyCQ/6i6uaPHTW7znsOdH3L+cK FUfNsIjoOU6VivLb5U5Pk+qfn7d+Ssl2c+U1t4un7g3JqSm+s3ll0jvvGxHu2998mlYyL3Jz 3IPa5+vyTrr6p/99fcL5Zs/FXe2W5z9ZOC16Lqz45XjnqqXdNy3maxmLv50kyDVLQ1iJpTgj 0VCLuag4EQD7St+u/wIAAA== 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: Sat, 13 Jun 2015 23:17:55 -0000 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 tag indicates. The replied tag indicates that *you* have sent a reply to a message. Mechanically, when you hit, say, r to start a reply and then send that 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