From: John Owens <jowens@ece.ucdavis.edu>
Subject: IMAP: file storage, relation to agent, and what the server does?
Date: Thu, 22 May 2003 17:23:29 -0700 [thread overview]
Message-ID: <u3cj6jyta.fsf@ece.ucdavis.edu> (raw)
Simple question: I'd like to leave my mail files (groups) on the IMAP
server. However, I'm happy with local cached versions on my laptop,
and I assume I can mark what I want cached and then allow gnus to sync
before I unplug.
I don't want to have to sync all the mail groups, and I don't think I
have to. But how should I set up my mail group files so that
a) I can read mail on the server and always be synched;
b) I can read mail on my laptop and have a few groups synched?
I imagine this is possible and a solved problem; I'm concerned with
the gnus settings necessary to point to the right directories and
files; I haven't used full-blown IMAP before and am not sure what it
magically does for me as far as keeping things synched, and what gnus
does, and what I have to do.
JDO
next reply other threads:[~2003-05-23 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 0:23 John Owens [this message]
2003-05-23 6:22 ` IMAP: file storage, relation to agent, and what the server Kai Großjohann
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=u3cj6jyta.fsf@ece.ucdavis.edu \
--to=jowens@ece.ucdavis.edu \
/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;
as well as URLs for NNTP newsgroup(s).