Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Gamari <bgamari@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Switching to Exchange
Date: Sat, 20 Feb 2010 12:38:58 -0500	[thread overview]
Message-ID: <1266687464-sup-6371@ben-laptop> (raw)
In-Reply-To: <1266612722-sup-5668@sgoldmanlinux.tower-research.com>

Excerpts from Steve Goldman's message of Fri Feb 19 15:57:02 -0500 2010:
> The remedy was to download all the messages off the server into a
> local mbox file and to use fetchmail/procmail to poll for new IMAP
> messages and append them to the mbox file.
> 
I would strongly encourage you to look into offlineimap. It's designed
exactly for this sort of application and does its job very well.

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


  parent reply	other threads:[~2010-02-20 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 22:56 Steve Goldman
2010-02-19 20:57 ` Steve Goldman
2010-02-19 21:28   ` hollunder
2010-02-21 17:40     ` Nicolas Pouillard
2010-02-20 17:38   ` Ben Gamari [this message]
2010-02-20 21:10     ` Mark Alexander

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=1266687464-sup-6371@ben-laptop \
    --to=bgamari@gmail.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