*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
