Domain Content Filtering Not Working since Upgrading to 9673 (Jun 26, 2026) and then to 9678 (Jul 1, 2026)

Problem reported by Brantz - 7/3/2026 at 8:27 AM

Resolved

Since upgrading, Domain Settings -> Content Filtering that previously moved mail from specific domains known for spam no longer works. Previously I have fitltered mail from domains like .shop and sent them to Junk Mail are now going to my inbox.

Here's the filter I have that no longer works:

Name: Spam Domains

Match Type: All conditions must be met

Conditions: Condition type, Field: From Address Comparison: Contains

Contains Specific Words or Phrases From Address Contains:

*.shop

.sa.com

.za.com

.goldinsightmarket.com

.ru.com

.mxfactory250.com

.landoftrades.com

.jdstudents.org

.nturalhlth.com

.click

.co.in

Actions -> Move Message -> Junk Mail

12 Replies

Reply to Thread

Douglas Foster Replied

7/3/2026 at 10:43 AM

I have a ticket on this

Using a routing rule as fallback is not working for me either. Build 8673

Sébastien Riccio Replied

7/3/2026 at 11:31 AM

Hello,

Does it affect all content filters ? We have quite a lot of users using content filters and this would be catastrophic and need quick hot fix, or it will be a support ticket mess on our side.

We upgraded from from 9623 to 9673 a few days ago...

Kind regards

Sébastien Riccio

System & Network Admin

https://swisscenter.com

Brantz Replied

7/3/2026 at 12:32 PM

The release notes for 9673 say it was resolved then but when I went to that upgrade that’s when my problems started. I hoped that 9678 would resolve it but it hasn’t. I’ve changed nothing on my end other than the upgrades that started this problem.

Douglas Foster Replied

7/3/2026 at 1:01 PM

Support could not reproduce my problem on their system. My experience is on a SmarterMail Free test systemwith one account and one rule.

Brantz Replied

7/6/2026 at 8:44 AM

NOT RESOLVED:

Here's a delivery log where a message from a .shop domain gets through. Any message from .shop is meant to be routed to Junk by my content filter. I do not see content filtering happening anywhere in the log:

[2026.07.06] 07:13:00.161 [49085286] Delivery started for 6626-6996-12986-1232-@mail.primebooost.shop@mail.primebooost.shop at 7:13:00 AM

[2026.07.06] 07:13:03.162 [49085286] Added to SpamCheckQueue (1 queued; 0/30 processing)

[2026.07.06] 07:13:03.162 [49085286] [SpamCheckQueue] Begin Processing.

[2026.07.06] 07:13:03.163 [49085286] Blocked Sender Checks started.

[2026.07.06] 07:13:03.165 [49085286] Blocked Sender Checks completed.

[2026.07.06] 07:13:03.217 [49085286] Spam Checks started.

[2026.07.06] 07:13:03.227 [49085286] Unable to run SpamAssassin spam checks on server : No Spam Assassin servers available

[2026.07.06] 07:13:03.228 [49085286] Unable to run SpamAssassin spam checks on server : No Spam Assassin servers available

[2026.07.06] 07:13:03.229 [49085286] Unable to run SpamAssassin spam checks on server : No Spam Assassin servers available

[2026.07.06] 07:13:03.230 [49085286] Unable to run SpamAssassin spam checks on server : No Spam Assassin servers available

[2026.07.06] 07:13:03.363 [49085286] Finished running spam checks. Time (non-rbls): 13ms, Time (URIBL/RBLS): 131ms

[2026.07.06] 07:13:03.364 [49085286] Spam Check results: [REVERSE DNS LOOKUP: 2,ReverseFailed], [_SPF: -2,Pass], [HOSTKARMA - BLACKLIST, HOSTKARMA - BROWNLIST, HOSTKARMA - WHITELIST: 0], [FIVE-TEN: 0], [UCEPROTECT LEVEL 3: 0], [SORBS - ABUSE, SORBS - DYNAMIC IP, SORBS - PROXY, SORBS - SOCKS: 0], [SPAMCOP: 0], [UCEPROTECT LEVEL 2: 0], [SPAMHAUS - PBL, SPAMHAUS - PBL2, SPAMHAUS - SBL, SPAMHAUS - XBL, SPAMHAUS - XBL2: 0], [UCEPROTECT LEVEL 1: 0], [_DMARC: 0,passed], [_INTERNALSPAMASSASSIN: 0:0], [_DKIM: 0,Pass], [_ARC: none], [URIBL: 4, 1 results], [SURBL: 4, 1 results]

