Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: moving one 'mailbox'
Date: 11 Oct 1996 09:50:22 -0400	[thread overview]
Message-ID: <x7pw2pehk1.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: Andy Eskilsson's message of 11 Oct 1996 09:00:30 +0200

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

>>>>> "AE" == Andy Eskilsson <flognat@fukt.hk-r.se> writes:

AE> MMh, Ain't nndir read-only?? 

Yeah, it is.  But whatever "native" method is used on the server is
probably read-write.  Not that it is likely, but something could get
munged that way.

AE> Feature idea.. some kind of remote gnus-mail reading?

Set up the FTP directories as "real" mail backends.  Or even more
simply, point <backend>-directory to the FTP directory to get the entire
heirarchy (or set this in a select method).  But, as I said, there is no
locking mechanism for FTP sessions, not one that will work reliably,
anyway.

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

iQCVAwUBMl5QoJ6VRH7BJMxHAQFTSAP/ZRAmaQpEsf8ifbItMkC2oajVoSrJnxeD
Q0ddR+T46JCdicNN03Gf2+4gNQMZf7bEPSzS8dCkGmkfKSG50/LqqWXUaRDl8pRM
4zTXR/hEkdtQXwhTZb07isbrxaThwD88J3wMUwajHygRLwqFE91LDjcS1MQJ9qob
CFiD8U283F8=
=PaYb
-----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-11 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-09  9:19 Andy Eskilsson
1996-10-09 13:39 ` Richard Pieri
1996-10-10 14:01   ` Andy Eskilsson
1996-10-10 14:12     ` Richard Pieri
1996-10-11  7:00       ` Andy Eskilsson
1996-10-11 13:50         ` Richard Pieri [this message]

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=x7pw2pehk1.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).