From: Richard Riley <rileyrg@googlemail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: Imap split, does not work (of course)
Date: Wed, 02 Feb 2011 12:25:36 +0100 [thread overview]
Message-ID: <nlhbcmbrv3.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87bp2uap6c.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 02 Feb 2011 07:08:59 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Francis Moreau <francis.moro@gmail.com> writes:
>
> [...]
>
>>> (nnimap-split-methods
>>> (("INBOX.toto" "^From:.*francis.moro@gmail.com")))
>
> [...]
>
>> Could anybody point out some way to debug this ?
>>
>> Any traces to activate to show some revelant stuff ?
>>
>> Thanks
>
> I cannot help you wrt debugging; I can however show you my (abridged)
> configuration which is based on fancy splitting. I never did get
> "not-so-fancy" splitting to work, so I can understand your frustration.
>
> All split related variables in my configuration are here:
>
>
>
> --8<---------------cut here---------------start------------->8---
> (setq
> nnmail-split-fancy
> '(| (to ".*somelist@somehost.org" "lists")
> (from ".*someuser@some.other.host" "people")
> "general"
> )
> nnimap-split-methods 'default
> nnmail-split-methods 'nnmail-split-fancy
> )
> --8<---------------cut here---------------end--------------->8---
>
>
>
If someone could explain the concept of "backend slots" vs using "setq"
it would help me a lot.
I have been unable to see when something should be set with setq and
when things are passed as a parameter to secondary-methods call.
next prev parent reply other threads:[~2011-02-02 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 21:35 Francis Moreau
2011-01-31 21:43 ` Richard Riley
2011-02-01 1:32 ` Lars Ingebrigtsen
2011-02-01 2:16 ` Poll time: IMAP client-side default match (was: Imap split, does not work (of course)) Lars Ingebrigtsen
2011-02-01 9:25 ` Poll time: IMAP client-side default match Rupert Swarbrick
2011-02-01 10:10 ` Lars Ingebrigtsen
2011-02-01 7:34 ` Imap split, does not work (of course) Francis Moreau
2011-02-01 8:04 ` Richard Riley
2011-02-01 8:27 ` Francis Moreau
2011-02-02 8:04 ` Francis Moreau
2011-02-01 19:21 ` Francis Moreau
2011-02-02 7:08 ` Eric S Fraga
2011-02-02 11:25 ` Richard Riley [this message]
2011-02-03 0:13 ` Michael Welsh Duggan
2011-02-03 8:47 ` Steinar Bang
2011-02-03 11:59 ` Richard Riley
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=nlhbcmbrv3.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).