Return-Path: Delivered-To: apmail-spamassassin-users-archive@www.apache.org Received: (qmail 63092 invoked from network); 3 Jun 2010 18:26:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Jun 2010 18:26:50 -0000 Received: (qmail 46419 invoked by uid 500); 3 Jun 2010 18:26:47 -0000 Delivered-To: apmail-spamassassin-users-archive@spamassassin.apache.org Received: (qmail 46396 invoked by uid 500); 3 Jun 2010 18:26:47 -0000 Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 46389 invoked by uid 99); 3 Jun 2010 18:26:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jun 2010 18:26:47 +0000 X-ASF-Spam-Status: No, hits=-0.4 required=10.0 tests=AWL,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.137.4.79] (HELO quad.pendre.co.uk) (195.137.4.79) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jun 2010 18:26:41 +0000 Received: from localhost (Quad [127.0.0.1]) by quad.pendre.co.uk (Postfix) with ESMTP id 2E0F02F4039 for ; Thu, 3 Jun 2010 19:26:19 +0100 (BST) X-Virus-Scanned: amavisd-new at pendre.co.uk Received: from quad.pendre.co.uk ([127.0.0.1]) by localhost (quad.pendre.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0ZkN9mcI88+s; Thu, 3 Jun 2010 19:26:18 +0100 (BST) Received: from [192.168.0.1] (pendre.co.uk [192.168.0.1]) by quad.pendre.co.uk (Postfix) with ESMTP id 9D3D32F4037 for ; Thu, 3 Jun 2010 19:26:18 +0100 (BST) Message-ID: <4C07F3CA.4060501@unixmail.co.uk> Date: Thu, 03 Jun 2010 19:26:18 +0100 From: Ned Slider User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: users@spamassassin.apache.org Subject: Re: yahoo X-YMail-OSG References: <4BE572BB.7090900@secnap.net> <15FCBF80-70D9-4614-AE5D-974A7F6DB4F1@cybernothing.org> <4BF6FE85.7010102@khopis.com> <1274479985.4912.37.camel@monkey> <1274484915.4912.41.camel@monkey> <4BF71EF6.7080704@secnap.net> <4BFB0868.7080404@khopis.com> <4C077577.4020905@unixmail.co.uk> <2772897D-2C57-44D3-BE26-2A7BE0F8D296@kreme.com> In-Reply-To: <2772897D-2C57-44D3-BE26-2A7BE0F8D296@kreme.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 06/03/2010 05:29 PM, LuKreme wrote: > On 3-Jun-2010, at 03:27, Ned Slider wrote: >> >> Can we re-evaluate how useful this is, or maybe exclude To: and CC: headers? > > After several years I have trained all my users to use the Bcc header for any email going to more than 4 or 5 users and to address those emails to themselves. > > To me, this seems like a better solution (but then part of my 'training' was to tell the webmail to disallow sending emails to more than 20 recipients in To/CC). > > Indeed, except it wasn't one of "my users" who stuck 90 addresses in the To field - one of "my users" just happened to be one of the 90 recipients. Who would you suggest I train? :-) I don't believe the genuine intent here is to write a rule to score messages sent "To:" multiple recipients. BTW, I received another such message today that /only/ had 40 recipients and that didn't trigger the rule.