Version info:

                       SmarterMail Enterprise
                       Build 7544 (Aug 27, 2020)

So I've had a rule for a long time to block EHLO localhost.localdomain.  Honestly, that works fine, but since the upgrade I noticed it was set to Direction was set to NONE, which I'm assuming is both incoming/outgoing as it was working on both submission ports and receiving port 25.  Had a client with an iPhone call about not being able to send emails, checked it out and found it was blocked because of this rule.  Deleted the rule and recreated it with it's default Incoming only, but it's still blocking on submission ports.

Example:

[2020.10.02] 17:28:43.034 [100.14.106.141][12491777] rsp: 220 smartermail.truenet.com
[2020.10.02] 17:28:43.034 [100.14.106.141][12491777] connected at 10/2/2020 5:28:43 PM
[2020.10.02] 17:28:43.034 [100.14.106.141][12491777] Country code: US
[2020.10.02] 17:28:43.049 [100.14.106.141][12491777] cmd: EHLO openssl.client.net
[2020.10.02] 17:28:43.049 [100.14.106.141][12491777] rsp: 250-smartermail.truenet.com Hello [100.14.106.141]250-SIZE 104857600250-AUTH LOGIN CRAM-MD5250-STARTTLS250-8BITMIME250-DSN250 OK
[2020.10.02] 17:28:43.065 [100.14.106.141][12491777] cmd: STARTTLS
[2020.10.02] 17:28:43.065 [100.14.106.141][12491777] rsp: 220 Start TLS negotiation
[2020.10.02] 17:28:49.424 [100.14.106.141][12491777] cmd: EHLO localhost.localdomain
[2020.10.02] 17:28:49.424 [100.14.106.141][12491777] rsp: 250-smartermail.truenet.com Hello [100.14.106.141]250-SIZE 104857600250-AUTH LOGIN CRAM-MD5250-8BITMIME250-DSN250 OK
[2020.10.02] 17:28:49.424 [100.14.106.141][12491777] The domain given in the EHLO command violates an EHLO SMTP blocking rule. Any authentication attempts or RCPT commands will be rejected.

Talked to a bunch of other providers and they suggested just blocking it on incoming which make sense, so hoping this can be fixed.