There are several solutions to this by configuring the recipient exchange that is having the problem:
- Solution 1:-Some email servers support the ability to disable bare line feed rejection. .So, check If Bare linefeed rejection is enabled ,that needs to be disabled.
- Solution 2:-Customer can configure the setting -BareLinefeedRejectionEnabled is \$false on the server's Receive connector for internet mail.(If the recipient exchange is having on-premises exchange)
- Solution 3:-Customer can create an inbound transport rule to append a disclaimer to the messages .The disclaimer will append the expected CR-LF combination to the message so that it can be delivered.
- Solution 4:-Customer can Enable Extended SMTP (ESMTP) on the recipient server so that the message can be sent by using CHUNKING or the BDAT command.
Engineering released a new email gateway hotfix to offer a permanent solution to this issue.
emailgtw-2.90-T1-build 59.zip is attached to this KB Article.