From: supermiri123@gmail.com
To: info-gnus-english@gnu.org
Cc: info-gnus-english@gnu.org
Subject: Re: Setting up gnus: read on local, store remote (but not on mailserver)
Date: Mon, 25 Feb 2013 12:34:07 -0800 (PST) [thread overview]
Message-ID: <e8b45510-04a0-4830-9f19-eecec1c21f9a@googlegroups.com> (raw)
In-Reply-To: <mailman.20819.1361821041.855.info-gnus-english@gnu.org>
> To answer your last question first: If only one Emacs machine will ever
> be the client in this setup, and you are not using an external utility
> like offlineimap or fetchmail directly on the mailbox, you could get
> away with using nnml over TRAMP. The advantage of nnmaildir is that,
> unlike MH-style mailboxes like nnml, the maildir layout is designed to
> be suitable for non-locking use, i.e. reading mail even as another
> program is putting stuff into the inbox. Therefore it's an excellent
> choice for a mailbox hosted on a central server for multiple clients to
> use.
OK, since it is indeed the case that only one emacs at a time will be client, I will stick with nnml. At least this has the advantage that I can simply copy the old mail archive then.
I guess that one drawback of the whole setup will be that regexp-searching mail articles will become much slower, right? After all, emacs will have to fetch each message / file separately via ssh, check whether it matches... Well, I'll see...
Many thanks for your help!
Martin
next prev parent reply other threads:[~2013-02-25 20:34 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
[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 [this message]
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=e8b45510-04a0-4830-9f19-eecec1c21f9a@googlegroups.com \
--to=supermiri123@gmail.com \
--cc=info-gnus-english@gnu.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).