Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: Reading mail on two different hosts
Date: 03 Oct 1996 13:49:05 -0400	[thread overview]
Message-ID: <x7ohik0wh9.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: Juri Pakaste's message of 03 Oct 1996 20:10:30 +0300

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "JP" == Juri Pakaste <pakaste@cc.Helsinki.FI> writes:

JP> I was thinking that I could perhaps split my mail into nnmbox folders
JP> at the university, and then tell Gnus at home to use ange-ftp to fetch
JP> them, and insert them into the nnml groups I use normally.

nnmail-spool-file may be set to a list of files for incoming mail
spools.  Gnus will go to each, in order, and drag them over to the local
mail area.  ange-ftp is possibly not the best way to do it, simply
because there is no file locking whatsoever involved with FTP.  So, if
anything attempts to access those files on the 'server' while you are
transferring them, almost any kind of corruption could occour.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQCVAwUBMlP8lJ6VRH7BJMxHAQEn+wP/e9gaeFF7LIorPxgQTpOc60AXNG3WlGJ1
pJMPqtRH6lLxjqyUj5VXtDSQYJTfUkgDwczRSZuIfQBxCCfinPv4T7jnY9CC8gLt
nvcuSsn7LVvZ+QZwgX3xx27Zy8fQ0Tc7QYbIyhdj5mYp7HDtCM05+HV6GLvLlyG/
vyS6Dlb0Ytw=
=xurL
-----END PGP SIGNATURE-----
-- 
Richard Pieri/Information Services \ Always give generously - a small bird or
<ratinox@unilab.dfci.harvard.edu>   \ rodent left on the bed tells them, "I
http://www.dfci.harvard.edu/         \ care". -A cat's guide to life


  reply	other threads:[~1996-10-03 17:49 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 [this message]
1996-10-04  5:40   ` Juri Pakaste
1996-10-04 14:01     ` Colin Rafferty
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=x7ohik0wh9.fsf@unilab.dfci.harvard.edu \
    --to=ratinox@unilab.dfci.harvard.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).