From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id D8E87431FD8 for ; Sun, 28 Oct 2012 08:31:43 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QECzeTWj3t5m for ; Sun, 28 Oct 2012 08:31:43 -0700 (PDT) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by olra.theworths.org (Postfix) with ESMTP id 1F018431FAF for ; Sun, 28 Oct 2012 08:31:43 -0700 (PDT) X-AuditID: 12074425-b7fcc6d00000091f-0d-508d4fde5330 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 61.11.02335.EDF4D805; Sun, 28 Oct 2012 11:31:42 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id q9SFVfxT018344; Sun, 28 Oct 2012 11:31:41 -0400 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q9SFVd6L007089 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sun, 28 Oct 2012 11:31:40 -0400 (EDT) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1TSUpu-0000Sk-Vt; Sun, 28 Oct 2012 11:31:39 -0400 Date: Sun, 28 Oct 2012 11:31:38 -0400 From: Austin Clements To: Andrei POPESCU Subject: Re: [PATCH 0/2] automatic tagging based on imap maildir Message-ID: <20121028153138.GB15377@mit.edu> References: <1351208039-32293-1-git-send-email-taesoo@mit.edu> <20121026171024.30658.84119@localhost> <877gqc7s67.fsf@zancas.localnet> <20121027044128.GB12051@taesoo.org> <87vcdw5atd.fsf@zancas.localnet> <20121028100324.GF6431@sid.nuvreauspam> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121028100324.GF6431@sid.nuvreauspam> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHKsWRmVeSWpSXmKPExsUixCmqrHvPvzfA4P8ieYtVE6QtbrR2M1pc vzmT2WLKl/eMDiweO2fdZfd4tuoWs8eWQ++ZA5ijuGxSUnMyy1KL9O0SuDJmzFnDUnBRsGL7 2ddMDYw/eLsYOTkkBEwkerdfYYKwxSQu3FvP1sXIxSEksI9R4t6JfkYIZwOjxPOjUxhBqoQE TjJJrD4iAJFYwihxd9pPsASLgKrE1NMLwGw2AQ2JbfuXg9kiAroSna8OgK1gFsiQ2Nf0mwXE FhZwkFi/cjs7iM0roCPxb/E9qG1/GSV+bNjPApEQlDg58wkLRLOWxI1/L4EGcQDZ0hLL/3GA hDmBXjj48i9YiaiAisSUk9vYJjAKzULSPQtJ9yyE7gWMzKsYZVNyq3RzEzNzilOTdYuTE/Py Uot0LfRyM0v0UlNKNzGCgp7dRXUH44RDSocYBTgYlXh4LxT0BAixJpYVV+YeYpTkYFIS5fXy 7Q0Q4kvKT6nMSCzOiC8qzUktPsQowcGsJMK7lBsox5uSWFmVWpQPk5LmYFES572RctNfSCA9 sSQ1OzW1ILUIJivDwaEkwWsCjG4hwaLU9NSKtMycEoQ0EwcnyHAeoOFyIDW8xQWJucWZ6RD5 U4y6HEffzH3IKMSSl5+XKiXOuw7kOgGQoozSPLg5sGT1ilEc6C1hXieQUTzARAc36RXQEiag JTp8YEtKEhFSUg2MM59ekFgtV/zvzsX3SxcnblUXqOV5VFc2Z3fAp1n3DkU4XPy2d/UcTzFx AYmfcd+E/erXP0mYYtNSHzp5i9Y7/3LP1PCJYso/iu5OWr9v3h6TE3ean+gWLCsqui0u0nuP e4v0ww83WpPy9h44EniSYeuaqJNzWJRsrd/cfnUkdspjO3PtfxNt7yuxFGckGmoxFxUnAgDi clKpMQMAAA== Cc: notmuch@notmuchmail.org, Taesoo Kim X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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, 28 Oct 2012 15:31:44 -0000 Quoth Andrei POPESCU on Oct 28 at 12:03 pm: > On Sb, 27 oct 12, 10:00:46, David Bremner wrote: > > > > As I said (or tried to say), in my opinion, duplication with an external > > package is not the main issue; I think moving features into the core > > when appropriate is a normal development process. On the other hand, I'm > > not really a gmail user, so I don't know yet if these patches solve > > enough of the problem to be interesting. > > They are interesting not only for Gmail[1], but also for other kinds of What is preventing folder: searches from addressing this? > setups. As far as I understand (please correct me if I'm wrong), > currently notmuch treats multiple copies of a message similar to Gmail > (indexes one, but ignores the rest), which is why I'm *not* receiving > any mailing lists on my Gmail account. notmuch tracks all copies of a message, but its output generally shows messages, rather than files, so you see a message only once regardless of how many copies there are in the file system. Why does that cause you to not receive mailing lists? (Or did I misinterpret your statement?) > Besides that consider also that I'm subscribed to about 40 mailing > lists, each sorted to it's own folder by rules based on List-Id (which > notmuch doesn't support yet as far as I know). This separation is very > useful for my read-flow. > > However, there are messages crossposed to several lists. It would be > great if notmuch or (more probably) a client using notmuch could mark > all copies of a message as read in all folders, but still keep it there > (otherwise the thread in the respective folder is incomplete). If I understand what you're saying, this is exactly what notmuch does. When you remove the "unread" tag, notmuch will (should?) add the "seen" maildir flag to all copies of that message in the file system (barring some corner-cases that flag sync doesn't handle well; maybe you're encountering one of those?). And since notmuch never deletes files, they will remain in the folders they were filed in. > [1] yes, this is probably one missing feature that prevents me from > putting my Gmail account in notmuch as well. > > Kind regards, > Andrei