From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs141774icb; Sun, 28 Nov 2010 07:01:52 -0800 (PST) Received: by 10.224.207.74 with SMTP id fx10mr4166230qab.270.1290956512199; Sun, 28 Nov 2010 07:01:52 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t30si9811357qcs.159.2010.11.28.07.01.51; Sun, 28 Nov 2010 07:01:52 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C8BD619782DB; Sun, 28 Nov 2010 10:01:51 -0500 (EST) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id AA8C01858346 for ; Sun, 28 Nov 2010 09:50:19 -0500 (EST) Received: by wwb31 with SMTP id 31so1910882wwb.23 for ; Sun, 28 Nov 2010 06:50:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:subject :from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=SRUfndC+I5v9h79ZwBdaTzCnuOUiYoMhrWeanXPFYqA=; b=MihOqmybjvNd7RNBTXGE+ZV0LpQVPbTijn64e1oQV/EHLV1ldMm7OENgqgwAykw2i7 H/+mhOZQ4mhmGW4hPIwvEODxAdsPUbDK731WGmaBtDvXHQX8/MIA/V7uL/1ksdfbxJJj YqfJMvROJPw/Lg9+Mjzc08Yhk1VgPzNSu6sqc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=w3KZLIeWA1x9QzCTi84ZsXPdzz76NJ52Fyn/pfboiqqLBanmzJuv8zDGX8xYiXd65A HesbAYyle7iivFx6nmacU5mJrB3YOozujnZ5PpQxQh+IfA1RlXQbWW/BEFaEhnPZR4fu S7ojBMJIrfsODmTmXglDSOtoJV3RGV8hM7cu8= Received: by 10.216.179.193 with SMTP id h43mr2122118wem.49.1290955818578; Sun, 28 Nov 2010 06:50:18 -0800 (PST) Received: from localhost (mut38-4-82-233-117-144.fbx.proxad.net [82.233.117.144]) by mx.google.com with ESMTPS id w84sm1898650weq.44.2010.11.28.06.50.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 28 Nov 2010 06:50:17 -0800 (PST) From: Damien Leone To: sup-talk In-reply-to: References: <1290889043-sup-6470@mailer> <1290935803-sup-8547@mailer> Date: Sun, 28 Nov 2010 15:50:15 +0100 Message-Id: <1290955366-sup-9628@mailer> User-Agent: Sup/git 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Lurkos's message of dim. nov. 28 15:05:32 +0100 2010: > 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]. 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. [0] : http://cr.yp.to/proto/maildir.html -- Damien Leone Web: http://dleone.fensalir.fr/ GPG: 0x82EB4DDF _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk