SmarterMail Build 9672 (2026-Jun-25) Notes/Comments/Problems
Problem reported by J. LaDow - 6/25/2026 at 6:07 PM
Submitted
Any takers?

Seems SpamFoo will be another paid add-on...  So we can spend more money fighting the big providers who let the spam out like an avalanche but fight legitimate email coming in all day long...




MailEnable survivor / convert --
Sagar Replied
I saw there are two features: 
SpamFoo Antivirus : currently in Beta version which is free and after that it will be add-on paid version
SPamFoo mail classification: this will be included with out extra cost 
echoDreamz Replied
We updated our gateways to 9672, SmarterMail is assigning SPF (none) scores to all incoming emails. There have not been any SPF failures etc. for over an hour, which does not happen for us, ALL incoming emails are being flagged with _SPF (none).

EDIT: Also scoring NULL SENDER for all incoming emails as well. Disabled the null sender check for now.
Nick Jansen Replied
Same for me, every message for me is also receiving SPF: none and Null Sender on 9672 Enterprise on Ubuntu. I have disabled the SPF and Null Sender checks for now, which will probably result in an increase in accepted spam.
Larry Duran Replied
Employee Post
For the Null Sender check do you guys have it enabled for SMTP blocking or at the spool (after delivery)? Recent changes should have only affected the SMTP Blocking, where it was never performing the check correctly.
Larry Duran
Product Manager 
SmarterTools Inc.
www.smartertools.com 
Zach Sylvester Replied
Employee Post
Hey Guys, 

Thanks for reporting this issue. 
Do you think you could try the following 

  • On the receiving SmarterMail server, go to:
    • Manage → Security → Whitelist
    • Add each gateway IP address and enable IP Bypass before saving.
    • Please include all gateway IPs that may forward mail to this server.
    • This allows SmarterMail to trust the spam results from the gateway instead of re-scanning the forwarded message.
  • Confirm the gateway is adding the spam result header
    • Please verify that the gateway is adding the X-SmarterMail-SmartHostSpam header when forwarding messages.
    • You can check the headers from Webmail by opening the message, clicking the button with the three dots, and selecting View Header.
Please let me know if this helps. 
If you could also open a ticket and send us an example EML that had this issue that would also be helpful for us. 

Kind Regards, 

Zach Sylvester

Software Developer
SmarterTools Inc.
echoDreamz Replied
Our gateways are the ones doing the SPF checks, not the primary server. However, yes, our gateway IPs are in the primary SM server with IP Bypass enabled.

As for null sender, yes, it was enabled for SMTP, not spool, it's not an EML that is having the issues, it is literally every single SMTP transaction into our gateways.
echoDreamz Replied
[2026.06.26] 01:50:04.076 [52.103.2.4][33695234] Connection initiated
[2026.06.26] 01:50:04.076 [52.103.2.4][33695234] rsp: 220 REMOVED
[2026.06.26] 01:50:04.076 [52.103.2.4][33695234] connected at 6/26/2026 1:50:04 AM
[2026.06.26] 01:50:04.076 [52.103.2.4][33695234] Country code: US
[2026.06.26] 01:50:04.148 [52.103.2.4][33695234] cmd: EHLO BYAPR05CU005.outbound.protection.outlook.com
[2026.06.26] 01:50:04.148 [52.103.2.4][33695234] rsp: 250-REMOVED Hello [52.103.2.4]250-SIZE 139810133250-AUTH PLAIN LOGIN CRAM-MD5250-STARTTLS250-8BITMIME250-SMTPUTF8250-DSN250 OK
[2026.06.26] 01:50:04.219 [52.103.2.4][33695234] cmd: STARTTLS
[2026.06.26] 01:50:04.219 [52.103.2.4][33695234] rsp: 220 Start TLS negotiation
[2026.06.26] 01:50:04.445 [52.103.2.4][33695234] cmd: EHLO BYAPR05CU005.outbound.protection.outlook.com
[2026.06.26] 01:50:04.445 [52.103.2.4][33695234] rsp: 250-REMOVED Hello [52.103.2.4]250-SIZE 139810133250-AUTH PLAIN LOGIN CRAM-MD5250-8BITMIME250-SMTPUTF8250-DSN250 OK
[2026.06.26] 01:50:04.518 [52.103.2.4][33695234] cmd: MAIL FROM:<REMOVED@hotmail.com> SIZE=28431
[2026.06.26] 01:50:04.518 [52.103.2.4][33695234] senderEmail(1): REMOVED@hotmail.com
[2026.06.26] 01:50:04.805 [52.103.2.4][33695234] rsp: 554 Sending address not accepted due to spam filter
[2026.06.26] 01:50:04.805 [52.103.2.4][33695234] Mail rejected due to SMTP Spam Blocking: _SPF (10,None), Null Sender (30,failed)
[2026.06.26] 01:50:04.902 [52.103.2.4][33695234] cmd: QUIT
[2026.06.26] 01:50:04.902 [52.103.2.4][33695234] rsp: 221 OK
[2026.06.26] 01:50:04.902 [52.103.2.4][33695234] disconnected at 6/26/2026 1:50:04 AM
Sample SMTP transaction. Below is an SMTP transaction for the same sender, on the same gateway with the same settings just a few days ago...


[2026.06.23] 02:53:55.524 [52.103.23.25][35852085] Connection initiated
[2026.06.23] 02:53:55.524 [52.103.23.25][35852085] rsp: 220 REMOVED
[2026.06.23] 02:53:55.524 [52.103.23.25][35852085] connected at 6/23/2026 2:53:55 AM
[2026.06.23] 02:53:55.524 [52.103.23.25][35852085] Country code: US
[2026.06.23] 02:53:55.586 [52.103.23.25][35852085] cmd: EHLO PH7PR06CU001.outbound.protection.outlook.com
[2026.06.23] 02:53:55.586 [52.103.23.25][35852085] rsp: 250-REMOVEDHello [52.103.23.25]250-SIZE 139810133250-AUTH PLAIN LOGIN CRAM-MD5250-STARTTLS250-8BITMIME250-SMTPUTF8250-DSN250 OK
[2026.06.23] 02:53:55.647 [52.103.23.25][35852085] cmd: STARTTLS
[2026.06.23] 02:53:55.647 [52.103.23.25][35852085] rsp: 220 Start TLS negotiation
[2026.06.23] 02:53:55.841 [52.103.23.25][35852085] cmd: EHLO PH7PR06CU001.outbound.protection.outlook.com
[2026.06.23] 02:53:55.841 [52.103.23.25][35852085] rsp: 250-REMOVEDHello [52.103.23.25]250-SIZE 139810133250-AUTH PLAIN LOGIN CRAM-MD5250-8BITMIME250-SMTPUTF8250-DSN250 OK
[2026.06.23] 02:53:55.919 [52.103.23.25][35852085] cmd: RSET
[2026.06.23] 02:53:55.919 [52.103.23.25][35852085] rsp: 250 OK
[2026.06.23] 02:53:55.996 [52.103.23.25][35852085] cmd: MAIL FROM:<REMOVED@hotmail.com> SIZE=28592
[2026.06.23] 02:53:55.996 [52.103.23.25][35852085] senderEmail(1): REMOVED@hotmail.com
[2026.06.23] 02:53:56.545 [52.103.23.25][35852085] rsp: 250 OK <REMOVED@hotmail.com> Sender ok
[2026.06.23] 02:53:56.545 [52.103.23.25][35852085] Sender accepted. Weight: 0. Block threshold: 30. 
[2026.06.23] 02:53:56.622 [52.103.23.25][35852085] cmd: RCPT TO:<sales@REMOVED>
[2026.06.23] 02:53:57.104 [52.103.23.25][35852085] rsp: 250 OK <sales@REMOVED> Recipient ok
[2026.06.23] 02:53:57.182 [52.103.23.25][35852085] cmd: DATA
[2026.06.23] 02:53:57.182 [52.103.23.25][35852085] Performing PTR host name lookup for 52.103.23.25
[2026.06.23] 02:53:57.182 [52.103.23.25][35852085] PTR host name for 52.103.23.25 resolved as mail-westus3azolkn19010025.outbound.protection.outlook.com
[2026.06.23] 02:53:57.182 [52.103.23.25][35852085] rsp: 354 Start mail input; end with <CRLF>.<CRLF>
[2026.06.23] 02:53:57.260 [52.103.23.25][35852085] senderEmail(2): REMOVED@hotmail.com parsed using FROM: REMOVED <REMOVED@hotmail.com>
[2026.06.23] 02:53:57.260 [52.103.23.25][35852085] Sender accepted. Weight: 0. Block threshold: 30. 
[2026.06.23] 02:53:57.383 [52.103.23.25][35852085] DMARC Results: Passed (Domain: hotmail.com, Reason: SPF: True, DKIM: True, Alignments: 2, Domain: hotmail.com), Reason: SPF: True, DKIM: True, Alignments: 2, Domain: hotmail.com, Reject? False
[2026.06.23] 02:53:57.383 [52.103.23.25][35852085] rsp: 250 OK
[2026.06.23] 02:53:57.383 [52.103.23.25][35852085] Received message size: 11423 bytes
[2026.06.23] 02:53:57.384 [52.103.23.25][35852085] Successfully wrote to the HDR file. (/var/lib/smartermail/Spool/SubSpool7/22408763.hdr)
[2026.06.23] 02:53:57.384 [52.103.23.25][35852085] Data transfer succeeded, writing mail to 22408763.eml (MessageID: <LV2PR19MB9973293BB2982D6A547642600D9EEE2@LV2PR19MB997329.namprd19.prod.outlook.com>)
[2026.06.23] 02:53:57.488 [52.103.23.25][35852085] cmd: QUIT
[2026.06.23] 02:53:57.488 [52.103.23.25][35852085] rsp: 221 OK
[2026.06.23] 02:53:57.488 [52.103.23.25][35852085] disconnected at 6/23/2026 2:53:57 AM
Nick Jansen Replied
Sorry I should have clarified, in my case I'm not using a gateway. The checks are happening on the primary mail server. They were set up for SMTP blocking.
Larry Duran Replied
Employee Post
Ok so it is SMTP blocking related. Turning it off would be best for now. Having the null sender check at the spool should be fine.
Larry Duran
Product Manager 
SmarterTools Inc.
www.smartertools.com 
Gabriele Maoret - SERSIS Replied
This is a blocking issue for us; we cannot update to this release if those two important filters are broken.
It will certainly result in complaints from customers.

Do you have an ETA for a fix?
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
Stefan Mössner Replied
Hi all,

the mobile web UI seems to be very slow with this release. I always see donuts or the login page won't be available fast.

Kind Regards
Sagar Replied
so you need to disable  Null Sender for now which is enable after upgrading this version ?
Cant you pull this version when there is faults related to this? Otherwise people would download it and complain
Gabriele Maoret - SERSIS Replied
I agree...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
Oliver Replied
I also agree.
Sébastien Riccio Replied
+1 x 1000
Sébastien Riccio
System & Network Admin

Michael Wallace Replied
We all Agree to pull this version till the issue is fixed, tested, double tested and then it can be put back on the site.
Gabriele Maoret - SERSIS Replied
To be clear, we're stuck on v. 9623 because of these bugs and the signature image bug in v. 9652.

Until a version with less impactful bugs is released, we won't budge from there...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
David Fisher Replied
Some of my Routing Rules broke with build 9672 too, I am still trying to narrow it down to exact conditions that broke.
Tim Uzzanti Replied
Employee Post
The Null sender issue is fixed and a new Build will be replacing the old one shortly.
Tim Uzzanti
CEO
SmarterTools Inc.
echoDreamz Replied
I assume this also fixes the SPF issue, Tim?
Michael Wallace Replied
Thank you Tim for the update and Team SmarterTools.
Larry Duran Replied
Employee Post
SPF will be fixed as well.
Larry Duran
Product Manager 
SmarterTools Inc.
www.smartertools.com 
echoDreamz Replied
Can confirm - build 9673 fixes null sender/SPF issues. SPF is now properly passing/failing and null senders are no longer occurring on every transaction.
Tim Uzzanti Replied
Employee Post
J. LaDow,

In regard to the comment you opened this thread with:

SpamFoo will be replacing both Cyren and MessageSniffer. SpamFoo is that good, and it's deeply integrated with SmarterMail to provide a seamless experience that most mail servers and hosted mail services simply don't offer.

In addition, we're working with SpamFoo to provide existing Cyren and MessageSniffer customers the SpamFoo add-on for the remainder of their maintenance and support cycle. At the moment, they've agreed to provide a three-month beta period to all customers as we continue to negotiate the terms.

Unlike our current Antispam integrations, SpamFoo provides dashboards with extensive information and functionality for System Administrators, Domain Administrators, and end users.  

The message classifications, which many people have been asking for, are similar to what Gmail offers.  The classifications are remarkably accurate out of the box and continue to improve as users move messages into the appropriate classifications.

SpamFoo also includes phishing protection features that have already helped prevent several scams targeting our employees. It's amazing how much phishing has increased recently and how closely new hires are being tracked by attackers via LinkedIn etc.

For customers currently using external SpamAssassin or rspamd, I'd encourage you to give SpamFoo a try. I receive a few hundred spam messages each day, and maybe 3 to 5 make it through. Best of all, I'm no longer missing legitimate email, which was a much bigger problem for me before when my inbox was littered with spam.

Lastly, I hope you can see that all of these efforts were made to provide our customers with the best solutions while trying to reduce costs.  

Here is a link on how they do what they do: https://spamfoo.com/how-it-works
Tim Uzzanti
CEO
SmarterTools Inc.
Who is Spamfoo? Do they have a website? Where can I find info on this??
Sébastien Riccio Replied
seems it's : https://spamfoo.com
Sébastien Riccio
System & Network Admin

