From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs177741icb; Mon, 29 Nov 2010 11:51:13 -0800 (PST) Received: by 10.216.24.139 with SMTP id x11mr5450736wex.27.1291060272196; Mon, 29 Nov 2010 11:51:12 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l13si13213791qck.46.2010.11.29.11.51.11; Mon, 29 Nov 2010 11:51:12 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id A1DDE1858381; Mon, 29 Nov 2010 14:51:11 -0500 (EST) X-Greylist: delayed 901 seconds by postgrey-1.31 at rubyforge.org; Mon, 29 Nov 2010 14:20:12 EST Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by rubyforge.org (Postfix) with ESMTP id 574921858378 for ; Mon, 29 Nov 2010 14:20:11 -0500 (EST) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PN929-0004oL-1f for sup-talk@rubyforge.org; Mon, 29 Nov 2010 20:05:05 +0100 Received: from rain.gmane.org ([80.91.229.7]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Nov 2010 20:05:04 +0100 Received: from lurkos.usenet by rain.gmane.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Nov 2010 20:05:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: sup-talk@rubyforge.org From: Lurkos Date: Mon, 29 Nov 2010 18:59:28 +0000 (UTC) Message-ID: <63f0d2ea234ebf04fe1fb894d9ad2dee.XPN@L622243018051.user.x-privat.org> References: <1290889043-sup-6470@mailer> <1290935803-sup-8547@mailer> <1290955366-sup-9628@mailer> Mime-Version: 1.0 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: rain.gmane.org User-Agent: XPN/1.2.6 (Street Spirit ; Linux) X-face: )^2%d:dly4s; phd)XP2{vaO3Gj68Kba?; /NjbPGyqUu'N)ow; >>#2i0@ X-OpenPGP-Key-ID: 135E4D8D X-OpenPGP-Key-Fprint: 1B57EB95F6191D6C1056B6D3BFCA1BDA135E4D8D X-Old-FQDN: L622132.user.x-privat.org X-New-FQDN: L622243018051.user.x-privat.org Subject: Re: [sup-talk] IMAP, labels, editors X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org *Damien Leone* wrote: >> Thanks for explaining. >> Yesterday I spent a couple of hours to search for more details about >> *sup*, *notmuch* and *offlineimap*. >> What I still have not completely understood is how *sup* is going to >> store label information inside Maildir sources. >> According to this message >> (http://lists.madduck.net/pipermail/mailtags/2007-August/msg00016.html), >> IMAP tags would not be perfect (even if probably the best solution in >> my opinion). >> Another problem is that is not completely clear if *offlineimap* would >> sync also these "special" tags. > > Currently everything is stored in the xapian database that stays local > to sup. On the maildir-sync branch, only the following flags are > exported [0]. | Flag "F" (flagged): user-defined flag; toggled at user discretion. I have not completely understood what can be stored inside this special user-defined flag. Here (http://wiki.dovecot.org/MailboxFormat/Maildir#IMAP_keywords) I found a non-standard way to implement some flags, but I don't how if offlineimap would support it. > That means that you have two sets of labels, the ones on the IMAP > server and the others in sup. Usually offlineimap will create a > Maildir source per IMAP label (at least with gmail) so it is easy to > add them separately in sup and auto-apply rules for each (such as > apply a label, archive messages from this source, etc.) so it is not > too painful. > >> Therefore the only possible solution seems to have a personal server >> running 24/7 and using *sup* via *ssh*. > > Yep, that's my case. Unfornately it doesn't apply to me, also because I have a standard ADSL home connection. > [0] : http://cr.yp.to/proto/maildir.html -- Lurkos _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk