Skip to content
Microsoft (Outlook.com and Microsoft 365) · permanent error

550 5.6.11: message contains bare line feeds

The message contains bare line feeds, and the destination server does not support the SMTP BDAT command needed to accept them.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
550 5.6.11
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
Either side, depending on the cause. Start with the checks below that are yours.
What the server says
550 5.6.11 Invalid characters

What it means

Lines in an email should end with a carriage return followed by a line feed (CR LF). A bare line feed is an LF without the CR. A message that contains them can only be sent with SMTP chunking, the BDAT command from RFC 3030. Microsoft 365 used to remove bare line feeds so older servers could accept such messages, but stopped, to better support standards such as DKIM. So when the destination server lacks BDAT, the message bounces with 5.6.11. Usually the email program that wrote the message added the bare line feeds.

Common causes

  • The email program or application that wrote the message used LF instead of CR LF line endings.
  • An attachment or generated content introduced bare line feeds.
  • The destination server does not support BDAT (SMTP chunking).

How to fix it

  1. 01Send the message from a different program, such as Outlook on the web.
  2. 02If the message had an attachment, try sending it without the attachment.
  3. 03Recipient admins: allow bare line feeds on the receiving server if it has such a setting (on Exchange Server receive connectors, -BareLinefeedRejectionEnabled $false).
  4. 04Or move the receiving server to software that supports BDAT.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

Further reading

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer