From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: The nndrafts server should be more customizable
Date: Mon, 19 Nov 2001 07:22:21 -0600 [thread overview]
Message-ID: <q6mlmh2lwtu.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <vafpu6fnpwr.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 19 Nov 2001 09:08:52 +0100")
>>>>> On Mon, 19 Nov 2001 09:08:52 +0100,
>>>>> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> (kg) writes:
kg> But maybe someone should write a filename handler for IMAP, then
kg> the drafts could be stored on the IMAP server. Any takers?
What if drafts were local, but then a C-c C-d saved it to IMAP, or
the backend of choice?
--
Amos
next prev parent reply other threads:[~2001-11-19 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 10:22 Kai Großjohann
2001-11-18 18:24 ` Amos Gouaux
2001-11-18 22:24 ` Paul Jarc
2001-11-19 8:08 ` Kai Großjohann
2001-11-19 13:22 ` Amos Gouaux [this message]
2001-11-19 14:22 ` Kai Großjohann
2001-12-29 3:55 ` Lars Magne Ingebrigtsen
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=q6mlmh2lwtu.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.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).