https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7132

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #3 from [email protected] ---
Piping the message through spamc does not appear to trigger the problem.
However piping it through spamassassin DOES trigger it. I don't understand why.


#spamc -r -U /var/run/spamd.sock -l -u [email protected] <
/tmp/1423008134.V7d13d4f4I47884M698140.mail:2,S

Content analysis details:   (1.6 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [209.171.16.76 listed in list.dnswl.org]
-0.0 T_RP_MATCHES_RCVD      Envelope sender domain matches handover relay
                            domain
-0.0 SPF_PASS               SPF: sender matches SPF record
 1.6 AWL                    AWL: Adjusted score from AWL reputation of From:
address


#spamassassin --nocreate-prefs --test-mode -d <
/tmp/1423008134.V7d13d4f4I47884M698140.mail:2,S

ontent analysis details:   (3.2 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 3.6 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
                            [1.2.3.4 listed in zen.spamhaus.org]
 1.3 RDNS_NONE              Delivered to internal network by a host with no
rDNS
 0.0 UNPARSEABLE_RELAY      Informational: message has unparseable relay lines
-1.6 AWL                    AWL: Adjusted score from AWL reputation of From:
address


The different AWL result is because the "spamassassin" invocation does not seem
to support sql awl/userprefs/etc. I can not explain the other differences. 



spamass-milter does add a received header to the message before sending it to
spamd. I was able to confirm this using it's debug mode. The received header it
inserts looks something like this (Not from the same message, but found one
from the same ISP. Indentation may be messed up by syslog since it comes
through as 1 line with ^M's):

Received: from cmta19.telus.net (cmta19.telus.net [209.171.16.92])
     by mx1.ctgameinfo.com(8.13.0/8.13.0) with SMTP id unknown;
    Wed, 04 Feb 2015 13:52:29 -0800
       (envelope-from <[email protected]>)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to