Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Anirudh Sanjeev <anirudh@anirudhsanjeev.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Questions about offlineimap+msmtp+maildir+gmail syncing
Date: Wed, 06 Jan 2010 17:08:20 +0530	[thread overview]
Message-ID: <1262776632-sup-1333@deepthought> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1845 bytes --]

Hi,

This is my first real email with sup! I configured sup to work with my
Gmail(hosted apps) account as follows:

1. Offlineimap fetches email and saves to Maildir (I am behind a very
   slow connection, I need to mirror email)
2. The appropriate Maildir is added as a source in sup. Specifically,
   the Gmail.[All Mail] Folder, which has "cur".
3. I configured msmtp to be used for sending email instead of sendmail.

So far I can read all my emails, and the experience is great. I have a
few minor questions:

1. When I send email via sup, I see the same email as an unread message
   in my Gmail web frontend in the Inbox folder rather than the sent
   folder.
2. Any changes in sup aren't reflected in my web frontend. I am guessing
   this is a problem with my offlineimap configuration. Deleting or
   archiving an email doesn't change anything in the web client.
3. I am unable to work with the drafts already existing in Gmail and the
   web interface is unaware of the drafts I have here. A suggestion on
   how to fix this would be awesome!.
4. Any other suggestions on how to make the experience with offlineimap
   would be awesome! I initially used offlineimap's imap server
   mirroring feature, but I found putting the emails in Maildir format
   made it a lot easier.

I've pasted some of my config files here:
1. My config.yaml - http://antileet.pastebin.com/m3209dc32
2. My sources.yaml - http://antileet.pastebin.com/m6fc935ee
3. My .msmtprc - http://antileet.pastebin.com/m564eafc3
4. My .offlineimaprc - http://antileet.pastebin.com/m3ac306b6

Please help me get sup working! This is exactly what I've been looking
for. I promise to write up a detailed tutorial for the Wiki if I can get
it to work :)

Thanks,
Anirudh

--
Senior undergraduate student, Indian Institute of Technology, Kharagpur
http://anirudhsanjeev.org

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

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

             reply	other threads:[~2010-01-06 12:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 11:38 Anirudh Sanjeev [this message]
2010-01-06 12:56 ` Eric Sherman
2010-01-06 19:09   ` Anirudh Sanjeev
2010-01-14 14:07     ` William Morgan
2010-01-14 14:30       ` Justin Mason
2010-01-14 14:32         ` Justin Mason
2010-01-17 16:57       ` Anirudh Sanjeev
2010-01-16 17:21     ` Scott Henson
2010-01-16 20:04       ` Tero Tilus
2010-01-17 14:54         ` William Morgan
2010-01-17 17:52           ` Scott Henson
2010-01-17 20:42             ` William Morgan
2010-01-19  4:44               ` Scott Henson

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=1262776632-sup-1333@deepthought \
    --to=anirudh@anirudhsanjeev.org \
    --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