From: Lurkos <lurkos.usenet@gmail.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] IMAP, labels, editors
Date: Mon, 29 Nov 2010 18:59:28 +0000 (UTC) [thread overview]
Message-ID: <63f0d2ea234ebf04fe1fb894d9ad2dee.XPN@L622243018051.user.x-privat.org> (raw)
In-Reply-To: <1290955366-sup-9628@mailer>
*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
next prev parent reply other threads:[~2010-11-29 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 18:17 Lurkos
2010-11-27 20:26 ` Damien Leone
2010-11-27 20:57 ` Moritz Wilhelmy
2010-11-27 23:34 ` Lurkos
2010-11-28 1:27 ` Lurkos
2010-11-28 9:21 ` Damien Leone
2010-11-28 14:05 ` Lurkos
2010-11-28 14:50 ` Damien Leone
2010-11-29 18:59 ` Lurkos [this message]
2010-11-29 20:08 ` Damien Leone
2010-11-30 2:36 ` Lurkos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63f0d2ea234ebf04fe1fb894d9ad2dee.XPN@L622243018051.user.x-privat.org \
--to=lurkos.usenet@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox