Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Florian Unglaub <f.unglaub@googlemail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup + offlineimap + Gmail
Date: Thu, 19 May 2011 23:17:20 +0200	[thread overview]
Message-ID: <1305839702-sup-8270@hal> (raw)
In-Reply-To: <1305705194-sup-5588@mailer>

Excerpts from Damien Leone's message of 2011-05-18 09:59:43 +0200:
> Hello,
> 
> Are you sure that reading a e-mail from sup marks it as read in Gmail
> after having executed offlineimap? Because this should not work,
> apparently you are using sup 0.12.1 which does not support backward
> synchronization. [0]

You are right. It doesn't sync back at all. I will try to figure out
how to achieve this with the git version.

Regards,
Florian.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2011-05-19 21:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  7:44 Florian Unglaub
2011-05-18  7:59 ` Damien Leone
2011-05-19 21:17   ` Florian Unglaub [this message]

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=1305839702-sup-8270@hal \
    --to=f.unglaub@googlemail.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