From: Chris Shenton <chris@shenton.org>
Subject: nnimap support for "NAMESPACE" (prefix "INBOX." on courier-imap)
Date: Fri, 27 Feb 2004 13:38:50 -0500 [thread overview]
Message-ID: <86u11ciczp.fsf@PECTOPAH.shenton.org> (raw)
I'm "No Gnus v0.2" with a couple of courier-imap servers which use an
IMAP namespace of "INBOX.":
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE NEWHORSE GRAPPA UMAMI LAPHROIG] Courier-IMAP ready. Copyright 1998-2003 Double Precision, Inc. See COPYING for distribution information.
2 login USERNAME PASSW0RD
2 OK LOGIN Ok.
3 namespace
* NAMESPACE (("INBOX." ".")) NIL (("shared." "."))
3 OK NAMESPACE completed.
Currently, when ever I want to refert to a server mailbox name (e.g.,
to move from my main inbox to some other) I have to use something like:
nnimap+pectopah:INBOX.list.ding
Gnus defaults the part up to the colon, which is usally good, but I
have to type that INBOX. thing every time. Is there a way to tell
Gnus to find out the namespace from the server and use this as a
prefix so I don't have to?
http://www.lysator.liu.se/~forsberg/docs/Gnus_and_Courier.xml
has some code which hides this display from the user, but IMHO that's
not the right thing -- gnus can figure out the prefix from the server.
Gnus *info* mentions "A note on namespaces" about mutant UoW IMAP
server behavior but doesn't say anything about setting one manually or
automatically.
Does Gnus have a way to determine this from the server? Have it
configured manually? use it when referring to mailbox names, for
retrieval, creation, moving, etc?
Thanks.
next reply other threads:[~2004-02-27 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 18:38 Chris Shenton [this message]
2004-02-27 19:42 ` nnimap support for "NAMESPACE" (prefix "INBOX." on Simon Josefsson
2004-03-01 20:57 ` Ted Zlatanov
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=86u11ciczp.fsf@PECTOPAH.shenton.org \
--to=chris@shenton.org \
/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).