From users-return-117258-archive-asf-public=cust-asf.ponee.io@spamassassin.apache.org Sat Feb 3 00:09:19 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id CB35C180608 for ; Sat, 3 Feb 2018 00:09:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BACCC160C57; Fri, 2 Feb 2018 23:09:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0E63C160C49 for ; Sat, 3 Feb 2018 00:09:18 +0100 (CET) Received: (qmail 78420 invoked by uid 500); 2 Feb 2018 23:09:17 -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 78401 invoked by uid 99); 2 Feb 2018 23:09:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2018 23:09:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 790281A0073 for ; Fri, 2 Feb 2018 23:09:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.788 X-Spam-Level: X-Spam-Status: No, score=0.788 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id taGe8B2qXPyC for ; Fri, 2 Feb 2018 23:09:13 +0000 (UTC) Received: from mail2.impsec.org (ga.impsec.org [108.161.139.220]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 3B6C45F1BE for ; Fri, 2 Feb 2018 23:09:13 +0000 (UTC) Received: from athena.impsec.org (localhost [127.0.0.1]) by ga.impsec.org (8.14.7/8.14.7) with ESMTP id w12N991V014388 for ; Fri, 2 Feb 2018 17:09:09 -0600 Received: from athena.impsec.org (tunnel.impsec.org [127.0.0.1]) by athena.impsec.org (8.14.9/8.14.9) with ESMTP id w12N98GU011408 for ; Fri, 2 Feb 2018 15:09:08 -0800 Received: from localhost (jhardin@localhost) by athena.impsec.org (8.14.9/8.14.9/Submit) with ESMTP id w12N98eg011400 for ; Fri, 2 Feb 2018 15:09:08 -0800 X-Authentication-Warning: athena.impsec.org: jhardin owned process doing -bs Date: Fri, 2 Feb 2018 15:09:08 -0800 (PST) From: John Hardin To: users@spamassassin.apache.org Subject: Re: Body rules hit on Subject In-Reply-To: <92d927e8-8603-9bc8-3dc9-1e7c5621abf5@mcgrail.com> Message-ID: References: <92d927e8-8603-9bc8-3dc9-1e7c5621abf5@mcgrail.com> User-Agent: Alpine 2.21 (LNX 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="16648705-351527240-1517612948=:30714" X-Greylist: inspected by milter-greylist-4.5.16 (ga.impsec.org [127.0.0.1]); Fri, 02 Feb 2018 17:09:09 -0600 (CST) for IP:'127.0.0.1' DOMAIN:'localhost' HELO:'athena.impsec.org' FROM:'jhardin@impsec.org' RCPT:'' X-Greylist: Sender IP whitelisted, ACL 245 matched, not delayed by milter-greylist-4.5.16 (ga.impsec.org [127.0.0.1]); Fri, 02 Feb 2018 17:09:09 -0600 (CST) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --16648705-351527240-1517612948=:30714 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 2 Feb 2018, Kevin A. McGrail wrote: > On 2/2/2018 1:41 PM, Alex wrote: >> Hi, >> I recall a conversation in the past about body rules hitting on the >> Subject of an email, but I don't believe there was ever a solution, or >> I otherwise missed it. >> >> It's now affecting me again, and I hoped someone had some ideas on how >> to prevent body rules from hitting on the subject too since it's >> apparently considered part of the message body? > > There is no solution at the moment.  The subject is appended to the body of > the text for rule parsing.  I've added a task I plan to submit for GSOC > consideration to add a tflag to disable this behavior. Globally, or per-rule? -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- Users mistake widespread adoption of Microsoft Office for the development of a document format standard. ----------------------------------------------------------------------- 4 days until the first Falcon Heavy test launch --16648705-351527240-1517612948=:30714--