Re: [notmuch] Potential problem using Git for mail (was: Idea for storing tags)

diff --git a/bf/b624cf6f1f7f32a4a30e78d1d419932a6e2cfe b/bf/b624cf6f1f7f32a4a30e78d1d419932a6e2cfe
new file mode 100644 (file)
index 0000000..6f1ba59
--- /dev/null
+++ b/bf/b624cf6f1f7f32a4a30e78d1d419932a6e2cfe
@@ -0,0 +1,107 @@
+Return-Path: <jrollins@finestructure.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 4BF18431FBD\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Jan 2010 11:38:35 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id WOdr-udPhVQx for <notmuch@notmuchmail.org>;\r
+       Tue, 12 Jan 2010 11:38:34 -0800 (PST)\r
+Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8])\r
+       by olra.theworths.org (Postfix) with ESMTP id 9BB9C431FAE\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Jan 2010 11:38:34 -0800 (PST)\r
+Received: from servo.finestructure.net (geco.phys.columbia.edu\r
+       [128.59.170.159])\r
+       (user=jgr2110 author=jrollins@finestructure.net mech=PLAIN bits=0)\r
+       by brinza.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o0CJcX1g026694\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT)\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Jan 2010 14:38:34 -0500 (EST)\r
+Received: from jrollins by servo.finestructure.net with local (Exim 4.71)\r
+       (envelope-from <jrollins@finestructure.net>) id 1NUmZV-0004Ua-OJ\r
+       for notmuch@notmuchmail.org; Tue, 12 Jan 2010 14:38:33 -0500\r
+Date: Tue, 12 Jan 2010 14:38:33 -0500\r
+From: Jameson Rollins <jrollins@finestructure.net>\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Message-ID: <20100112193833.GM8342@finestructure.net>\r
+References: <20100111221909.GA30299@lapse.rw.madduck.net>\r
+       <1263267603-sup-302@elise>\r
+       <20100112045152.GA15275@lapse.rw.madduck.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; micalg=pgp-sha256;\r
+       protocol="application/pgp-signature"; boundary="Ayym4vmyMU9P4uDb"\r
+Content-Disposition: inline\r
+In-Reply-To: <20100112045152.GA15275@lapse.rw.madduck.net>\r
+User-Agent: Mutt/1.5.20 (2009-06-14)\r
+X-No-Spam-Score: Local\r
+X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8\r
+Subject: Re: [notmuch] Potential problem using Git for mail (was: Idea for\r
+ storing tags)\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 12 Jan 2010 19:38:35 -0000\r
+\r
+\r
+--Ayym4vmyMU9P4uDb\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Tue, Jan 12, 2010 at 05:51:53PM +1300, martin f krafft wrote:\r
+> If the MDA delivers to Git, then potentially, you might get into\r
+> a situation where you cannot write your own changes back to the\r
+> repo. This is also a DoS scenario: I'll just keep sending you\r
+> e-mail, and if I manage to pass your mail filters, I'll basically\r
+> commit to your mail repository at regular intervals. Say those are\r
+> 5 seconds. In order for you to write updates to the repo, e.g. to\r
+> update tags, then you would need to pull, rebase, and push all\r
+> within 5 seconds, for otherwise you'd try to push non-fast-forwards.\r
+>=20\r
+> This a bit unrealistic, surely, but there's a real annoyance in it:\r
+> you'd have to pull/rebase/push until a push succeeds =E2=80=94 until you\r
+> found a time window between pull and push during which the MDA\r
+> didn't write to the repo. This might take a long time. If this\r
+> happens in the background by Cron, it's not a real concern, but if\r
+> this becomes a UI issue, I wouldn't know how to handle it.\r
+\r
+What about if just the tag information is stored in the repository,\r
+and not the mail itself?  In that case only the user would be pushing\r
+into the repo and you wouldn't have to worry about the DoS scenario.\r
+\r
+jamie.\r
+\r
+--Ayym4vmyMU9P4uDb\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+Content-Description: Digital signature\r
+Content-Disposition: attachment\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJLTM+3AAoJEO00zqvie6q8IpEP/R6zjS0HKKmaHPGd1Fatz2C9\r
+CPeWvAR4zvs9aFj2du4RH/SX1/ZJX9nL2sFxBLuTB+B4nlvMlbqrJq5gc4JQJoTO\r
+tEGJOjvdWdJHCwmUZuImZxaPjsjcLoMfv38FWVgDpBWJ3dCNzcj2j5QgZYiYuXKN\r
+snmqVnG1ALB4hOo1YS2mbAMkdUzxBZVn9Mmfz6L2zubA87oRXeRV5NnKigztCaY2\r
+l37VseDNDC06AnHtUermwYJw4sT3uD2iNHHPOpdBTZgR7k2x6fkOENkjlPygJGVo\r
+A4E82aHG7aFav/onaw1ZOlgLpXMIdjeBSpci2tB4XnJ2nwXkXUh2xCpBdv+yg4Uo\r
+Iixv1tJTWi8tL+zZSyXD8MgQjdMoaY/DYU9vn2k8CLUwaijgWYd9Q8ox5v8LNKaR\r
+EyLMKJVispw2WXUB+Ybrw8J8Kf2PLtCqtFOp223EeNtD5RrwXXrTcM5gsFNzwnzW\r
+DzogC+LiMjWoJK/F85EXqM9lqQo9eggB8B25Mu2fXzJ1CH43ysoK+s52ROx3BkdA\r
+o/DeQrhPBtmC/m27YqpPxCUBLI92Z4dpSvSIF6S2KquCUoKfT0zxmVt2lqfJSWSN\r
+pUCWyOC+dq6B6M/MRCJBrUPQCEHECTjALmlxctv6XsIt777BZzwaAHC5CS+QoqtU\r
+FxwY8kDRoLQLlE2SjyWo\r
+=TVY2\r
+-----END PGP SIGNATURE-----\r
+\r
+--Ayym4vmyMU9P4uDb--\r