SmarterMail Build 9672 (2026-Jun-25) Notes/Comments/Problems
Problem reported by J. LaDow - Today 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
Thia is a blocking issue to us, we cannot update to this release if those two important filters are broken... 
It certainly will result in compliants by 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)

Reply to Thread

Enter the verification text