From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: info-gnus-english-mXXj517/zsQ@public.gmane.org
Subject: Re: Setting up gnus: read on local, store remote (but not on mailserver)
Date: Mon, 25 Feb 2013 15:03:08 +0000 [thread overview]
Message-ID: <87zjyso2qb.fsf@riseup.net> (raw)
In-Reply-To: <5896e2dc-a264-4ea7-b250-9e95cfaf01a2@googlegroups.com>
Hi Martin,
supermiri123-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org writes:
> Hi gnurus!
>
> Since I have a new job, I need to modify my gnus setup, and don't know
> how. I have the following:
>
> 1) mail is coming from some server with limited storage space (in
> fact, not enough)
>
> 2) I have enough storage space on a machine I can ssh to, but where I
> do not have a reasonably recent emacs (No root rights. Emacs version
> there is 21.) However, this is in a local network (at a university),
> so ssh should not be too slow.
>
> 3) My email archive (which I depend on for every day work) has just
> about 2GB currently.
>
> I would like to use my local emacs with gnus to read email, but have
> it stored on the other computer, so I can always access it, even if
> I'm not in my office.
>
> Is there an effective solution known, or do I have to experiment?
>
> Many thanks,
>
> Martin
A maildir might be a good choice. The `nnmaildir' backend (info "(gnus)
Maildir") can use a remote filesystem, e.g.
(setq gnus-select-method
'(nnmaildir "mail"
(directory "/rsyncc:user-3I8OyKyBCfCmcwpypvFeBw@public.gmane.org:/path/to/maildir/")
(get-new-mail t)))
The above would use Gnus to incorporate mail using whatever methods you
picked in `mail-sources', and store them in a remote maildir accessed
with rsync (you can use any TRAMP filename, e.g. ssh:, scpc:, etc.).
If you have the ability to install packages on the remote host, you
could also install offlineimap or something, and skip the `get-new-mail
t' in this example.
--
Regards,
WGG
next prev parent reply other threads:[~2013-02-25 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 13:24 supermiri123
2013-02-25 15:03 ` W. Greenhouse [this message]
[not found] ` <mailman.20803.1361804622.855.info-gnus-english@gnu.org>
2013-02-25 18:04 ` supermiri123
2013-02-25 19:36 ` W. Greenhouse
[not found] ` <mailman.20819.1361821041.855.info-gnus-english@gnu.org>
2013-02-25 20:34 ` supermiri123
2013-02-25 23:06 ` W. Greenhouse
[not found] ` <mailman.20848.1361833630.855.info-gnus-english@gnu.org>
2013-02-27 7:56 ` supermiri123
2013-02-27 9:17 ` supermiri123
2013-02-28 17:30 ` W. Greenhouse
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=87zjyso2qb.fsf@riseup.net \
--to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
--cc=info-gnus-english-mXXj517/zsQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).