From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2763 Path: news.gmane.org!not-for-mail From: jesseh@cs.kun.nl (Jesse F. Hughes) Newsgroups: gmane.emacs.gnus.user Subject: Spam.el, ham groups and INBOX Date: Thu, 24 Jul 2003 13:31:52 +0200 Organization: University of Nijmegen, The Netherlands Message-ID: <87r84gf9ef.fsf@phiwumbda.localnet> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1138669077 16252 80.91.229.2 (31 Jan 2006 00:57:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:57:57 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:31:11 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!nsc.no!nextra.com!uio.no!feed.news.nacamar.de!newsfeed.stueberl.de!proxad.net!freenix!ircam.fr!news.completel.fr!nntpfeed-01.ops.asmr-01.energis-idc.net!131.211.28.48.MISMATCH!humbolt.nl.linux.org!news.nl.linux.org!surfnet.nl!kun.nl!wnnews.sci.kun.nl!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: catv2171.extern.kun.nl Original-X-Trace: wnnews.sci.kun.nl 1059046421 21837 131.174.122.171 (24 Jul 2003 11:33:41 GMT) Original-X-Complaints-To: usenet@sci.kun.nl Original-NNTP-Posting-Date: Thu, 24 Jul 2003 11:33:41 +0000 (UTC) Mail-Copies-To: poster X-face: %~L/gE]R-~x=ts~2{uqw2UbIBo"-}9IOSP>u[,.*)zvo,`6A3&E)_wz)[rn^My@(eY(.(7D A8EwTYfhf*u~,Eu,tf6$HN*MY&)u0G=N' x<%)/"s=GZ_BD2Qz9m=S%4v^I+>T|'1{w70ZY=ih,=)kM"Y_}?{%)x0)];K\~@J6m5.EN?>Zh\Xh;Y V|',x(js'Jfq02joVpj|#x User-Agent: Gnus/5.090017 (Oort Gnus v0.17) XEmacs/21.1 (Cuyahoga Valley, linux) Cancel-Lock: sha1:CHHpKgBE1ygoE+LKVpprUw3xIFs= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2903 Original-Lines: 46 X-Gnus-Article-Number: 2903 Tue Jan 17 17:31:11 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2763 Archived-At: Hey ho. I'm just getting started with spam.el. I think my set-up looks okay, but I am not sure that I understand how ham is handled. What is the intended meaning of "ham groups"? I thought that, whenever I have a piece of mail in my INBOX that isn't spam, then I should consider it ham. Therefore, it makes sense to mark the INBOX as a ham group, as long as I am careful to mark each false negative as spam. However, I saw a recent question in the gnus.ding list which worried about whether messages in the INBOX will be processed as ham every time one leaves the group. Here is the excerpt from Ted's response. On Mon, 21 Jul 2003, jklymak@coas.oregonstate.edu wrote: > I didn't want to set my Inbox as a ham group because I didn't > want all the mails in the group processed *every* time I exit > the group. Ah yes, I've been meaning to use the gnus-registry for that, so messages are only processed once. It's not hard, I'm just unable to do it right now. The tracking data needs to be stored in the "extra" field of the registry entry, the rest is already handled by the registry. This suggests that I'm wrong to set my INBOX as a ham group -- or does it? As a rule, I don't fetch previously read messages, so I guess those won't be processed. Of course, once in a while, I enter the group with C-u so that I can search for an old email. I reckon that when I do that, every email fetched is re-processed as ham. But, all those old articles are marked ancient (or expired), not read, deleted, killed, etc. So, they can't be re-processed, can they? Is it or is it not a good idea to have INBOX as a ham group? Thanks for any help. -- "Come on people!!! The US just blew up a lot of people in Iraq, don't you realize that a person with my exposure might just end up dead, by mysterious circumstances?" --James Harris, on the dangers of "proving" Fermat's last theorem