Print Page | Close Window

SPF parser issue in SpamFilter 4.1.2.808 – TXT r

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=7176
Printed Date: 22 October 2026 at 2:03pm


Topic: SPF parser issue in SpamFilter 4.1.2.808 – TXT r
Posted By: alfaproject
Subject: SPF parser issue in SpamFilter 4.1.2.808 – TXT r
Date Posted: 22 October 2026 at 9:59am

Hello LogSat Support,

We are running SpamFilter ISP version 4.1.2.808 on a legacy Windows server and are experiencing SPF rejections for legitimate Atlassian/Jira emails.

Our logs show the following results during the SPF evaluation:

found SPF record for atlassian-bounces.atlassian.net: v=spf1 include:amazonses.com ~all
SPF analysis for amazonses.com done: - none
SPF query result: softfail
SPF analysis for atlassian-bounces.atlassian.net done: - softfail
failed SPF test (softfail) - Disconnecting 76.223.147.183

The sending IP is covered by the published Amazon SES SPF record. The DNS TXT record for amazonses.com is returned as multiple character strings, which must be concatenated when evaluating the SPF record.

We found your official release notes for version 4.7.6.263, which explicitly mention a fix for SPF lookups failing to find a match when a TXT record consists of two or more concatenated strings.

Could you please confirm whether this issue affects version 4.1.2.808 and whether a patch, configuration workaround, or other supported solution is available for this installation?

Upgrading the existing legacy server may require additional compatibility assessment, so we would first like to understand the available options and the safest way to address this specific SPF parsing issue.

We can provide the relevant SMTP logs and DNS record details if required.

Thank you for your assistance.


Replies:
Posted By: LogSat
Date Posted: 22 October 2026 at 12:48pm
Hi alfaproject,

There have been several fixes related to the SPF filter since that 4.1.2.808 build that dates back from 2007. 

I was able to duplicate your issue with it - on that build 4.1.2.808, SpamFilter does indeed mark the email from IP 76.223.147.183 as "softfail" when the sender is in the @atlassian-bounces.atlassian.net domain. I also confirmed that the latest build v4.7.6.301 that is available in the registered user area does correctly mark it as authorized.

For the evaluation, it could be as simple as just backing up and replacing just the two files SpamFilter.exe and SpamFilterSvc.exe with their new version, and adding the "SpamFilter_Service_GUI.exe" that is not present in that old 4.1 version. Should there be any issues, just restore those two files.

If you contact us via email at support@logsat.com we can work to make them available to you so you can test the new version.




-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Print Page | Close Window