From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/66010 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: file storage in IMAP (eventually for Tramp) working and needs testing Date: Mon, 31 Dec 2007 06:30:24 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: References: <86k5n1443g.fsf@lifelogs.com> <87fxxjgohd.fsf@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199104313 30978 80.91.229.12 (31 Dec 2007 12:31:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 31 Dec 2007 12:31:53 +0000 (UTC) Cc: ding@gnus.org, David To: Michael Albinus Original-X-From: ding-owner+M14503@lists.math.uh.edu Mon Dec 31 13:32:07 2007 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1J9JoM-0003PB-UJ for ding-account@gmane.org; Mon, 31 Dec 2007 13:32:07 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1J9JnQ-0006J4-R4; Mon, 31 Dec 2007 06:31:08 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1J9JnO-0006Il-VP for ding@lists.math.uh.edu; Mon, 31 Dec 2007 06:31:06 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.67) (envelope-from ) id 1J9JnI-0006QD-SY for ding@lists.math.uh.edu; Mon, 31 Dec 2007 06:31:06 -0600 Original-Received: from blockstar.com ([170.224.69.95] helo=mail.blockstar.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1J9JnI-00086P-00 for ; Mon, 31 Dec 2007 13:31:00 +0100 Original-Received: from mungo (c-67-186-103-18.hsd1.il.comcast.net [67.186.103.18]) by mail.blockstar.com (Postfix) with ESMTP id 874843F88B5; Mon, 31 Dec 2007 05:00:34 -0800 (PST) X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Followup-To: Michael Albinus , ding@gnus.org, David In-Reply-To: <87fxxjgohd.fsf@gmx.de> (Michael Albinus's message of "Mon, 31 Dec 2007 11:14:38 +0100") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (darwin) X-Spam-Score: -2.5 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:66010 Archived-At: On Mon, 31 Dec 2007 11:14:38 +0100 Michael Albinus wrote: MA> Ted Zlatanov writes: >> I had not thought about using drafts over Tramp, but I think it's better >> to support drafts to an IMAP server directly, so you can use them with >> any other IMAP client (as Thunderbird does by default, for example). MA> I don't get the point. Tramp is good for storing files somewhere else, MA> this could be a draft folder of an IMAP server(1). How would it prevent MA> other IMAP clients using it? MA> (1) It would need an imap method implementation, of course. I'm throwing the whole file, PGP-encrypted, into an article, and using minimal headers plus a hacked-up Subject header to make it work. I'm not doing this with interoperability in mind, and I don't think as it stands now it's usable by other IMAP clients. If there's a standard for file storage over IMAP (and I don't mean MIME) I don't know about it. It needs to support deletion, overwriting, unambiguous naming, etc. Gnus, whether accidentally or by design, will actually understand these primitive articles and decode them without Trimp's help, but that was a surprise to me :) Incidentally since I mentioned "unambiguous naming" above, the header currently has the file name stripped of any characters other than [a-zA-Z/] which is nice for searching but will cause conflicts with many file names. I am thinking of using Subject: trimp-subject-marker stripped-filename subject-encoded-filename So the full filename is also visible without getting the article, but the stripped filename lets us do IMAP searches easily. The encoding could be UTF-8. As I said, there's no standard for this AFAIK, so any suggestions are welcome. Ted