Gnus development mailing list
 help / color / mirror / Atom feed
From: "Steven E. Harris" <steven.harris@tenzing.com>
Subject: Re: nnimap RFC2342 support (IMAP4 Namespace)
Date: 01 Feb 2001 10:37:21 -0800	[thread overview]
Message-ID: <87lmrqfdwe.fsf@torus.tenzing.com> (raw)
In-Reply-To: NAGY Andras's message of "01 Feb 2001 03:34:54 +0100"

NAGY Andras <nagya@inf.elte.hu> writes:

> But it would be a really nice feature (however implemented) if I
> could say "on this (cyrus) server all but one of the mailboxes have a
> name starting with `INBOX.'.  I don't like this, so please let me name
> my mailboxes whatever I want, and prepend this prefix automatically,
> at low level, when sending it to the server, and remove it on the way
> back.  Do this on all the mailboxes except for the special one
> `INBOX'."

That's exactly what I was asking for. Additionally, there should be a
way to abstract folder "nesting." As my example showed, one server
allowed/permitted slashes, while the other required dots as
separators. On one server, private user folders can live alongside
INBOX. On the other server, those folders must be under the
INBOX. Conceptually, the folders are in the same place, though. I
thought RFC2342 enables that abstraction. The user thinks only of
INBOX, and a folder tree. The actual syntactic representation of that
tree may be server-specific, but RFC2342 allows the proper translation
to happen.

Maybe I'm projecting more hope into than it deserves. It just seems
that Outlook is able to maintain this single representation as far as
the user interface goes. Perhaps Gnus could do something similar.

-- 
Steven E. Harris        :: steven.harris@tenzing.com
Tenzing                 :: http://www.tenzing.com



  parent reply	other threads:[~2001-02-01 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 21:33 Steven E. Harris
2001-01-31 22:21 ` Simon Josefsson
2001-02-01  2:34   ` NAGY Andras
2001-02-01  3:06     ` NAGY Andras
2001-02-01 18:37     ` Steven E. Harris [this message]
2001-02-11  1:58     ` NAGY Andras
2001-02-01 19:29   ` Steven E. Harris

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=87lmrqfdwe.fsf@torus.tenzing.com \
    --to=steven.harris@tenzing.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).