From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/56156 Path: main.gmane.org!not-for-mail From: Martin Monsorno Newsgroups: gmane.emacs.gnus.general Subject: Re: problem with bbdb whitelist filtering Date: Thu, 22 Jan 2004 10:53:15 +0100 Sender: ding-owner@lists.math.uh.edu Message-ID: <200401220953.i0M9rFDm020430@loki.exolution.lan> References: <200401120935.i0C9ZbVV024046@loki.exolution.lan> <4nllocri65.fsf@collins.bwh.harvard.edu> <200401130845.i0D8jChq029589@loki.exolution.lan> <4nu12qi348.fsf@collins.bwh.harvard.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1074765240 29626 80.91.224.253 (22 Jan 2004 09:54:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2004 09:54:00 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M4696@lists.math.uh.edu Thu Jan 22 10:53:49 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 1AjbX3-0005Zk-00 for ; Thu, 22 Jan 2004 10:53:49 +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 1AjbWj-0001FQ-00; Thu, 22 Jan 2004 03:53:29 -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 1AjbWZ-0001FI-00 for ding@lists.math.uh.edu; Thu, 22 Jan 2004 03:53:19 -0600 Original-Received: from thor.exolution.de (thor.exolution.de [212.18.2.65]) by justine.libertine.org (Postfix) with ESMTP id DBD363A0037 for ; Thu, 22 Jan 2004 03:53:18 -0600 (CST) Original-Received: from loki.exolution.lan (root@loki.exolution.lan [192.168.1.100]) by thor.exolution.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i0M9rHhj010858; Thu, 22 Jan 2004 10:53:17 +0100 Original-Received: from loki.exolution.lan (monsorno@localhost [127.0.0.1]) by loki.exolution.lan (8.12.3/8.12.3/Debian-6.6) with ESMTP id i0M9rGOC020432; Thu, 22 Jan 2004 10:53:16 +0100 Original-Received: (from monsorno@localhost) by loki.exolution.lan (8.12.3/8.12.3/Debian-6.6) id i0M9rFDm020430; Thu, 22 Jan 2004 10:53:15 +0100 X-Authentication-Warning: loki.exolution.lan: monsorno set sender to monsorno@gmx.de using -f Original-To: Ted Zlatanov In-Reply-To: <4nu12qi348.fsf@collins.bwh.harvard.edu> (Ted Zlatanov's message of "Tue, 20 Jan 2004 18:58:47 -0500") User-Agent: Gnus/5.110002 (No Gnus v0.2) XEmacs/21.4 (Reasonable Discussion, linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:56156 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:56156 Ted, thanks for your help. I try to explain the problem more detailed and hope that you can clear up some points then. So my configuration may not be as spam.el is supposed to be used, but I thought it work anyway: the idea was the following when splitting mail: - Split mails that are considered not to be spam, i.e. mails of mailing-lists, into several folders, without letting spam.el see them. - All the remaining mail should then be checked, if the sender is in the BBDB. I use spam.el for this, by inserting the fancy split rule (: spam-split) after the mailing-list splits, and setting spam-use-BBDB to t - this is the only spam-checking rule I activated. I expected spam.el now to do the following: for every mail in the list if the sender is in the BBDB, add a header 'X-Spammer: white: From: Pit ' if not, do nothing I don't want spam.el to do anything more with the mail. No more extraordinary intelligent spam checks, no moving of mails. Just insert the header, and let my mail splitting go further. - The following split rules should then use the inserted header to move the messages to several groups depending on several rules, and the messages without this header to different groups. I suppose, step 2 is the critical one. I really do not know if spam.el just inserts a header if it finds mail to be clean. But it seems to work in most of the cases. The problem is: sometime such a header is inserted into mails of senders that are _not_ in the bbdb. And it seems, that this happens, when the sender's mail address belongs to my domain. I don't think, that it would help to switch on spam-use-BBDB-exclusive, because it would mark mails explicitly as black, I just want to have white mails marked as white and leave the others. However, I tried this out, nothing changed, at least nothing about the X-Spammer header to be set. So the questions are: 1) Is it possible to do the mail-splitting described? I.e. does spam.el only inserts a header marking it as white, and let my following split rules do the rest? 2) How could it be then, that some messages are marked as white, if their sender is not in the BBDB? BTW: While re-reading the manual, I found an error in the info page 'Spam ELisp Package Sequence of Events' on line 28, talking 2 times about the same variable: ,---- | ... `G p' as usual), and the corresponding variables | `gnus-spam-autodetect-methods' and `gnus-spam-autodetect-methods' | ... `---- -- Martin Monsorno mailto:monsorno@gmx.de