From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/54634 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: How to use the spam.el package? Date: Mon, 03 Nov 2003 13:37:37 -0500 Organization: =?koi8-r?q?=F4=C5=CF=C4=CF=D2=20=FA=CC=C1=D4=C1=CE=CF=D7?= @ Cienfuegos Sender: ding-owner@lists.math.uh.edu Message-ID: <4nptg947ta.fsf@lockgroove.bwh.harvard.edu> References: <87brrv269g.fsf@emptyhost.emptydomain.de> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1067884820 16711 80.91.224.253 (3 Nov 2003 18:40:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 3 Nov 2003 18:40:20 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M3175@lists.math.uh.edu Mon Nov 03 19:40:18 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AGjcf-0008MN-00 for ; Mon, 03 Nov 2003 19:40:18 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1AGjb4-0003Za-00; Mon, 03 Nov 2003 12:38:38 -0600 Original-Received: from justine.libertine.org ([66.139.78.221]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1AGjb0-0003ZV-00 for ding@lists.math.uh.edu; Mon, 03 Nov 2003 12:38:34 -0600 Original-Received: from clifford.bwh.harvard.edu (clifford.bwh.harvard.edu [134.174.9.41]) by justine.libertine.org (Postfix) with ESMTP id 5AC2E3A0066 for ; Mon, 3 Nov 2003 12:38:32 -0600 (CST) Original-Received: from lockgroove.bwh.harvard.edu (lockgroove [134.174.9.133]) by clifford.bwh.harvard.edu (8.10.2+Sun/8.11.0) with ESMTP id hA3Ic0711981; Mon, 3 Nov 2003 13:38:00 -0500 (EST) Original-Received: (from tzz@localhost) by lockgroove.bwh.harvard.edu (8.11.6+Sun/8.11.0) id hA3Ibbm02099; Mon, 3 Nov 2003 13:37:37 -0500 (EST) Original-To: Kai Grossjohann X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Followup-To: Kai Grossjohann , ding@gnus.org In-Reply-To: <87brrv269g.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Sat, 01 Nov 2003 20:17:15 +0000") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (usg-unix-v) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:54634 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:54634 On Sat, 01 Nov 2003, kai@emptydomain.de wrote: > (setq spam-use-bogofilter-headers t) > (setq spam-split-group "INBOX.spam") > (setq spam-junk-mailgroups (list "nnimap:INBOX.spam" "nnimap:INBOX.makespam")) > (setq gnus-spam-process-newsgroups > '(("^nnimap:INBOX" nil))) > (setq gnus-spam-process-destinations > '(("^nnimap:INBOX" "nnimap:INBOX.makespam"))) > (spam-initialize) You don't need to explicitly define the spam-process parameter - it's nil by default, as one would expect. Everything else looks fine. > I'm reading mail from a Cyrus server with the following setup: > Incoming messages are passed through bogofilter before Cyrus sees > them. There is a cron job which goes through all INBOX.makespam and > INBOX.makeham folders for all users and classifies messages found > there as spam or ham respectively. Great. > So what I want is this: Incoming spam should be split into > nnimap:INBOX.spam. Hitting M-d on a message should send it to the > nnimap:INBOX.makespam group, where it will be picked up by the Cron > job later. Also, marking something as ham in a spam group should > result in that message being moved to nnimap:INBOX, I guess. > (There, nnimap-split-fancy will find it again, and then hopefully > won't consider it spam again.) That's sensible. Just don't try to split spam from INBOX right back into INBOX - that can cause problems. > Things I found: > > * The docs say "First of all, you *must* run the function > `spam-initialize' to autoload `spam.el' and to install the > `spam.el' hooks". In fact, however, it seems that spam-initialize > should come /last/, not first: its behavior depends on the other > variables being set. > > I like obscure jokes just as well as the next person, but maybe a > hint for the uninitiated would be nice? The docs are correct. The behavior of spam-initialize will not be affected by any spam.el variables, except for spam-use-stat which adds some hooks (the spam-use-stat exception should probably be in the manual). > * I /think/ that spam-split-group should be a naked group name > whereas all the other variables should be fully qualified group > names. It isn't made clear in the documentation. You are correct. I have clarified it. > * The format of gnus-spam-process-newsgroups and > gnus-spam-process-destinations isn't made clear, neither in info > nor in C-h v. I suggest to say something like "this should be a > list of newsgroup specifications. Each newsgroup specification > has the format (REGEXP PROCESSOR)". > I found out what to do by running M-x customize-variable RET and > then looking at the resulting Lisp expression, but why not make it > explicit? I have added this clarification. I strongly prefer that users use the customize interface, so I don't want to provide code samples for setting the variables manually. If you do, please write them and add them to the manual. I have no problem with that. > * I wasn't sure that just setting the processor to nil was the right > thing to do, I was just operating on a hunch that it might work. > How about making this explicit, too? Why? It makes perfect sense that if you don't explicitly set a processor, there won't be one. I don't want to confuse the users more than they need to be :) > * I would also appreciate some tutorial kind of advice, like saying > for the following common situation, this is how you set the > variables. It's difficult to figure out how it all ties together: > you have to read all of the main node on spam.el and /understand/ > it, too, if you want to configure things. Sure. I welcome any contributions in that direction. Integration of spam.el with the registry plus making the registry work properly in all cases are higher on my priority list. > * How do I tell spam.el that messages from nnimap:INBOX.spam and > nnimap:INBOX.makespam don't need to be frobbed further? I'm > afraid they'll be subjected to gnus-spam-process-destinations... If the messages in those groups are marked as spam, they will be moved to the spam-process-destination whether there is or isn't a spam processor. So don't set a spam-process-destination if you don't want one, ditto for the spam-processor. Is that what you're asking? > * I completely ignored the group parameters thing, even though it > seemed the easiest way to configure stuff. The reason for doing > so was that I didn't fancy setting the same spam process > destination on all my groups. (I just switched to a new server > and haven't switched on topics mode, yet.) Yeah, unfortunately group/topic parameters are incredibly easy and convenient for this task, so I'd rather have the user use that than write Lisp code. > I hope that the above stupid questions are useful for something. > I'd like to promise to help improving the documentation, but what > with real life and a job, my time has been more limited than some > months ago. No problem, I appreciate the suggestions. Ted