Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: Alberto Luaces <aluaces@udc.es>
Cc: ding@gnus.org
Subject: Re: Moving Split Rules from Gnus 5.13 to NoGnus (IMAP) Not Working
Date: Sat, 08 Jan 2011 22:11:52 +0100	[thread overview]
Message-ID: <24ipxzje1z.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87wrmfch0h.fsf@eps142.cdf.udc.es> (Alberto Luaces's message of "Sat, 08 Jan 2011 20:49:50 +0100")

Alberto Luaces <aluaces@udc.es> writes:

> Aric writes:
>
>> I apologize for this post as it seems that splitting rules have been discussed 
>> very frequently here. However, despite reading up on this I am still not able 
>> to get my splits to work.
>>
>> I have four Imap accounts that use splitting and this had been working just 
>> fine on Gnus 5.13 (Emacs 23.2.1) with adaptive scoring and gnus registry. In 
>> NoGnus no splitting occurs. It will not move emails according to the split 
>> rules, nor will it move incoming follow-ups to the appropriate mailbox based 
>> upon earlier thread locations. Both of these worked fine in 5.13. I see that 
>> 'nnimap-split-inbox' was changed to 'nnimap-inbox', which I did. Any 
>> suggestions or ideas on how to get this working would be great. NoGnus is so 
>> much faster that I prefer to use it over 5.13. 
>>
>> Thanks, Aric
>>
>> Here are my rules for splitting:
>>
>> (setq nnmail-message-id-cache-length '8000)
>> ;; Second trial at split after losing mail
>> ;(setq nnimap-split-inbox '("INBOX" )) ;; regular gnus
>> (setq nnimap-inbox '("INBOX" )) ;; for nognus
>> (setq nnimap-split-predicate "UNDELETED")
>> (setq nnimap-split-crosspost nil)
>> (setq nnimap-split-rule '(
>> 			  ("Mac" ("INBOX" nnimap-split-fancy))
>> 			  ("BOL" ("INBOX" nnimap-split-fancy))
>> 			  ("Speakeasy" ("INBOX" nnimap-split-fancy))
>> 			  ("Mednet" ("INBOX" nnimap-split-fancy))
>> 			  ))
>> ;; this appears necessary for the new gnus
>> (setq nnimap-treat-duplicates 'warn     ; or `delete'
>>       nnmail-cache-accepted-message-ids t
>>       nnimap-split-fancy
>> ;;      '(| (: nnmail-split-fancy-with-parent) <- did nothing upon adding    
>>        '(|                                ;; (2)
>>          (: gnus-registry-split-fancy-with-parent) ;; (3)
>>          ;; splitting rules go here       ;; (4)
>> 	 (any "promed-digest@promedmail.org" "PROMED")
>> 	 (any "zfs-discuss@opensolaris.org" "SunSupport")
>> 	 (any "ggplot2" "RList")
>> [...snip - more of same idea...]
>> 	 "INBOX" 
>> 	 ))
>
> They changed the nnimap-split-rule naming to nnmail-*, but I can't find
> it in the online manual. Take a look at a working posted example:
>
> http://permalink.gmane.org/gmane.emacs.gnus.general/72705

I dont think they have. It exists in addition to.



  reply	other threads:[~2011-01-08 21:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 17:38 Aric
2011-01-08 19:49 ` Alberto Luaces
2011-01-08 21:11   ` Richard Riley [this message]
2011-01-10 21:25     ` Aric
2011-01-11 19:10       ` Lars Magne Ingebrigtsen
2011-01-11 23:11         ` Aric
2011-01-20 20:46         ` Aric
2011-01-21 13:43           ` Michael Welsh Duggan
2011-01-21 17:02             ` Richard Riley
2011-01-21 17:25               ` Michael Welsh Duggan
2011-01-21 20:11             ` Aric

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=24ipxzje1z.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=aluaces@udc.es \
    --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).