Gnus development mailing list
 help / color / mirror / Atom feed
From: NAGY Andras <nagya@inf.elte.hu>
Subject: Re: nnimap RFC2342 support (IMAP4 Namespace)
Date: 01 Feb 2001 04:06:38 +0100	[thread overview]
Message-ID: <87snlz5cg1.fsf@lovi.inf.elte.hu> (raw)
In-Reply-To: <87wvbb5dwx.fsf@lovi.inf.elte.hu> (NAGY Andras's message of "01 Feb 2001 03:34:54 +0100")

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

> To be honest, I have no idea what the IMAP NAMESPACE thing is good
> for.  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'."

One little addition after reading the NAMESPACE RFC:

This prefix could be figured out by issuing a NAMESPACE command, so
the user could say "the prefix for my personal mailboxes" instead of
"INBOX.".

Nnimap could introduce the `nnimap-prefix' paramter, containing either
a string (the prefix itself) or a symbol (personal, other, shared)
indicating a namespace class from which the prefix should be obtained.
Of course, the latter would yield an error if the namespace class in
question contains more or less than one namespace.


Andras



  reply	other threads:[~2001-02-01  3:06 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 [this message]
2001-02-01 18:37     ` Steven E. Harris
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=87snlz5cg1.fsf@lovi.inf.elte.hu \
    --to=nagya@inf.elte.hu \
    /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).