The whole BDAT thing seems to be a way of allowing the length of message content to be indicated up front (a bit like Content-Length in HTTP, maybe) instead of a blank CRLF line needing to be detected. SMTPSEND.BareLineFeedsAreIllegal NDR received by Exchange Online or EOP users in Office 365 Dedicated/ITAR Here's what Microsoft have to say about it: Sounds like a delicious combination of Thunderbird's notorious stewardship issues (Mozilla throwing it over the side several times as they doggedly focus on trying to monetise the Web) and Microsoft's celebrated attitudes towards interoperability ("Sorry it broke, why not buy our products instead?"). I've no idea what! I didn't know line feeds were illegal, I'm sure I've been using them for about 40 years now and I'm not in prison yet. The failure was replaced by a retry response because the message was marked for retry if rejected. My e-mail provider says they don't want to allow "bare line feed" messages into their server as there may be a security implication. Last Error: 400 4.4.7 The server responded with: 550 5.6.2 SMTPSEND.BareLinefeedsAreIllegal message contains bare linefeeds, which cannot be sent via DATA. The same sender can send the same message through Thunderbird using a Gmail account and it works, that's the only solution we have at the minute. Looks to have happened overnight following a Thunderbird update by the sender, I have tried to revert to an earlier version but it won't read the profile any more if I do that. Remote Server returned '550 5.6.11 SMTPSEND.BareLinefeedsAreIllegal message contains bare linefeeds, which cannot be sent via DATA and receiving system does not support BDAT' Code: Select all The mail client submitted this message with bare line feeds, which cannot be sent via SMTP protocol DATA command and receiving system does not support BDAT.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |