What versions of SmarterMail support BDAT?
Question asked by Jay Altemoos - 8/17/2022 at 2:32 PM
We are currently running SM 15.7.6970 enterprise, there's an issue where a client on Office365 is sending our clients emails and they are getting rejected. The message the sender is getting is "Your message contains invalid characters (bare line feed characters) which the email servers at xxxxxx don't support" Is there any way for the version of SmarterMail we are on not reject these messages? Or do I have to upgrade? I see where the message attempts delivery and then throws a data transfer failed message in our log. I erased out the IP and actual name of the O365 server.

[2022.08.16] 17:35:02 [xx.xx.xx.xx][1541760] cmd: DATA
[2022.08.16] 17:35:02 [xx.xx.xx.xx][1541760] Performing PTR host name lookup for xx.xx.xx.xx
[2022.08.16] 17:35:02 [xx.xx.xx.xx][1541760] PTR host name for xx.xx.xx.xx resolved as mail-xxxxxxxx.outbound.protection.outlook.com
[2022.08.16] 17:35:02 [xx.xx.xx.xx][1541760] rsp: 354 Start mail input; end with <CRLF>.<CRLF>
[2022.08.16] 17:35:02 [xx.xx.xx.xx][1541760] data transfer failed.

Anything I found online so far is the sending server should be inquiring whether or not our server supports BDAT and in our log file I never see our server telling O365 that we support it, so the server should just honor the DATA command correct?

I did see as of this year Microsoft stopped stripping out the bare line feed characters, not sure why, but apprarently it's affecting our server. i did see another post inquiring about the same issue at the beginning of this year:

From what I got out of the post is SM should not be affected but apparently it is. Can anyone shed some light on this?

1 Reply

Reply to Thread
In your log it's using DATA command. So, does work with SM. The command for BDAT it's BDAT and I guess the SM don't support that yet.

Reply to Thread