From: Olivier Sirven <the.slaa@gmail.com>
To: ding@gnus.org
Subject: Re: Splitting rules
Date: Thu, 21 Oct 2010 16:41:34 +0200 [thread overview]
Message-ID: <87eibjfw0x.fsf@corwin.home.thebuble.org> (raw)
In-Reply-To: <8762wwh7ts.fsf@corwin.home.thebuble.org>
On 2010-10-20 23:29:03, Olivier Sirven <the.slaa@gmail.com> wrote:
> Hi,
>
> Since the upgrade to No Gnus v0.11 I'm stuck with my splitting rules and
> can't make them to work. Oddly all incoming emails are moved to
> mail.misc group.
>
> The configuration I use (anonymized):
>
>
> (add-to-list 'gnus-secondary-select-methods
> '(nnimap "df"
> (nnimap-inbox "INBOX")
> (nnimap-split-methods
> (
> ("INBOX.toto"
> (lambda(group)
> (message group)
> (and
> (string-match
> "^From: toto@example.com"
> (buffer-string))
> (string-match
> "^Subject:.*toto email"
> (buffer-string)))))
> ("INBOX.tutu"
> "^From: .*tutu@example.com")
> ;; general rule
> ("INBOX.misc" "")
> ))
> (nnir-search-engine imap)
> (nnimap-address "mail.example.com")
> (nnimap-server-port 993)
> (nnimap-stream ssl)
> (nnimap-authinfo-file "~/.authinfo.gpg")
> ))
>
>
> What am I doing wrong here?
After some tests, I found that nnimap-split-methods was not
used. `gnus-summary-respool-trace' allowed me to trace what variable was
used to decide the splitting. And it seems it's
nnmail-split-fancy: destination group change when I update this
variable.
What's weird is that nnmail-split-fancy should be used if and only if
nnmail-split-method is defined to nnmail-split-fancy. Which is not the
case: to make sure I defined it to the same value as
nnimap-split-methods.
Maybe there is a bug somewhere. What file should I look into if I want
to investigate?
--
Olivier
next prev parent reply other threads:[~2010-10-21 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 21:29 Olivier Sirven
2010-10-21 14:41 ` Olivier Sirven [this message]
2010-10-21 15:56 ` Lars Magne Ingebrigtsen
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=87eibjfw0x.fsf@corwin.home.thebuble.org \
--to=the.slaa@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).