From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/57955 Path: main.gmane.org!not-for-mail From: "Ted Zlatanov" Newsgroups: gmane.emacs.gnus.general Subject: Re: wallowing out of the spam quagmire Date: 22 Jun 2004 12:45:42 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Sender: ding-owner@lists.math.uh.edu Message-ID: <4n7jtzy215.fsf@lifelogs.com> References: <4n659lvv05.fsf@lifelogs.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1087923857 8818 80.91.224.253 (22 Jun 2004 17:04:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 22 Jun 2004 17:04:17 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M6496@lists.math.uh.edu Tue Jun 22 19:04:09 2004 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 1Bcogq-0006ec-00 for ; Tue, 22 Jun 2004 19:04:08 +0200 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 1Bcoga-00044k-00; Tue, 22 Jun 2004 12:03:52 -0500 Original-Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1BcogV-00044f-00 for ding@lists.math.uh.edu; Tue, 22 Jun 2004 12:03:47 -0500 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by util2.math.uh.edu with esmtp (Exim 4.30) id 1BcogV-0004NY-2n for ding@lists.math.uh.edu; Tue, 22 Jun 2004 12:03:47 -0500 Original-Received: from mail.bwh.harvard.edu (sysblade0.bwh.harvard.edu [134.174.9.44]) by justine.libertine.org (Postfix) with ESMTP id 038613A003A for ; Tue, 22 Jun 2004 12:03:42 -0500 (CDT) Original-Received: (qmail 17751 invoked from network); 22 Jun 2004 16:57:12 -0000 Envelope-Sender: tzz@lifelogs.com Envelope-Recipients: reader@newsguy.com, ding@gnus.org, Original-Received: from asimov.bwh.harvard.edu (HELO asimov) ([134.174.9.63]) (envelope-sender ) by mail.bwh.harvard.edu (qmail-ldap-1.03) with SMTP for ; 22 Jun 2004 16:57:12 -0000 Mail-Followup-To: "Harry Putnam" , ding@gnus.org Original-To: "Harry Putnam" 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" In-Reply-To: (Harry Putnam's message of "Mon, 21 Jun 2004 20:40:35 -0500") User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:57955 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:57955 On Mon, 21 Jun 2004, reader@newsguy.com wrote: > My usage will probably be the simplest one would find. I want to run > bogofilter against only one group. (My setup described in previous > post) .. that group gets whatever has made it by SA and dozens of my > own procmail rules including splitting out many list-server messages > from dozens of subscribed lists. So this group doesn't get lots of > mail. However, the spam that shows up there though is fairly > sophisticated and will be hard to indentify as spam. (for computer > tools). > > It is readily indentifieable by humans though, so I thought if I showed > enough of it to bogofilter, that filter would eventually become able to > indentify most of it. Maybe that isn't how Bogofilter works..? > > At this stage I'd like to see a few steps that would get this process > started. Something like (examples are made up): > > 1) put (some elisp) in G p of this group (auto-detect I guess) Yes, auto-detect with spam-use-bogofilter. > 2) install bogofilter and set (`bogo-on' to t) You should (setq spam-use-bogofilter t), that's the most important thing BEFORE you call (spam-initialize). > 3) set variables (spam-group "groupname") (ham-group "groupname") Set the group spam/ham classification you mean. You can do that on a topic too, it's easier for many groups. > 4) enter group and mark messages spam or ham > 5) let bogofiter wallow around in spam-group ham-group several times > a day. > Do steps four/five 7,535 times and then bogofilter will know what is > what.... Yes, this is very sensible. Your workflow then is: 1. Enter ham group A with parameters: auto-detect with spam-use-bogofilter spam-process-destination "S" spam-process (spam spam-use-bogofilter) 1.1. mark spam in ham group A (if any was missed by auto-detect) 1.2. quit ham group A 1.3. the marked spam goes to the spam-process-destination, after being processed with the bogofilter processor 2. Enter spam group S with parameters: spam-process-destination nil (just delete spam) ham-process-destination "A" spam-process (ham spam-use-bogofilter) 2.1. mark ham (with a ham-mark, e.g. !) 2.2. quit spam group S 2.3. the marked ham goes to the ham-process-destination, after being processed with bogofilter Specifically regarding the treatment and motion of the spam/ham articles when exiting, you may want to look at the new spam.el and specifically the spam-summary-exit-behavior variable. I also like spam-mark-ham-unread-before-move-from-spam-group set to t, so instead of ! ham is marked unread when it goes to ham group A. I hope that explains things... Ted