When I send mail with line feed characters, I find that some mail servers reject the mail.
If I remove line breaks, it works fine.
Message: Your message contains invalid characters (bare line feed characters) which the email servers at getmail.no don't support.
I have tried replacing line feed with carriage return constant. It works against mail servers that accept line feed, but recipients with mail servers that do not accept line feed receive mail without line breaks.
I use LV 2015. Windows 7.
Can anyone help?
Solved! Go to Solution.
Have you checked to see if the email server will accept the line feeds with an escape character preceding it?
e.g. \ or \\ before the line feed.
it may just be the way that the server is processing the string.
Maybe they are Windows based and insist on Windows line end, which in fact is a carriage return followed by a line feed. For a mail server I would absolutely consider this a bug, but tell that the big guys.
Typically different OSes use different line forward characters,
Unix uses line feed
MacOS uses carriage return
Windows uses carriage return and line feed
When receiving, smart applications should be prepared to accept all of these, while sending out what the underlying OS prefers, unless you state otherwise in the documentation. But a mail sever barking on carriage return or line feed only contents should be considered garbage.
Great. Now it works. My text included "all" cind of line feed. By cleaning up the text strings (code in the image) it's no longer a problem.
Thank's a lot.
Best Regards Stein
You seem to have marked my post number 2 as the solution, but from looking at your fix I would suggest that Rolfk's post 3 is at least as useful and possibly more worthy of being marked as the solution - I think you could mark them both if you wanted to mark up to 2 posts.
(It erks me to take credit away from an uber guru like Rolf )
ERROR: 5126.96.36.199 Invalid Message Content, contains bare linefeeds
Well, all there is a PDF attachment no Text or HTML. I simplified the Code to have no Text to even enter a bare linefeed.
Anyone having problems sending attachments and getting the Bare Linefeed error? This is happening with Exchange Online (O365).