Gnus development mailing list
 help / color / mirror / Atom feed
From: XeCycle <XeCycle@Gmail.com>
To: ding@gnus.org
Subject: Re: Respooing nnimap with nnmail-split-fancy
Date: Wed, 20 Jun 2012 12:58:51 +0800	[thread overview]
Message-ID: <87a9zymvec.fsf@xc.laptop> (raw)
In-Reply-To: <86txy7xn65.fsf@colorado.edu>

[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]

Damon Haley <Damon.Haley@Colorado.EDU> writes:

> XeCycle <XeCycle@Gmail.com> writes:
>
>> Damon Haley <dkh@member.fsf.org> writes:
>>
>>> Hi, I split IMAP mail happily using the following setting, which works
>>> well.
>>>
>>> (setq nnimap-split-methods 'nnmail-split-fancy)
>>
>> See (info "(gnus) Splitting in IMAP"), and search for `fancy'
>> there.  The variable is nnimap-split-rule for me.
>
> Hmm, it looks like the same issue I am experiencing was documented here
> (unresolved):
>
> http://comments.gmane.org/gmane.emacs.gnus.general/74703
>
> I can't see to get rid of this message when trying to repool IMAP
> articles, even when gnus-summary-respool-query is working fine.
>
> Here's the error I get:
>
> "gnus-summary-respool-article: No method given for respooling
>
> Here are my relevant settings:
>
> (setq nnimap-split-methods 'nnmail-split-fancy)

Let me repeat:  The variable is named `nnimap-split-rule' in my
manual.  Check yours.

> (setq gnus-select-method
>       '(nnimap "pu"
>                (nnimap-address "exchange.pu.edu")
>                (nnimap-stream ssl)
>                (nnimap-server-port 993)
>                (nnimap-authenticator login)
>                (nnir-search-engine imap)
>                (nnimap-expunge-on-close never)
>                (nnimap-split-methods default) 
>                (nnimap-inbox "INBOX")))
>
>
> It looks like the select method for nnimap is defined as this:
>
> ("nnimap" post-mail address prompt-address physical-address respool
>  server-marks)
>
> Is there a way to make it stop prompting for a physical-address and just
> do the right thing like mmnl does?
>
> I'm not good enough with elisp to debug this all the way right now, but
> may have more time later.  It does look like a bug to me.  Let me know
> if I should file it as one.
>
> Any help appreciated.
>
> Thanks,
>
> Damon
>
>
>      
>
>

-- 
Carl Lei (XeCycle)
Department of Physics, Shanghai Jiao Tong University
OpenPGP public key: 7795E591
Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2012-06-20  4:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 22:24 Damon Haley
2012-06-19  2:32 ` XeCycle
2012-06-19 16:48   ` Damon Haley
2012-06-20  4:58     ` XeCycle [this message]
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=87a9zymvec.fsf@xc.laptop \
    --to=xecycle@gmail.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).