From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 977C1431FBC for ; Tue, 12 Jan 2010 21:52:53 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.152 X-Spam-Level: X-Spam-Status: No, score=-0.152 tagged_above=-999 required=5 tests=[AWL=0.435, BAYES_00=-2.599, FAKE_REPLY_C=2.012] autolearn=no 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 1BYQkXnpAml9 for ; Tue, 12 Jan 2010 21:52:52 -0800 (PST) Received: from clegg.madduck.net (clegg.madduck.net [193.242.105.96]) by olra.theworths.org (Postfix) with ESMTP id A1517431FAE for ; Tue, 12 Jan 2010 21:52:52 -0800 (PST) Received: from lapse.rw.madduck.net (unknown [IPv6:2404:130:0:1000:20a:e4ff:fe30:4316]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "lapse.rw.madduck.net", Issuer "CAcert Class 3 Root" (verified OK)) by clegg.madduck.net (postfix) with ESMTPS id 6D81E1D4097; Wed, 13 Jan 2010 06:52:44 +0100 (CET) Received: by lapse.rw.madduck.net (Postfix, from userid 1000) id ADBE126E6; Wed, 13 Jan 2010 18:52:41 +1300 (NZDT) Date: Wed, 13 Jan 2010 18:52:41 +1300 From: martin f krafft To: mailtags discussion list , notmuch discussion list Message-ID: <20100113055241.GB13006@lapse.rw.madduck.net> Mail-Followup-To: mailtags discussion list , notmuch discussion list MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="aM3YZ0Iwxop3KEKx" Content-Disposition: inline In-Reply-To: X-Motto: Keep the good times rollin' X-OS: Debian GNU/Linux squeeze/sid kernel 2.6.32-trunk-686 i686 X-Spamtrap: madduck.bogus@madduck.net X-Subliminal-Message: debian/rules! User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.3 at clegg X-Virus-Status: Clean Subject: Re: Idea for storing tags 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, 13 Jan 2010 05:52:53 -0000 --aM3YZ0Iwxop3KEKx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable also sprach Scott Morrison [2010.01.13.1752 +1300]: > The problem with anything that is not universally supported is > that for a package that is to appeal to a wide userbase, most > don't know and don't care about the particulars of this IMAP > server vs that IMAP server. all they know it that for some reason > it doesn't work with account X -- which leads to support head > aches. [...] > Call it Googles problem as you like -- but when I have a product > that doesn't work with GMAIL IMAP there are a lot of potential > users that don't care about server peculiarities and rather just > have it work. Well, the way I see it: you cannot change all IMAP servers at once, and you certainly cannot change Google. If it's possible to implement tagging for email (dare say semantic e-mail) with standard means (where standard means sub-standard, as exemplified by your previous GMail IMAP example), then that's the best way, but if that can't happen then we ought to try a better way. Should we find a solution then, by the rate of standardisation on the 'Net, maybe my grandchildren will finally be able to do proper e-mail. ;) > I agree that conceptually duplicates should be buried but end > users do have "peculiar" organization systems. I think tags should help abstract e-mail away from underlying storage and I'd love that to be a goal. > From my reading, uidplus doesn't allow a delta modification of > a message on a server -- just to write a portion of a message back > -- you still have to write the whole thing back and that can mean > real bandwidth issues for some messages. Absolutely. It would indeed be better if you could just send changes. I just sent a blank mail to imap-protocol-subscribe@mailman.u.washington.edu and have started browsing the archives. So far, there's not really anything relevant. Anyway, looking back at the RFC on keywords, it's not exactly encouraging: A keyword is defined by the server implementation. Keywords do not begin with "\". Servers MAY permit the client to define new keywords in the mailbox (see the description of the PERMANENTFLAGS response code for more information). Anyway, I'll try to untangle the various issues re:IMAP we've been seeing, write mails for each, and hopefully get to the point where I can enquire about IMAPv5. ;) --=20 martin | http://madduck.net/ | http://two.sentenc.es/ =20 the unix philosophy basically involves giving you enough rope to hang yourself. and then some more, just to be sure. =20 spamtraps: madduck.bogus@madduck.net --aM3YZ0Iwxop3KEKx Content-Type: application/pgp-signature; name="digital_signature_gpg.asc" Content-Description: Digital signature (see http://martin-krafft.net/gpg/) Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEAREDAAYFAktNX6kACgkQIgvIgzMMSnV/YwCglR2UwcD7CJ+8xw0L7qrl/A4x +REAmwd7zqatkjFJ1K1vTWmow7EYs7eV =oLU3 -----END PGP SIGNATURE----- --aM3YZ0Iwxop3KEKx--