Happened today for the first time:
Email body not accepted due to the following reason: "Message contains bare LF and is violating 822.bis section 2.3
I was not able to replicate the issue within Gmail or Yahoo. Additionally, my plain text formatting was changed where lots of empty lines were added between paragraphs. Soon after, eM Client crashed.
Any chance you are sending some or part of your message with different encoding? I looked up your error message and on the Internet there are references to em client handles only one, UTF-8, which should accommodate almost all character sets in most languages. In what language is your message? Are you composing a new, fresh message or are you forwarding or pasting in text from somewhere else?
Thanks for replying. I did a look-up too and I didn’t find what you did. But it makes sense.
The email is a reply, but I removed the existing repy from the message body to preserve the email address.
The reply was in English but parts of the original message where in Taiwanese.
The interesting thing when I went to my web based email account, I did the same and I had no issue — there was no error message. eM Client just doesn’t like it and previous replies that did go through (other emails) had the extra Line Feeds (LF). Again, this is seemingly an eM Client issue.
Yeah, I’ll have to leave to the folks at em client for further comment. Your confirming that parts of the original message you were replying to was in Taiwanese may be a clue.
What happens if you start a new message to the same recipient and type something new. If the outgoing message sends OK, then the clue is in the body.
Suggest for a test, to copy an email body contents “that has this issue when you send mail” to eg: Notepad on Windows or Textedit Mac, to first strip out any special characters. Then create a new email and paste that text back into the body of a new email. Then try to send the email to the same person and see if it works.