From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: nnimap support for "NAMESPACE" (prefix "INBOX." on
Date: Mon, 01 Mar 2004 15:57:13 -0500 [thread overview]
Message-ID: <4nd67wmgk6.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <86u11ciczp.fsf@PECTOPAH.shenton.org> (Chris Shenton's message of "Fri, 27 Feb 2004 13:38:50 -0500")
I also would like to find the namespace prefix and separator from the
IMAP server. Right now I do this in order to have working splitting:
(setq
nnimap-split-rule '(
("lifelogs" ("INBOX" nnimap-split-fancy)) ; UW IMAP
("sysblade0" ("INBOX" nnimap-courier-split-fancy))) ; Courier
nnimap-courier-split-fancy '(|
; ... omitted ...
(: gnus-registry-split-fancy-with-parent)
(: spam-split 'spam-use-regex-headers)
; ... omitted ...
(: spam-split 'spam-use-blackholes)
;; default mailbox
"INBOX.mail")
nnimap-split-inbox "INBOX"
nnimap-split-fancy '(|
; ... omitted ...
(: gnus-registry-split-fancy-with-parent)
(: spam-split 'spam-use-regex-headers)
; ... omitted ...
(: spam-split)
;; default mailbox
"mail")
)
(defun nnimap-courier-split-fancy ()
(let ((nnimap-split-fancy nnimap-courier-split-fancy)
(spam-split-group "INBOX.spam"))
(nnimap-split-fancy)))
Note I set the spam-split-group also, because it's "spam" by default.
With the namespace prefix this would be simpler. I would still have
separate split rules because the servers have different purposes, but
I wouldn't have to set the spam-split-group explicitly, and I
wouldn't have different mailbox names everywhere.
That being said, I think the Courier model of having a namespace
prefix for private vs. shared vs. public groups is very clean, and I
like it very much.
Ted
prev parent reply other threads:[~2004-03-01 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 18:38 nnimap support for "NAMESPACE" (prefix "INBOX." on courier-imap) Chris Shenton
2004-02-27 19:42 ` nnimap support for "NAMESPACE" (prefix "INBOX." on Simon Josefsson
2004-03-01 20:57 ` Ted Zlatanov [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=4nd67wmgk6.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).