Hello Ian,
We apologize for the inconvenience caused to you.
We will check and help you with this issue.
May I know the version of your Windows operating system and also the AVG Internet Security program version?
Please confirm which email client application you are using.
If possible, could you please share us the screenshot of that email with error message in order to check and help you further?
For taking a screenshot, please refer to this article: https://bit.ly/3A3I5Ru
You can post the screenshot here in your topic. Click on Answer & then click on the Image [mountain symbol] & follow the instructions.
Thank you and keep us updated.
Solution - after an AVG update on 4th August 2022, some of my client’s sent mail was being returned with error code 550 5.6.11 invalid linefeed detected in body of message. The was being caused by the AVG signature appended to email. The mail icon in the signature is a broken link when the message is sent and SMTP protocol adds a CR LF to the message. Some ISPs will reject the message. I successfully sent the same email to a Gmail mail account and noticed that the icon was initially broken and then rendered correctly.
Temporary solution - open AVG dashboard > settings > basic settings > email shield > disable signature
Hello Ian,
We apologize for the inconvenience caused to you.
We will check and help you with this issue.
May I know the version of your Windows operating system and also the AVG Internet Security program version?
Please confirm which email client application you are using.
If possible, could you please share us the screenshot of that email with error message in order to check and help you further?
For taking a screenshot, please refer to this article: https://bit.ly/3A3I5Ru
You can post the screenshot here in your topic. Click on Answer & then click on the Image [mountain symbol] & follow the instructions.
Thank you and keep us updated.
Good call Ian!
We've (my work, where we host a few thousand customer domains) had to advise customers to disable Mail Shield completely… probably 30 or so calls over the last week… due to the stray CRLF injection in the signature component.
Glad to hear we can explicitly disable just the signature, as it's never great to have to advise a client to turn off parts of their A/V scanner!
Hopefully someone at AVG diffs their codebase and fixes the stray LF in the next patch heh