Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Bryan Richardson <btricha@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Archive Emails to Different Source
Date: Mon, 18 Apr 2011 16:26:25 -0600	[thread overview]
Message-ID: <BANLkTinZm7tWyFgRrBENKrEUgG28=5Emew@mail.gmail.com> (raw)
In-Reply-To: <1301499350-sup-8327@bloovis.org>

On Wed, Mar 30, 2011 at 9:39 AM, Mark Alexander <marka@pobox.com> wrote:
> I would recommend using fetchmail instead of offlineimap.  That way
> you are ensured that you have local copies of your email that won't
> get deleted, no matter what happens on your Exchange server.  I used
> offlineimap briefly because so many people on this mailing list said
> it was wonderful.  But when it started deleting messages that
> apparently other Outlook users had "recalled", I went back to
> fetchmail.
>
> I use fetchmail in combination with maildrop, which actually places
> the emails in maildir directories.  You can also use procmail instead
> of maildrop, though its configuration language is a bit obscure.

Thanks for the responses Mark and Philippe. My apologies for not
realizing the fact that it's an OfflineIMAP thing and not a Sup thing.

I'll look into the capabilities of OfflineIMAP a bit more, as well as
investigate fetchmail and maildrop/procmail.

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


      reply	other threads:[~2011-04-18 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 21:46 Bryan Richardson
2011-03-30 14:21 ` Bryan Richardson
2011-03-30 15:39 ` Mark Alexander
2011-04-18 22:26   ` Bryan Richardson [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='BANLkTinZm7tWyFgRrBENKrEUgG28=5Emew@mail.gmail.com' \
    --to=btricha@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