Sébastien Riccio Replied
Any one brave enough tried the new build 9673 ? 
Sébastien Riccio
System & Network Admin

Gabriele Maoret - SERSIS Replied
I'm a little crazy, so I'm trying it now... Fingers crossed!

Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
Sébastien Riccio Replied
I'm a little crazy, so I'm trying it now... Fingers crossed!

Good luck! I'm crossing all available fingers
Sébastien Riccio
System & Network Admin

Gabriele Maoret - SERSIS Replied
At the moment everything seems OK to me...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
Sébastien Riccio Replied
Thanks a lot for the feedback. Happy it went well. I'll still wait a bit though before I pull the trigger...
Sébastien Riccio
System & Network Admin

Jay Dubb Replied
Do we have any Spamfoo pricing hints after the beta is over?
 
Tim Uzzanti Replied
Employee Post
Jay,

Here is an overview on pricing for SmarterMail and SpamFoo. 

Most of you already know that all our competitors basically charge for every mailbox, and most of our competitors are twice as expensive, if not more. 

We know our customers appreciate our licensing approach and REALLY appreciate that they can build behemoth servers with our Unlimitted license.

The Antispam and Cybersecurity world is also primarily per mailbox or per user licensing.

Because we’re trying to avoid industry trends and offer our customers licensing models that are far more flexible and cheaper, it limits what companies we can partner with.  

It’s almost impossible to find an Antispam company who would offer Unlimitted Antispam for an Unlimitted SmarterMail, and our other licensing levels just don’t work with these companies either.  

If we partnered with some of the major Antispam companies, you would be paying more for Antispam than you would for SmarterMail.  And, most of those Antispam companies aren’t much better than Cyren and MessageSniffer and are still based off legacy technologies, unlike SpamFoo.

For this reason, we are working diligently with SpamFoo to offer our customers similar pricing they are familiar with, with Cyren and Message Sniffer.  In addition, SpamFoo offers email classifications, which is a feature that customers have been asking for, for a long while.  

SmarterMail High Availability (HA) is built on a per user model but is priced VERY similarly to how SmarterMail has been sold.  With SmarterMail HA, we look at each node like an Unlimited and work with our partners to provide add-ons for every Node.

SmarterTools works very hard to keep pricing VERY low compared to our competitors, and we negotiate with our partners in the same manner.  We have a few select customers who like to jump all over us because they’re generally pessimistic, but after 20 years of working with us, should realize our efforts but they still like to take every opportunity to demonize us. 

In any case, once we finish our negotiations with SpamFoo, we will be releasing more info on pricing.  
Tim Uzzanti
CEO
SmarterTools Inc.
Why not call it what it is... Its a part of smartermail. Dont call it third party. Call it what it is. 

Google...

The People Involved
Because SpamFoo is tightly integrated into the SmarterMail ecosystem, the key leaders managing its distribution, support, and implementation to the public include the SmarterTools Leadership Team: [1, 2]
  • Tim Uzzanti (CEO): Oversees the strategic corporate partnership and the licensing structure bringing SpamFoo to enterprise mail servers. [1]
  • Grady Werner (CTO): Leads the technical integration of SpamFoo's multi-lingual embedding models and context engine into the SmarterMail architecture. [1, 2]
  • Derek Curtis (CCO): Manages the commercial rollout, customer relations, and beta program communication for the anti-spam add-on. [1, 2]
Tim Uzzanti Replied
Employee Post
Brian,

I'm not sure about everything you included regarding our titles at SmarterTools.

Regarding SpamFoo, it is not part of SmarterMail. It's integrated the same way any third-party product is integrated, just at a much deeper level than we were able to achieve with Cyren or MessageSniffer.

When we negotiate partnerships or integrations, companies constantly try to convince us to make their software part of our core products because that would entitle them to royalties on everything we sell.

We know not everyone wants to pay extra for SpamFoo, which is why it's offered as an add-on rather than being bundled with SmarterMail.

Giving customers the choice of whether or not to include an add-on has always been our preferred approach. Even something as tightly integrated as Email Classification is a SpamFoo feature, not a SmarterMail feature. It's similar to how we license GeoIP location services. If SpamFoo's Email Classification ever stopped meeting our quality standards, we could simply integrate another provider.

Hope this helps.
Tim Uzzanti
CEO
SmarterTools Inc.
Michael Wallace Replied
@Gabriele Maoret - SERSIS: How the new update a couple days later going for your clients? Any updates? Or do you recommend going forward and updating?

Anyone using Linux version with any news?
Thanks.
Gabriele Maoret - SERSIS Replied
Hi Michael! To me it seems ok, no compliants from users at the moment
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)

Reply to Thread

Enter the verification text