From: Horacio Sanson <hsanson@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] Gmail source sync back.
Date: Wed, 3 Jul 2013 18:44:49 +0900 [thread overview]
Message-ID: <CAHWBo_bRwKArh7nLQ8EMWdWvBV_kRGT=NqDU=Z69pTY+fNpMUQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1285 bytes --]
I finally got the sync back feature of the Gmail source working. The sync
code uses the offlineimap sync algorithm the Matthieu mentioned some emails
ago.
So far it works ok with my small tests but this code should be considered
alpha so do not test it with your work emails.
https://github.com/hsanson/sup/tree/gmail_source
I also added some fixes and the config option provided by Matthieu.
Testing and feedback is greatly appreciated.
Issues to solve:
- Sync back flags: Not sure if this is needed or how it may work. All
messages I get from Gmail have the \Seen flag no matter if I have seen or
not the message on Gmail web interface. The \Flagged flag can be changed
using the \Starred label instead. The only flag that I really need to care
about is the \Deleted flag.
- How to refresh the index after polling finishes? When new labels are
synced from Gmail to Sup the index is not updated with the new labels until
I reload sup or press "@" to refresh the index. Is there a callback to
refresh the index when the polling finishes?
- Sync back iterates over all messages in the Gmail account checking for
differences between message labels. This can take a long time and may not
finish before the next polling starts. How to do this efficiently?
regards,
Horacio Sanson
[-- Attachment #1.2: Type: text/html, Size: 1728 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2013-07-03 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 9:44 Horacio Sanson [this message]
2013-07-04 20:38 ` Matthieu Rakotojaona
2013-07-29 19:37 ` Gaute Hope
2013-07-29 19:48 ` Gaute Hope
2013-07-29 20:01 ` Gaute Hope
2013-08-22 12:35 ` Gaute Hope
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='CAHWBo_bRwKArh7nLQ8EMWdWvBV_kRGT=NqDU=Z69pTY+fNpMUQ@mail.gmail.com' \
--to=hsanson@gmail.com \
--cc=sup-devel@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