Date: Tue, 12 Jan 2010 14:38:33 -0500
From: Jameson Rollins <jrollins@finestructure.net>
To: notmuch <notmuch@notmuchmail.org>
Message-ID: <20100112193833.GM8342@finestructure.net>
References: <20100111221909.GA30299@lapse.rw.madduck.net>
	<1263267603-sup-302@elise>
	<20100112045152.GA15275@lapse.rw.madduck.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="Ayym4vmyMU9P4uDb"
Content-Disposition: inline
In-Reply-To: <20100112045152.GA15275@lapse.rw.madduck.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [notmuch] Potential problem using Git for mail (was: Idea for
 storing tags)
Precedence: list


--Ayym4vmyMU9P4uDb
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 12, 2010 at 05:51:53PM +1300, martin f krafft wrote:
> If the MDA delivers to Git, then potentially, you might get into
> a situation where you cannot write your own changes back to the
> repo. This is also a DoS scenario: I'll just keep sending you
> e-mail, and if I manage to pass your mail filters, I'll basically
> commit to your mail repository at regular intervals. Say those are
> 5 seconds. In order for you to write updates to the repo, e.g. to
> update tags, then you would need to pull, rebase, and push all
> within 5 seconds, for otherwise you'd try to push non-fast-forwards.
>=20
> This a bit unrealistic, surely, but there's a real annoyance in it:
> you'd have to pull/rebase/push until a push succeeds =E2=80=94 until you
> found a time window between pull and push during which the MDA
> didn't write to the repo. This might take a long time. If this
> happens in the background by Cron, it's not a real concern, but if
> this becomes a UI issue, I wouldn't know how to handle it.

What about if just the tag information is stored in the repository,
and not the mail itself?  In that case only the user would be pushing
into the repo and you wouldn't have to worry about the DoS scenario.

jamie.

--Ayym4vmyMU9P4uDb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: attachment

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLTM+3AAoJEO00zqvie6q8IpEP/R6zjS0HKKmaHPGd1Fatz2C9
CPeWvAR4zvs9aFj2du4RH/SX1/ZJX9nL2sFxBLuTB+B4nlvMlbqrJq5gc4JQJoTO
tEGJOjvdWdJHCwmUZuImZxaPjsjcLoMfv38FWVgDpBWJ3dCNzcj2j5QgZYiYuXKN
snmqVnG1ALB4hOo1YS2mbAMkdUzxBZVn9Mmfz6L2zubA87oRXeRV5NnKigztCaY2
l37VseDNDC06AnHtUermwYJw4sT3uD2iNHHPOpdBTZgR7k2x6fkOENkjlPygJGVo
A4E82aHG7aFav/onaw1ZOlgLpXMIdjeBSpci2tB4XnJ2nwXkXUh2xCpBdv+yg4Uo
Iixv1tJTWi8tL+zZSyXD8MgQjdMoaY/DYU9vn2k8CLUwaijgWYd9Q8ox5v8LNKaR
EyLMKJVispw2WXUB+Ybrw8J8Kf2PLtCqtFOp223EeNtD5RrwXXrTcM5gsFNzwnzW
DzogC+LiMjWoJK/F85EXqM9lqQo9eggB8B25Mu2fXzJ1CH43ysoK+s52ROx3BkdA
o/DeQrhPBtmC/m27YqpPxCUBLI92Z4dpSvSIF6S2KquCUoKfT0zxmVt2lqfJSWSN
pUCWyOC+dq6B6M/MRCJBrUPQCEHECTjALmlxctv6XsIt777BZzwaAHC5CS+QoqtU
FxwY8kDRoLQLlE2SjyWo
=TVY2
-----END PGP SIGNATURE-----

--Ayym4vmyMU9P4uDb--