From: Colin Rafferty <craffert@spspme.ml.com>
Subject: Re: Reading mail on two different hosts
Date: 04 Oct 1996 10:01:49 -0400 [thread overview]
Message-ID: <ocrg23u4ylu.fsf@spssunp.spspme.ml.com> (raw)
In-Reply-To: Juri Pakaste's message of 04 Oct 1996 08:40:28 +0300
Juri Pakaste writes:
>>>>>> "RP" == Richard Pieri <ratinox@unilab.dfci.harvard.edu> writes:
>>>>>> "JP" == Juri Pakaste <pakaste@cc.Helsinki.FI> writes:
JP> I was thinking that I could perhaps split my mail into nnmbox
JP> folders at the university, and then tell Gnus at home to use
JP> ange-ftp to fetch them, and insert them into the nnml groups I
JP> use normally.
RP> nnmail-spool-file may be set to a list of files for incoming mail
RP> spools. Gnus will go to each, in order, and drag them over to
RP> the local mail area. ange-ftp is possibly not the best way to do
JP> Okay. But if I do it this way, will it preserve the marks on what's
JP> read, etc? Does Gnus store that information with some additional
JP> header (umm... "Status"?), or in a separate file?
If you are serious about using ange-ftp, you could just set up home
machine to have your university groups as local groups, with the
location specified using ange-ftp protocols.
You will have all the marks form what you did at school, and if you move
them to your home groups, all the marks go with it.
Conversely, if your home machine is always online, you can directly
split your email from school into your home disks with the following
elisp:
(setq nnml-directory "/pakaste@my.machine.home:/home/pakaste/Mail/"
nnmail-crosspost-link-function 'copy-file)
--
Colin
next prev parent reply other threads:[~1996-10-04 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-03 17:10 Juri Pakaste
1996-10-03 17:49 ` Richard Pieri
1996-10-04 5:40 ` Juri Pakaste
1996-10-04 14:01 ` Colin Rafferty [this message]
1996-10-03 18:05 ` Kai Grossjohann
1996-10-04 5:30 ` Juri Pakaste
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=ocrg23u4ylu.fsf@spssunp.spspme.ml.com \
--to=craffert@spspme.ml.com \
--cc=craffert@ml.com \
/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).