From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/49666 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: gnus & spamassassin Date: Mon, 27 Jan 2003 12:46:28 -0500 Organization: =?koi8-r?q?=F4=C5=CF=C4=CF=D2=20=FA=CC=C1=D4=C1=CE=CF=D7?= @ Cienfuegos Sender: owner-ding@hpc.uh.edu Message-ID: <4nfzrecwp7.fsf@lockgroove.bwh.harvard.edu> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1043689554 12198 80.91.224.249 (27 Jan 2003 17:45:54 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 27 Jan 2003 17:45:54 +0000 (UTC) Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18dDKS-0003AS-00 for ; Mon, 27 Jan 2003 18:45:52 +0100 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 18dDLM-0004bO-00; Mon, 27 Jan 2003 11:46:48 -0600 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Mon, 27 Jan 2003 11:47:46 -0600 (CST) Original-Received: from sclp3.sclp.com (sclp3.sclp.com [66.230.238.2]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id LAA13399 for ; Mon, 27 Jan 2003 11:47:34 -0600 (CST) Original-Received: (qmail 2203 invoked by alias); 27 Jan 2003 17:46:32 -0000 Original-Received: (qmail 2198 invoked from network); 27 Jan 2003 17:46:32 -0000 Original-Received: from clifford.bwh.harvard.edu (134.174.9.41) by 66.230.238.6 with SMTP; 27 Jan 2003 17:46:32 -0000 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 h0RHkVW13183 for ; Mon, 27 Jan 2003 12:46:31 -0500 (EST) Original-Received: (from tzz@localhost) by lockgroove.bwh.harvard.edu (8.11.6+Sun/8.11.0) id h0RHkTI26332; Mon, 27 Jan 2003 12:46:29 -0500 (EST) Original-To: ding@gnus.org 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: ding@gnus.org In-Reply-To: (Graham Murray's message of "Sun, 26 Jan 2003 22:50:12 +0000") User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 (sparc-sun-solaris2.8) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:49666 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:49666 On Sun, 26 Jan 2003, graham@gmurray.org.uk wrote: > Are there any plans to incorporate an interface into SpamAssassin > (or other spam detectors) into gnus? > > Spamassassin will mark mail which it considers spam (which is, of > course, not infallible) and gnus can split this into a 'spam' > group. This can be done automatically if you write a spam-check-spamassassin function (see spam-check-bogofilter for an example). It would probably be easier for the users to set a boolean than to manually modify the split rules. > However it would be nice if gnus could do 2 additional things:- > > 1) Pass mail in Spam & Ham groups (identified by the configuration > in spam.el) through the spamassassin bayes learner > (sa-learn-spam, sa-learn-nonspam) on group exit - in the same way > as spam.el will pass it through bogfilter and ifile. Can you or someone else provide the relevant functions? See the bogofilter spam/ham processing functions in spam.el, I'm sure spamassassin won't be too different. Basically, spam-assassin-register-spam-routine and spam-assassin-register-ham-routine are needed. I don't mind doing it, but it would probably be better if someone who uses spamassassin could do a sanity check on the parameters - they are much more likely to get the functionality right. Even pseudocode would be helpful, I can do the rest. > 2) Spamassassin (as from V2.50) 'mangles' spam by creating an email > report with the original (suspect) mail as a MIME > (message/rfc822) attachment. It would be useful if gnus had a > feature to 'decode and move' (pipe the mail through 'spamassassin > -d' then action either Bm or Br) manually identified false > positives to a non-spam group. That's possible as an option, I think. spam-ham-move-routine is the function I need to modify; does spam-assassin-demangle-false-positives sound good as an option name? Ted