Gnus development mailing list
 help / color / mirror / Atom feed
From: Timothy Brown <tim@tux.org>
Subject: Spam splitting and multiple nnimap methods
Date: Mon, 17 May 2004 17:50:42 -0400	[thread overview]
Message-ID: <20040517175042.B23864@gwyn.tux.org> (raw)

Hi,

I'm a little clueless about Gnus, having just started using it and Emacs a few
months ago.  The manual isn't entirely clear about how best to proceed along
this path.  Basically:

	1) I have multiple IMAP select methods.
	2) I want to do spam filtering via bogofilter and blackholes, and potentially
	   SA later.
	3) I want mail to be "autodetected" and shifted into a spam group.
	4) I will also manually train bogofilter by marking messages as spam.

I'm a little confused about how the options in .gnus and the group customize
options end up interacting.  i've spent hours poring over this and I'm still
not getting anywhere.

I've included my .gnus; i'm wondering if people could give me some pointers
on how best to get this accomplished?  You will note the relevant sections
of my configuration are commented out in order to prevent myself from losing
any more mail. :-)

Thanks,
Tim

; nil select methods

(setq gnus-select-method '(nnnil ""))

; IMAP select methods

[snip, multiple named nnimap methods, with
 -address, -directory, and stream defined for each]

[snip, additional customizations]

;(setq nnimap-split-download-body)    ; download bodies - IMAP
;(setq spam-split-group "INBOX.spam") ; put all spam in this group
;(setq spam-use-blackholes t)         ; use blackholes
;(setq spam-use-bogofilter t)         ; use bogofilter

;(require 'spam)                      ; flip the switch marty
;(spam-initialize)                    ; flip the other switch too, doc

;(setq nnimap-split-inbox '("INBOX"))  ; split messages in INBOX

;(setq nnimap-split-rule 'nnimap-split-fancy) ; fancy splitting

; 
; fancy splitting rulesets
; 

;(setq nnimap-split-fancy '(| 
;                          (: spam-split)
;                          ;; default mailbox
;                          "INBOX"))




             reply	other threads:[~2004-05-17 21:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 21:50 Timothy Brown [this message]
2004-05-18  9:53 ` Jonas Steverud
2004-05-18 12:53   ` Timothy Brown
2004-05-18 13:50     ` Jonas Steverud
2004-05-18 14:02     ` IMAP Splitting with multiple mailboxes (was Re: Spam splitting and multiple nnimap methods) Timothy Brown
2004-05-18 14:13       ` IMAP Splitting with multiple mailboxes Kai Grossjohann
2004-05-18 14:15         ` Timothy Brown
2004-05-18 15:53           ` Kai Grossjohann
2004-05-18 15:58             ` Timothy Brown
2004-05-18 16:14               ` Kai Grossjohann
2004-05-18 14:13     ` Spam splitting and multiple nnimap methods Jonas Steverud
2004-05-18 19:11     ` Ted Zlatanov
2004-05-18 22:19       ` Timothy Brown
2004-05-19 11:36         ` Jonas Steverud
2004-05-19 14:50           ` Ted Zlatanov
2004-05-19 14:48         ` Ted Zlatanov
2004-05-20 10:27       ` Yair Friedman
2004-05-20 18:49         ` Ted Zlatanov
2004-05-22 23:45           ` 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=20040517175042.B23864@gwyn.tux.org \
    --to=tim@tux.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).