From: Damon Haley <dkh@member.fsf.org>
To: ding@gnus.org
Subject: Respooing nnimap with nnmail-split-fancy
Date: Mon, 18 Jun 2012 16:24:18 -0600 [thread overview]
Message-ID: <868vfkz2b1.fsf@member.fsf.org> (raw)
Hi, I split IMAP mail happily using the following setting, which works
well.
(setq nnimap-split-methods 'nnmail-split-fancy)
But, when I run gnus-summary-respool-article on an IMAP message, I get
prompted with "Backend to use when respooling (default nnmail):"
I then chose "nnimap" but then it won't accept any of my server choices
like 'cu' or provide me with any default choices.
Does the ability to fancy split IMAP mail exist yet? I know my nnmail
respooling works well without any effort.
Here's my IMAP set up:
(setq gnus-select-method
'(nnimap "cu"
(nnimap-address "exchange.university.edu")
(nnimap-stream ssl)
(nnimap-server-port 993)
(nnimap-authenticator login)
(nnir-search-engine imap)
(nnimap-expunge-on-close never)
(nnimap-inbox "INBOX")
)
Thanks,
Damon
next reply other threads:[~2012-06-18 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 22:24 Damon Haley [this message]
2012-06-19 2:32 ` XeCycle
2012-06-19 16:48 ` Damon Haley
2012-06-20 4:58 ` XeCycle
2012-06-20 7:27 ` Andreas Schwab
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=868vfkz2b1.fsf@member.fsf.org \
--to=dkh@member.fsf.org \
--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).