Sitewide, Restricted learning and Headers to be ignored...

[Joe Borg]

Hi, I’ve got Spamassassin v.2 .63 installed and I’ve been trying to configure sitewide filtering and restricted learning as described in William Stearns’s guide (spamassassin with sendmail). The guide states that:    Add the following to /etc/mail/spamassassin/local.cf . The "bayes_ignore_header" lines tell the bayesian filtering code to ignore the headers your users' mail apps will add in bouncing the message. bayes_ignore_header ReSent-Date bayes_ignore_header ReSent-From bayes_ignore_header ReSent-Message-ID . . .   Now, the Mail Client I’m using is Microsoft Outlook. I’ve sent a normal email through the system and I’ve also bounced an email. The following are the respective headers:   Normal Email __________________________________________________________________________________ From [EMAIL PROTECTED]  Thu Aug 12 10:59:34 2004 Return-Path: <[EMAIL PROTECTED]> Received: from juu ([217.15.97.57])         by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i7C8xUkE017637         for <[EMAIL PROTECTED]>; Thu, 12 Aug 2004 10:59:34 +0200 Message-Id: <[EMAIL PROTECTED]> Reply-To: <[EMAIL PROTECTED]> From: "Joe Borg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: This is a normal mail Date: Thu, 12 Aug 2004 11:01:29 +0200 Organization: DataStream Ltd. MIME-Version: 1.0 Content-Type: multipart/alternative;         boundary="----=_NextPart_000_0009_01C4805B.B80D5FC0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcSASvRGLYJbMmRjTeK7N4NWz2jSog== X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on antispam X-Spam-Level: X-Spam-Status: No, hits=-101.6 required=5.0 tests=BAYES_00,HTML_50_60,         HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE,MSGID_FROM_MTA_SHORT,         USER_IN_WHITELIST autolearn=no version=2.63   This is a multi-part message in MIME format. _____________________________________________________________________________________   Bounced Email __________________________________________________________________________________ From [EMAIL PROTECTED]  Mon Jul 19 08:52:48 2004 Return-Path: <[EMAIL PROTECTED]> Received: from juu ([217.15.97.57])         by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i6J6qjVN002945         for <[EMAIL PROTECTED]>; Mon, 19 Jul 2004 08:52:48 +0200 Message-Id: <[EMAIL PROTECTED]> Reply-To: <[EMAIL PROTECTED]> From: "collin hedrick" <[EMAIL PROTECTED]> Sender: "Joe Borg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Yxbtk Pain Management Resources Date: Mon, 19 Jul 2004 08:54:20 +0200 Organization: DataStream Ltd. MIME-Version: 1.0 Content-Type: text/plain;         charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcRKChjg9x80RJ5hRxan7rFqHRjRig== content-class: urn:content-classes:message x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1441 x-ms-tnef-correlator: x-ms-has-attach: x-uidl: O78!!8dg"!YkH!!b-D"! x-accept-language: en-us X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on antispam X-Spam-Level: X-Spam-Status: No, hits=-97.0 required=5.0 tests=BAYES_40,         MSGID_FROM_MTA_SHORT,USER_IN_WHITELIST autolearn=no version=2.63 _________________________________________________________________________________   Now, as can be observed, the only difference in the header (before the Mime stuff) is:   Sender: "Joe Borg" <[EMAIL PROTECTED]>   I’ve therefore added:   bayes_ignore_header Sender to my local.cf file. Is this ok? What I’m concerned about is that the following headers are not ignored in my configuration, and that they therefore my email address may be used as a shortcut in the bayes database:   From [EMAIL PROTECTED]  Mon Jul 19 08:52:48 2004 Return-Path: <[EMAIL PROTECTED]> Received: from juu ([217.15.97.57])         by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i6J6qjVN002945         for <[EMAIL PROTECTED]>; Mon, 19 Jul 2004 08:52:48 +0200 Message-Id: <[EMAIL PROTECTED]> Reply-To: <[EMAIL PROTECTED]>   Should I be concerned? If so, how can I go about changing the configuration so that my details are all ignored by bayes, whilst spam or ham is still learned? In the meantime, I’ve done a manual whitelist for my email address…   Also related to this problem, I want to restrict who can report to the system. I’ve set-up everything as described in the guide. My hamtrap procmailrc file looks like this:   SHELL=/bin/sh PATH=/bin:/usr/bin PMDIR=$HOME/.procmail LOGABSTRACT=all MAILDIR=$HOME/mail LOGFILE=$PMDIR/proclog VERBOSE=off   #Spamassassin start :0 * > 256000 toobigtoreport   :0c: spamassassin.lock * ^From [EMAIL PROTECTED] * ^Sender: "Joe Borg" <[EMAIL PROTECTED]> | /usr/bin/sa-learn --ham --single --local :0: learned-ham   :0: unauthorized   For some reason, however, the above does not seem to be working. In other words, other users can still report to the system (i.e. the email gets saved in learned-ham as opposed to unauthorized). Does anyone have any idea what I’m doing wrong? Thanks for your help.   Joe ------------------------------------------------ Mr. Joseph Borg Network Engineer DataStream Ltd. Office Direct: 2567 7245 Office General: 2567 7000 URL: <http://www.datastream.com.mt/> This Email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions represented are solely those of the author and do not necessarily represent those of Datastream Ltd. If you are not the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding,printing or copying of this Email is strictly prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake or call +356 21482000 and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or free of errors as information could be intercepted, corrupted, lost, destroyed, delayed or incomplete, and/or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of Email Transmission.