Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: isra@herraiz.org (Israel Herraiz)
Subject: [sup-talk] problems with Maildir and IMAP offline
Date: Tue, 14 Jul 2009 18:21:45 +0200	[thread overview]
Message-ID: <1247587742-sup-5619@elly> (raw)
In-Reply-To: <20090713232022.fe1d4839.lcanas@libresoft.es>

Excerpts from Luis's message on Jul 13, 2009 about 11 PM:
> This afternoon I've been trying to set up a gmail account with offlineimap and
> I'm having the same problem reported by this guy[1]. I run offlineimap and it
> creates a Maildir directory with 4hundred read mails and 2hundred unread mails
> (yes, I should pay more attention to my gmail account;).

I have not used IMAP with Sup, but AFAIK, Sup does not touch the
original sources of email. For instance, it does not read nor modify
messages using IMAP, it just read them using that protocol (or maildir
or whatever).

Therefore, the only way to get those messages marked as read is using
sup-sync with the --read option. That will mark the messages as read
in Sup.

However there are two problems. If all the messages (unread or read)
are in the same source, there is no way to indicate which messages are
going to be marked as read and which are not.

Moreover, if you read a message in Sup, it still will appear in Gmail
as unread.

I also use Gmail with Sup, but using POP. I use the web interface of
Gmail when I cannnot access my laptop. I use IMAP from my mobile
phone. And I download all my email to my laptop using POP.

If I get a message in my laptop, it is marked as archived and read in
GMail, so it does not appear as unread in the web nor in my phone.

However, if I read the message in the phone or the web, it will appear
as unread in Sup.

Still it is a good solution if you have a "central" node where you
store your mail, and do your main work (my laptop), and a couple of
"external" agents (phone, web) to be able of reading your email if you
do not have your laptop at hand.

Another advantage is that you keep a copy of your mail in your
laptop. GMail is not going to last forever (of course, it still has a
long live) and with this you ensure that you will not loose your
old-email in GMail is closed some day, and it is also very handy to
make backups of all your email (just copy the mbox file to another
location).

To get the email I use getmail [1], and msmtp [2] with these scripts
[3] (see last section) as a lightweight replacement for sendmail. I
can provide you my config scripts if you want.

It is not a good solution though if you read your email from several
different computers.

Cheers,
Israel

[1] http://pyropus.ca/software/getmail/
[2] http://msmtp.sourceforge.net/
[3] http://wiki.archlinux.org/index.php/Msmtp


      parent reply	other threads:[~2009-07-14 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 21:20 Luis Cañas Díaz
2009-07-14 13:24 ` Andrei Thorp
     [not found]   ` <20090714134544.GD90157@d228.scdc1.swarthmore.edu>
2009-07-14 14:02     ` Andrei Thorp
2009-07-14 15:00       ` Tim Gray
2009-07-14 15:07         ` Ben Walton
2009-07-14 15:28           ` Tim Gray
2009-07-14 15:39             ` Andrei Thorp
2009-07-14 15:59               ` Tim Gray
2009-07-14 15:14         ` Andrei Thorp
2009-07-14 15:45           ` Tim Gray
2009-07-14 16:21 ` Israel Herraiz [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=1247587742-sup-5619@elly \
    --to=isra@herraiz.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