Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 42257431FAF for ; Wed, 4 Mar 2015 05:13:46 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 2.439 X-Spam-Level: ** X-Spam-Status: No, score=2.439 tagged_above=-999 required=5 tests=[DNS_FROM_AHBL_RHSBL=2.438, HTML_MESSAGE=0.001] 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 4GLWQe41SK9t for ; Wed, 4 Mar 2015 05:13:43 -0800 (PST) X-Greylist: delayed 317 seconds by postgrey-1.32 at olra; Wed, 04 Mar 2015 05:13:42 PST Received: from mx1b.lautre.net (mx1b.lautre.net [80.67.160.72]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id F2F34431FAE for ; Wed, 4 Mar 2015 05:13:42 -0800 (PST) Received: from vm_arch_64.bat.fr.eu.org (97.100.203.77.rev.sfr.net [77.203.100.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: vm_arch_64@bat.fr.eu.org) by mx1b.lautre.net (Postfix) with ESMTPSA id 21F677E070 for ; Wed, 4 Mar 2015 14:07:07 +0100 (CET) Received: by vm_arch_64.bat.fr.eu.org (sSMTP sendmail emulation); Wed, 04 Mar 2015 14:07:01 +0100 From: Baptiste To: notmuch@notmuchmail.org Subject: Add /renew/ tag to moved/renamed/reflagged messages Organization: bat.fr.eu.org User-Agent: Notmuch/0.18.1+51~gbbbdf04 (http://notmuchmail.org) Emacs/25.0.50.2 (x86_64-unknown-linux-gnu) Date: Wed, 04 Mar 2015 14:07:01 +0100 Message-ID: <87ioegq5ca.fsf@vm_arch_64.bat.fr.eu.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=-=-=" X-Mailman-Approved-At: Wed, 04 Mar 2015 12:10:35 -0800 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: Wed, 04 Mar 2015 13:13:46 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, new messages are given a default (configurable) tag, typically /new/=C2=A0= =E2=80=A6 This is handy for automatic tagging. What about another automatic tag to re-add to an existing mail when =3Dnotm= uch new=3D detect a moved, renamed or reflagged message=C2=A0=E2=80=A6=20 This would allow something like tag synchro through an =3DIMAP=3D mailbox, = or at least keep folder and tag organization coherent while a message is mo= ved =E2=80=A6 my usecase is=C2=A0: - On PC A - message /1/ is received from =3DIMAP=3D in default mail folder, given t= ag /new/ - message /1/ is automatically tagged /inbox/ (see /afew/) - On PC B - message /1/ is received from =3DIMAP=3D in default mail folder, given t= ag /new/ - message /1/ is automatically tagged /inbox/ (see /afew/) - manual tagging into mail client as /archive/ - mail is moved (see /afew/) to /Archives/ folder due to /archive/ tag - message /1/ no more in default but /Archives/ folder is synchronized ba= ck to =3DIMAP=3D server - On PC A (not possible today) - message /1/ is re-received from =3DIMAP=3D in /Archives/ folder, and re= moved from default mail folder, added tag /renew/ - (today, =3Dnotmuch new=3D just detect the moved file, and thanksfully= keep existing tags) - message /1/ is automatically tagged /archive/ due to presence in /Archi= ves/ folder (and /renew/ tag) Thank you, --=20 ~~^v^~~ Baptiste --=-=-= Content-Type: multipart/related; boundary="==-=-=" --==-=-= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi,

new messages are given a default (configurable) tag, typically new= =C2=A0=E2=80=A6
This is handy for automatic tagging.

What about another automatic tag to re-add to an existing mail when n= otmuch new detect a moved, renamed or reflagged message=C2=A0=E2=80= =A6
This would allow something like tag synchro through an IMAP ma= ilbox, or at least keep folder and tag organization coherent while a messag= e is moved =E2=80=A6

my usecase is=C2=A0:

  • On PC A
    • message 1 is received from IMAP in default mail fol= der, given tag new
    • message 1 is automatically tagged inbox (see afew)=
  • On PC B
    • message 1 is received from IMAP in default mail fol= der, given tag new
    • message 1 is automatically tagged inbox (see afew)=
    • manual tagging into mail client as archive
    • mail is moved (see afew) to Archives folder due to arc= hive tag
    • message 1 no more in default but Archives folder is synch= ronized back to IMAP server
  • On PC A (not possible today)
    • message 1 is re-received from IMAP in Archives folder, and removed from default mail folder, added tag renew
      • (today, notmuch new just detect the moved file, and thanks= fully keep existing tags)
    • message 1 is automatically tagged archive due to presence= in Archives folder (and renew tag)

Thank you,

–
~^v^~ Baptiste

--==-=-=-- --=-=-=--