On 2026-01-10 at 10:29:55 UTC-0500 (Sat, 10 Jan 2026 15:29:55 +0000) Niamh Holding <[email protected]> is rumored to have said:
Hello Mainly from businesses I do buy from. Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: by iron.holtain.net (Postfix, from userid 1013) id CAD16C0AA2F3; Sun, 4 Jan 2026 07:05:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 iron.holtain.net CAD16C0AA2F3 Received: from localhost by iron.holtain.net with SpamAssassin (version 3.4.6); Sun, 04 Jan 2026 07:05:45 +0000
Here's your problem. Your MTA is doing something to strip all of the Received headers from the message before SpamAssassin is seeing it. This is incompatible with a LARGE number of SpamAssassin tactics and rules. You should fix it so that you still have all of the headers the message had when it arrived when it is handed to SpamAssassin, including (most importantly) the one showing the final SMTP handoff, i.e. to your mail server. If you can't do that, SHOPIFY_IMG_NOT_RCVD_SFY is just one of many rules that will not work as designed. You can try to disable all of the rules that require proper Received headers but I doubt that what remains after such a mass disabling will be very useful. Provenance is fundamental to spam detection.
You are also running an obsolete version of SpamAssassin, but that is not the cause of false positives.
-- Bill Cole
