Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: Michael Welsh Duggan <md5i@md5i.com>
Cc: ding@gnus.org
Subject: Re: Head. Wall. Bang. (imap fancy splitting)
Date: Tue, 21 Dec 2010 12:20:40 +0100	[thread overview]
Message-ID: <ox8vzjjrsn.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87k4j4exl5.fsf@maru.md5i.com> (Michael Welsh Duggan's message of "Mon, 20 Dec 2010 20:14:30 -0500")

Michael Welsh Duggan <md5i@md5i.com> writes:

> Tommy Kelly <tommy.kelly@verilab.com> writes:
>
>> I'm trying to get even a simple fancy split going, so I can build up my
>> understanding from there. But I can't even do that. I'm trying this
>> simple split:
>>
>> (| "TEST-GROUP")
>>
>> My understanding is, that will shove everything into group
>> TEST-GROUP. Yes? Here's how I'm using it:
>>
>> (setq gnus-secondary-select-methods
>>       '(
>> 	(nnimap "work"
>> 		(nnimap-address "imap.gmail.com")
>>  	 	(nnimap-stream ssl)
>> 		(nnimap-server-port 993)
>>
>> 		(nnimap-inbox "INBOX")
>> 		(nnimap-split-methods nnimap-split-fancy)
>> 		(nnimap-split-fancy (| "TEST-GROUP"))
>> 	)
>>       )
>
> Try changing to:
> (setq gnus-secondary-select-methods
>       '((nnimap "work"
>                 (nnimap-address "imap.gmail.com")
>                 (nnimap-stream ssl)
>                 (nnimap-server-port 993)
>                 (nnimap-inbox "INBOX")
>                 (nnimap-split-methods nnmail-split-fancy))))

^^
So no quote here?

> (setq nnmail-split-fancy '(| "TEST-GROUP"))

My fancy mail spam splitting is broken too. I cant figure out if its the
group paremeters not interacting with spam-split or not. I did a M V c
in my INBOX which clears all marks (so they are "unseen" : should the
mail then be treated for spam processing again?) If not, what group
parameter do I need to set? I set the obvious one "Spam Autodetection".

Q1 : How do I mark or unmark my mail so its considered for spam checks
once again? Currently nothing is being processed using the split vars
used below. I have    (setq spam-use-spamassassin t) and the
spam-initialize done.

My fancy split settings are set as

   (setq nnimap-split-inbox '("INBOX"))
   (setq nnimap-split-fancy '(| (: spam-split) "INBOX"))

   (setq nnmail-split-inbox '("INBOX"))
   (setq nnmail-split-fancy '(| (: spam-split) "SYS-INBOX"))

And I'm not getting sequencep errors with this - but possibly since its
not actually doing any splitting at the moment. It all used to work for
me but I wonder if that was more by luck than judgement now.  Having
reset the groups I dont seem to have the magic combo of group parameters
and split variables once more ;( I know my old settings worked as I
shared them with a few people and got them up and running.

So, if anyone is using spam-split could you please report your group
settings and your split variables? It would  be a great help.






      parent reply	other threads:[~2010-12-21 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 23:57 Tommy Kelly
2010-12-21  1:14 ` Michael Welsh Duggan
2010-12-21  1:38   ` Tommy Kelly
2010-12-21  3:49     ` Tommy Kelly
2010-12-21 11:24       ` Richard Riley
2010-12-21 15:26         ` Tommy Kelly
2010-12-21 11:20   ` Richard Riley [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=ox8vzjjrsn.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=ding@gnus.org \
    --cc=md5i@md5i.com \
    /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).