From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/56631 Path: main.gmane.org!not-for-mail From: Jonas Steverud Newsgroups: gmane.emacs.gnus.general Subject: Regarding spam.el Date: Tue, 09 Mar 2004 14:49:22 +0100 Organization: The Deciples of Albericht Nibelungen Sender: ding-owner@lists.math.uh.edu Message-ID: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1078840203 19716 80.91.224.253 (9 Mar 2004 13:50:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 Mar 2004 13:50:03 +0000 (UTC) Original-X-From: ding-owner+M5171@lists.math.uh.edu Tue Mar 09 14:49:53 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 1B0hcH-0000Oo-00 for ; Tue, 09 Mar 2004 14:49:53 +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 1B0hc1-0004Lw-00; Tue, 09 Mar 2004 07:49:37 -0600 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1B0hbt-0004Lq-00 for ding@lists.math.uh.edu; Tue, 09 Mar 2004 07:49:29 -0600 Original-Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by justine.libertine.org (Postfix) with ESMTP id E11153A0054 for ; Tue, 9 Mar 2004 07:49:23 -0600 (CST) Original-Received: from c-9f5372d5.036-4-67626721.cust.bredbandsbolaget.se.bredband.net ([213.114.83.173] [213.114.83.173]) by mxfep01.bredband.com with ESMTP id <20040309134922.GNF15586.mxfep01.bredband.com@c-9f5372d5.036-4-67626721.cust.bredbandsbolaget.se.bredband.net> for ; Tue, 9 Mar 2004 14:49:22 +0100 Original-To: ding@gnus.org Mail-Copies-To: never User-Agent: Gnus/5.110001 (No Gnus v0.1) Emacs/21.3 (darwin) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:56631 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:56631 1. Is gnus-group-*-exit-processor-bogofilter obsolete? If so, it should be better marked as such in the info file. Same for all similar obsolete variables. 2. In "Spam ELisp Package Sequence of Events": Second half of fifth paragraph: The `spam-autodetect' and `spam-autodetect-methods'... Yes, what about them? First half of the paragrapg is clear, then a bunch of parameters and varaibles comes out of the blue. What are they used for? What can they be set to? The reader only gets confused. Either a reference to a info node or explaination text is needed. The paragraph after explains it but not very clear. An example woul be very nice. 3. There are several group parameters and variables mentioned in the info file and it is not always obvious which is which. A separate page/node or at the end of one of the nodes with a list of all variables and the corresponding parameters with examples would be a good idea. 4. How do I tell Gnus that nnfolder:Spam is my spam group and that all other groups are ham? There a number of references to a spam-contents variable/parameter but I got all confused trying to figure out what to set it to. And where. Several parts of the info nodes only lists what parameters and variables there are but not what I set them to, what values that are valid. 5. The following paragraph from "Spam ELisp Package Global Variables" is typical for the entire documentation: "When you leave a _spam_ group, all spam-marked articles are marked as expired after processing with the spam processor. This is not done for _unclassified_ or _ham_ groups. Also, any *ham* articles in a spam group will be moved to a location determined by either the `ham-process-destination' group parameter or a match in the `gnus-ham-process-destinations' variable, which is a list of regular expressions matched with group names (it's easiest to customize this variable with `customize-variable gnus-ham-process-destinations'). Each newsgroup specification has the format (REGEXP PROCESSOR) in a standard Lisp list, if you prefer to customize the variable manually. The ultimate location is a group name or names. If the `ham-process-destination' parameter is not set, ham articles are left in place. If the `spam-mark-ham-unread-before-move-from-spam-group' parameter is set, the ham articles are marked as unread before being moved." a. The author gets sidetracked by his own willingness to explain and help the reader, e.g. the "(it's easiest to customize...)" part. It is not uncommon that when the author explains what something is, he then tells the reader how to set the variable/parameter ("use M-x customize-..." or "...G c or G p as usual"). These lengthy side notes cuts up the flow of the text and starts to annoy the reader when he reads it for the umpteenth time. Better to state in the beginning of the Spam nodes that these fascillities can be used and when a reminder is needed, add a short reminder that doesn't side track the reader. b. The explaination of (gnus-)ham-process-destinations is not complete and even confusing. It is a list of regexp matched with group names. In the next sentance it is declared as a (REGEXP PROCESSOR). That is not a list of regexps, it is a list of lists that contains a regexp and a PROCESSOR. What this PROCESSOR is not explained. c. The given information is not consistent with information given a bit further down the page: "When you leave a _ham_ or _unclassified_ group, all *spam* articles are moved to a location determined by either the `spam-process-destination' group parameter or a match in the `gnus-spam-process-destinations' variable, which is a list of regular expressions matched with group names (it's easiest to customize this variable with `customize-variable gnus-spam-process-destinations'). Each newsgroup specification has the repeated format (REGEXP GROUP) and they are all in a standard Lisp list, if you prefer to customize the variable manually. The ultimate location is a group name or names. If the `spam-process-destination' parameter is not set, the spam articles are only expired. The group name is fully qualified, meaning that if you see `nntp:servername' before the group name in the group buffer then you need it here as well." Here the parameter is a list of (REGEXP GROUP). What is the REGEXP matched on? d. In the example section gives the following example: ((spam-process-destination . "nnimap+mail.lifelogs.com:train")) When did a string become a (REGEXP PROCESSOR) or (REGEXP GROUP)? Same goes for (ham-process-destination "nnimap+mail.lifelogs.com:mail" "nnimap+mail.lifelogs.com:trainham") Summary: The entire documentation needs to be fleshed out with examples and a better flow of text. At some places it is more or less just a long list of variable and parameter names which is as penetrable as a brick wall. I'm willing to help with this, but I need to understand how it works before I can do anything about it. -- ( http://hem.bredband.net/steverud/ ! Wei Wu Wei ) ( Meaning of U2 Lyrics, Roleplaying ! To Do Without Do )