[2026.07.06] 07:13:03.364 [49085286] Spam Checks completed.

[2026.07.06] 07:13:03.366 [49085286] Removed from SpamCheckQueue (0 queued or processing)

[2026.07.06] 07:13:06.167 [49085286] Added to LocalDeliveryQueue (1 queued; 0/50 processing)

[2026.07.06] 07:13:06.167 [49085286] [LocalDeliveryQueue] Begin Processing.

[2026.07.06] 07:13:06.188 [49085286] Starting local delivery to [MY HIDDEN EMAIL ADDRESS]

[2026.07.06] 07:13:06.353 [49085286] Message saved to MailProcessing directory for [MY HIDDEN EMAIL ADDRESS] File name: 49085286-20003-NOID.tmpmsg

[2026.07.06] 07:13:06.353 [49085286] Process delivery status notification step from local recipient success. Recipient: [MY HIDDEN EMAIL ADDRESS], Notify: [], Delivered: [True], Forwarded: [False], Deleted: False

[2026.07.06] 07:13:06.354 [49085286] Delivery for 6626-6996-12986-1232- [MY HIDDEN EMAIL ADDRESS]@mail.primebooost.shop to [MY HIDDEN EMAIL ADDRESS] has completed (Delivered) Filter: Spam (Weight: 8), Action (Global Level): PrefixSubject

[2026.07.06] 07:13:06.354 [49085286] End delivery to [MY HIDDEN EMAIL ADDRESS] (MessageID: <6jma7gfhnhgo3hd3-wujh4z9t6opawvt8-32ba@primebooost.shop>)

[2026.07.06] 07:13:06.354 [49085286] Removed from LocalDeliveryQueue (0 queued or processing)

[2026.07.06] 07:13:09.168 [49085286] Removing Spool message: Killed: False, Failed: False, Finished: True

[2026.07.06] 07:13:09.169 [49085286] Delivery finished for 6626-6996-12986-1232- [MY HIDDEN EMAIL ADDRESS]@mail.primebooost.shop at 7:13:09 AM [id:49085286]

Andrew Barker Replied

7/6/2026 at 11:38 AM

Employee Post

@Brantz Does your content filter have wildcards enabled? I noticed that your condition has a wildcard on the first potential match, but not on the others.

Andrew Barker
Lead Software Developer
SmarterTools Inc.
www.smartertools.com

Brantz Replied

7/6/2026 at 11:55 AM

Yes, wildcards are enabled.

David Fisher Replied

7/6/2026 at 1:11 PM

@Brantz

I noticed an issue with WildCards and filters with 9672 and posted about it.

Tim admitted to changing the way wildcards work to fix an issue of it not working the correct way. But I just disabled wildcard in the rules and it works fine for me. To me *.shop is the same thing as .shop>

https://portal.smartertools.com/community/a98006/routing-rules-w-wildcards-enabled-broken-in-build-9672.aspx

I use it for Routing Rules, but would imaging it uses the same logic for both areas.

Brantz Replied

7/7/2026 at 7:56 AM

RESOLVED

Thanks @David Fisher Once I disabled wildcards and changed *.shop to just .shop everything started working properly again. Your tip is much appreciated!

David Fisher Replied

7/7/2026 at 10:38 AM

@Brantz

Your welcome, please note, doing .shop for me caught things like shopify.com and shop-something.com

I had to do .shop> in order for it to stop catching those. Unless that has been resolved, it was acting like an automatic wildcard at the end from experience.

Brantz Replied

7/7/2026 at 11:28 AM

I had a similar problem with a pharmacy called shoppersdrugmart.ca so I made a rule to direct that and other domains that were getting caught to my inbox and that rule is the first one in the sequence which solves the issue. I do like knowing about the .shop> syntax though and may give it a try. Thanks again.

Douglas Foster Replied

7/9/2026 at 7:27 AM

My issue is also resolved. Routing rules and Content Filtering rules based on the TO address are looking at the message's TO address visible to the user. In my case, the message was forwarded and the recipient address had no relationship to the TO address, so the filter rule did not apply.

Back to Community Threads

Please leave this box unchecked

Reply to Thread

Enter the verification text