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 AE6D06DE015B for ; Tue, 19 Jul 2016 02:51:32 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -2.301 X-Spam-Level: X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_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 YNFe3IwuzkLa for ; Tue, 19 Jul 2016 02:51:22 -0700 (PDT) X-Greylist: delayed 603 seconds by postgrey-1.35 at arlo; Tue, 19 Jul 2016 02:51:22 PDT Received: from incoming1.cnam.fr (incoming1.cnam.fr [163.173.128.32]) by arlo.cworth.org (Postfix) with ESMTP id 257A16DE012F for ; Tue, 19 Jul 2016 02:51:21 -0700 (PDT) X-IronPort-AV: E=Sophos;i="5.28,388,1464645600"; d="scan'208";a="45326897" Received: from 252.36.151.77.rev.sfr.net (HELO localhost) ([77.151.36.252]) by incoming1.cnam.fr with ESMTP/TLS/AES128-GCM-SHA256; 19 Jul 2016 11:41:15 +0200 Date: Tue, 19 Jul 2016 11:42:05 +0200 From: =?iso-8859-1?Q?Rapha=EBl?= Fournier-S'niehotta To: notmuch@notmuchmail.org Subject: Avoiding the "huge INBOX of death" Message-ID: <20160719094205.qmf5sjnja6crt5t3@gotlib> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Tue, 19 Jul 2016 09:51:32 -0000 Hello fellow notmuchers, I am a longtime "classic" mutt user, willing to switch to a notmuch-based solution (probably neomutt). However, as far as I understand, I will have to deal with a "huge INBOX of death", as put by Anarcat in a recent blog post [1], that when all emails remain in a single maildir, which may the become very large. I would like to avoid this, for quota reasons on my work imap server first, and also because I sometimes have to use webmail access, with poor searching capabilities. Thus, I think I need to have my emails sorted into maildir folders according to the notmuch tags. Namely, emails with the "inbox" tag should stay in the INBOX maildir, those with "archive" should be moved to Archives (all synchronized with the server). As a bonus, it would be great to have a few more features, like "mails in Archives older than 6 months are moved to Archives/" (kept locally and not stored on the server). As far as I understand, "afew" and its MailMover feature could be useful for my case, but it does not seem currently maintained (plus, very few mentions of it on the notmuch archives) and Michael Turquette said it's buggy [2], so I would like more feedback to be sure before letting it mess with my maildir. Another tool that could be useful is the "maildir-notmuch-sync" script written by Ethan Schoonover and adapted by Michael Turquette [3]. However, it seems dedicated to handling the synchronization of Gmail labels, not a generic imap server hierarchy. Perhaps there is another solution to deal with this in a notmuch-based setup, I would very much like any of your feedback. [1]: https://anarc.at/blog/2016-05-12-email-setup/ [2]: http://deferred.io/2016/01/17/state-of-the-dotfiles.html [3]: http://deferred.io/2016/01/18/notmuch-tags-gmail-labels-bidirectional-sync.html -- Raphaël Fournier-S'niehotta http://raphael.fournier-sniehotta.fr/apropos