# 550 5.6.11: invalid characters (bare line feeds)

URL: https://iblockspam.com/smtp-errors/550-5-6-11
Last updated: 2026-10-22

Code: 550 5.6.11 (permanent failure, the message bounced)
Provider: Microsoft 365 / Outlook.com

The message contained bare line feed characters, and the destination server doesn't support the SMTP feature needed to accept them, so Microsoft 365 couldn't deliver it.

What the bounce says:

```
Invalid characters
```
The description Microsoft's Exchange Online NDR reference gives for 5.6.11.

Microsoft says you get 5.6.11 because your message contains bare line feeds and the destination email server doesn't support messages with bare line feeds. A bare line feed is a line feed character (LF) that isn't immediately preceded by a carriage return (CR). RFC 5321 is strict here: a line in SMTP ends with CR followed by LF, and conforming implementations must not recognize or generate any other line terminator.

According to Microsoft, a message with bare line feeds can only be sent between servers using SMTP chunking, the BDAT command defined in RFC 3030. If the destination doesn't support BDAT, it can't accept the message. Microsoft 365 used to remove bare line feeds so delivery to older servers would work, but to better support security standards such as DKIM, it no longer does.

So this error usually involves two things at once: an email program or script that writes bare line feeds into the message, and an older receiving server without BDAT support. The sender can avoid the first; only the recipient's admin can fix the second.

## Common causes

- The email program, script or device that created the message used LF instead of CRLF at line ends.
- An attachment or generated content introduced bare line feeds.
- The destination server doesn't support the SMTP BDAT command (chunking), so it can't take such messages.

## How to fix it (sender)

- Send the message from a different email program, such as Outlook on the web, as Microsoft suggests.
- If the original had an attachment, try sending without it to see whether the attachment is the cause.
- If an app or script generates the mail, fix it to end every line with CRLF.
- If that doesn't help, refer the recipient's admin to Microsoft's article on 5.6.11.

## How to fix it (recipient or admin)

- Admins can disable bare line feed rejection where the server supports it; on Exchange Server, Microsoft cites -BareLinefeedRejectionEnabled $false on the internet Receive connector.
- Or upgrade to mail server software that supports the SMTP BDAT command.

**Q: What is a bare line feed in an email?**
A line feed character (LF, ASCII 10) that isn't preceded by a carriage return (CR, ASCII 13). Email lines are supposed to end with CRLF. Some scripts and older programs write only LF, which strict or older servers reject.

**Q: Why does 5.6.11 happen now when the same mail used to work?**
Microsoft says Microsoft 365 used to strip bare line feeds so older servers could accept the mail, but it stopped doing so to better support security standards such as DKIM. Servers without BDAT support now get the message as written and can refuse it.

Sources:
- Fix NDR error 550 5.6.11 in Exchange Online (Microsoft Learn): https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/fix-error-code-550-5-6-11-in-exchange-online
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online (Microsoft Learn): https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/non-delivery-reports-in-exchange-online
- RFC 5321, section 2.3.8: Lines: https://www.rfc-editor.org/rfc/rfc5321#section-2.3.8
- RFC 3030: SMTP Service Extensions for Transmission of Large and Binary MIME Messages (BDAT): https://www.rfc-editor.org/rfc/rfc3030

---

Source: iBlockSpam, https://iblockspam.com/smtp-errors/550-5-6-11 (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt