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.