From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 14D986DE146A for ; Sun, 26 Mar 2017 22:52:16 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.205 X-Spam-Level: X-Spam-Status: No, score=-0.205 tagged_above=-999 required=5 tests=[AWL=-0.185, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 Y6VmElWO92nI for ; Sun, 26 Mar 2017 22:52:15 -0700 (PDT) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) by arlo.cworth.org (Postfix) with ESMTPS id D0CDF6DE145D for ; Sun, 26 Mar 2017 22:52:14 -0700 (PDT) Received: by mail-lf0-f50.google.com with SMTP id x137so14757383lff.3 for ; Sun, 26 Mar 2017 22:52:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gaute-vetsj-com.20150623.gappssmtp.com; s=20150623; h=date:from:subject:to:references:in-reply-to:user-agent:message-id :mime-version:content-transfer-encoding; bh=2nOBaPAYoWSlLFU6hdihg/xLH/0DYHBDAmSYYUVF4zc=; b=NRkVI38EHx9JTNq4T8GR0tboHBAAurd6p0x8Cr1hUWvxg7cFvhC6u5F4ULONUWjHC0 H/6j1ds3L0jUrou1vVCcou1tDr5Qkl6yF+ygVgEOeYIneyIC4vTCY4nckr3WnWVkBAbd UeMvaITXm0xky+CMX8nqtWRhwkvRuFRKw5+Mx5mOP/iYpKiizhiZkuXKrk6yfYizvC0m cYUqIta+Sg8Idf8FUhMc7r5zfo10K2tNCV141qU2+RTWSD/fUfG0zrp1cNsufCdwdcYL VOlmrms6WBIn59VfcO49jVWUu+jAxO5OmyXgMrHwBjGAEjn+8YPvw9B7kTGLbqR9X9zJ +KxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-transfer-encoding; bh=2nOBaPAYoWSlLFU6hdihg/xLH/0DYHBDAmSYYUVF4zc=; b=oo/ihMJIYy8vogb6bey8WWZVhoF+L90nurxY4PnNVe562ZTOb606qH7EmNvS840uYl 26DoCMXvEuFOHkFCAwtSvlo2Y43mf5KAP4rAsqdsIOFTeYsrhPuByvd5Mw8TjF8n71d9 bJrjKvLGK65dsYmQWJOyhdkTGafyFLQ+3AdopfTPTRXkxL5L/DpjGQPva3KQamFi+3JI 8Aq1XErBm1qqQejVdbsBAcPzMHfgNWAdlTtKDKntK2uE7p4tudEUdo72uGRrJicybqdS oKTr9v5dJq6CUbN814kNSJdR+ivz6OogmbQE4hi5QTHwT87SJPqZAu1wp+6dMSfBq6JI 1rGg== X-Gm-Message-State: AFeK/H1dMOlSteZ+vXVUETZhe+SBMqD+ZI9+K48jsTObRFvnq0dcxFZXbv3xWDgxsjGMQw== X-Received: by 10.25.195.11 with SMTP id t11mr9223038lff.165.1490593932634; Sun, 26 Mar 2017 22:52:12 -0700 (PDT) Received: from localhost (cm-84.215.128.252.getinternet.no. [84.215.128.252]) by smtp.gmail.com with ESMTPSA id z26sm1785394lja.28.2017.03.26.22.52.11 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 26 Mar 2017 22:52:11 -0700 (PDT) Date: Mon, 27 Mar 2017 05:52:08 +0000 From: Gaute Hope Subject: Re: [gmailieer] fast fetch and two-way tag synchronization between notmuch and GMail To: notmuch@notmuchmail.org, Rafael Avila de Espindola References: <1489401808.6fnnjm7u8s.astroid@strange.none> <87k27r26xd.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> <1489526023.3h28rur3jt.astroid@strange.none> <878tnrla97.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> In-Reply-To: <878tnrla97.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-ti ckle-me> User-Agent: astroid/v0.8-7-g7144d7e0 (https://github.com/astroidmail/astroid) Message-Id: <1490591813.ujxyjti2et.astroid@strange.none> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Mon, 27 Mar 2017 05:52:16 -0000 Rafael Avila de Espindola writes on mars 27, 2017 4:32: > I currently have a mbsync + notmuch setup and I am just about to give > this a try. > > One question is what the notmuch setup should look like. I assume I > should create a new config file pointing to the directory where the > emails will be written to. Do I have to run notmuch setup to create the > db? > Yes, it is a good idea to just back up your entire notmuch db and set up a new one to test gmailieer with. gmailieer respects $NOTMUCH_CONFIG and reads it to figure out which 'new' tags to add (no need to use inbox or unread here, that will only create confusion - I only use 'new' to do tagging). Assuming you want to set up a separate notmuch database to test you do the following: first: get a client secret API key for gmailieer [0], you only need this during setup or if gmailieer needs to be re-authenticated. so store it somewhere safe, say: ~/.secret/client_secret.json. ideally this should be unnecessary [1]. # setting up a separate notmuch db $ mkdir ~/test_mail/ # our new mail root $ cd ~/test_mail $ export NOTMUCH_CONFIG=3D$(pwd)/.notmuch-config $ mkdir mail # new mail database root $ notmuch setup * specify ~/test_mail/mail as mail database * specify only 'new' as new tag $ notmuch new # create db $ cd mail NOTE: As long as you are using a non-standard notmuch config location make sure that environment variable is set when using gmailieer. # setting up gmailieer $ mkdir gmail * this will be the gmailieer local repository. * it should be a sub-dir of the root mail db. * you can keep other mail (from other accounts) outside this gmailieer local repository. $ cd gmail $ gmi auth -c ~/.secret/client_secret.json * authenticate gmailieer, choose the correct account, say: charlie.root@gmail.com $ gmi init -a charlie.root@gmail.com # gmailieer should now be set up $ gmi pull # does the initial pull, fetching all you messages - this # could take some time. When you want to synchronize your account you do: $ gmi sync # which effectively does gmi push; gmi pull this will also update the notmuch database so it should not be necessary to run 'notmuch new' afterwards. Regards, Gaute [0] https://console.developers.google.com/flows/enableapi?apiid=3Dgmail [1] https://github.com/gauteh/gmailieer/issues/1 =