SpamAssassin Email headers
Problem reported by Jay Altemoos - December 19, 2018 at 9:11 AM
Submitted
This might sound like a stupid question but I am going to ask anyways and explain why I am asking. I apologize in advance that this will be a lengthy post.

So we are currently still using SM Enterprise 15.7.6844. On our setup we have a remote spamassassin server setup and I am wanting to see the email headers that the Remote Spamassassin server writes to the message. I want to be sure emails are scored properly and what rules were triggered from the Remote SpamAssassin server. Currently I am only seeing the email headers that Smarter mail writes. So I was going under the assumption that since we have the SpamAssassin Based pattern matching turned on that maybe it had something to do with that. So I shut it off and I also double checked the settings for each in regards to header log level, this is what they are currently set to:

Remote SpamAssassin:
Header Log level: Score with test names and descriptions

SpamAssassin Based Pattern:
Header Log level: Score only

So with that said, I should see the full header information that the Remote SpamAssassin installation writes and not what SmarterMail is writing. I even went as far as unchecking the SpamAssassin-Based Pattern Matching and I still only get header information from SmarterMail and never get the email headers that my remote spamassassin would write. I even stopped and restarted the SmarterMail service to make sure it took my changes. No change at all, i still get the SmarterMail headers. I will provide a snippet below of what i am talking about.

So I found where the header information is written from SmarterMail, it's under the SmarterTools -> SmarterMail -> Service -> SAData -> 10_default_prefs.cf file on the server itself. So no matter whether the SpamAssassin Based matching is on or off, SmarterMail just keeps on writing it's own headers and ignores the settings I have set under Security -> AntiSpam Administration.

Here's a snippet of what I am talking about:

X-SmarterMail-Spam: SORBS - Spam, SORBS 06 - Recent, Reverse DNS Lookup [Passed], SpamAssassin -4 [raw: -2], SPF_Pass, DK_None, DKIM_Pass, Custom Rules [] 
X-SmarterMail-SpamDetail: Spam detection software, running on the system "XXXXXX", 
X-SmarterMail-SpamDetail: has NOT identified this incoming email as spam.  The original 
X-SmarterMail-SpamDetail: message has been attached to this so you can view it or label 
X-SmarterMail-SpamDetail: similar future email.  If you have any questions, see 
X-SmarterMail-SpamDetail: XXXXXXXX for details. 
X-SmarterMail-SpamDetail: Content preview:  Test w/SpamAssassin Based Pattern matching off. Test w/SpamAssassin 
X-SmarterMail-SpamDetail: Based Pattern matching off. [...] 
X-SmarterMail-SpamDetail: Content analysis details:   (-2.0 points, 5.0 required) 
X-SmarterMail-SpamDetail: pts rule name              description 
X-SmarterMail-SpamDetail: ---- ---------------------- -------------------------------------------------- 
X-SmarterMail-SpamDetail: -0.0 SPF_PASS               SPF: sender matches SPF record 
X-SmarterMail-SpamDetail: 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider 
X-SmarterMail-SpamDetail: (xxxxxxxxx) 
X-SmarterMail-SpamDetail: -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% 
X-SmarterMail-SpamDetail: [score: 0.0000] 
X-SmarterMail-SpamDetail: 0.0 HTML_MESSAGE           BODY: HTML included in message 
X-SmarterMail-SpamDetail: -0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's 
X-SmarterMail-SpamDetail: domain 
X-SmarterMail-SpamDetail: -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature 
X-SmarterMail-SpamDetail: 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid 
X-SmarterMail-TotalSpamWeight: 0 (Trusted Sender - User)

So with the above example, SmarterMail recognizes that I shutoff the SpamAssassin-Based Pattern Matching, but still writes the full headers anyways and ignores the setting I specified.

This is example is what I should expect to see (this is a test email from a different SpamAssassin setup):

X-Spam-Flag: YES
X-Spam-Status: Yes, score=8.8 required=5.1 tests=BAYES_99,BAYES_999,    DKIM_ADSP_NXDOMAIN,FROM_NOT_REPLY,FSL_BULK_SIG,NO_DNS_FOR_FROM,PYZOR_CHECK,    RCVD_IN_RP_RNBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.3.2
X-Spam-Report:
    *  3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100%    
    *      [score: 1.0000]    *  0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100%
    *      [score: 1.0000]    *  0.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address      *      [117.92.165.153 listed in dnsbl.sorbs.net]
    *  1.3 RCVD_IN_RP_RNBL RBL: Relay in RNBL,
    *      [117.92.165.153 listed in bl.score.senderscore.com]
    *  0.0 NO_DNS_FOR_FROM DNS: Envelope sender has no MX or A DNS records
    *  0.9 DKIM_ADSP_NXDOMAIN No valid author signature and domain not in DNS
    *  1.4 PYZOR_CHECK Listed in Pyzor
    *  1.0 RDNS_DYNAMIC Delivered to internal network by host with
    *      dynamic-looking rDNS
    *  0.5 FROM_NOT_REPLY From: and Reply-To: have different domains
    *  0.0 FSL_BULK_SIG Bulk signature with no Unsubscribe
X-Spam-Level: ********
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on electronicart.hu

So with all that said, any idea why SmarterMail just continues to write it's own header information and ignores the settings specified under the AntiSpam Administration?

Reply to Thread