From: Erik Quaeghebeur <sup@equaeghe.nospammail.net>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Hints for newby switching from Alpine with multiple imap accounts
Date: Sun, 25 Apr 2010 14:44:05 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1004251432440.2734@flfbcjrt> (raw)
Hi,
I'm about to try out sup, because I might switch from Alpine (former
pine). I have multiple imap accounts and (a number of) folder hierarchies.
While things are installing, I have a number of preliminary questions:
* Does anybody have experience with switching from Alpine? What are the
things I should look out for?
* What is the best strategy to try out sup? (I'm first going to try out
the installation and GMail guide on
http://anirudhsanjeev.org/temp/supsite/.)
* I understand that I'll have to keep a local mail store, but is it
possible for basic mail state (read/deleted/answered/...) to be resynced
with the online imap account?
* Can sup be used for usenet?
Best,
Erik
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2010-04-25 18:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.00.1004251432440.2734@flfbcjrt \
--to=sup@equaeghe.nospammail.net \
--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