Re: [art] not an erratum in RFC 6376, was Argh!!!! onto https://www.rfc-editor.org/errata.php

[John Levine <[e-mail]>]

It appears that Steffen Nurpmeso  <[e-mail]> said:
>Hello.
>
>(I take you off the address list since i now always seem to get
>
>  <[e-mail]>: host mx1.taugh.com[64.57.183.56] said:
>    554 5.6.0 Bare CR or LF not accepted. (in reply to end of DATA command)
>
>even though i use postfix 3.9, .. and already before had those new
>configuration settings.)

That means there's something wrong in your mail setup that is sending
bare carriage returns or line feeds. As the saying goes, Don't Do
That. If you really can't figure it out, send me a message from some
non-broken mail system and I can arrange to catch some of the
offending messages and see what's in them.

> |We quite deliberately did not speculate about what one might do with
> |a block of text that is sort of like a 5322 message but isn't one.
>
>But .. that is what happens in real life software? 

The issue of what to do what bare CR and LF has been batted around for
decades, and we have decided that there is no answer better than saying
don't do that if you want to interoperate.

See, for example, the last paragraph on page 13 of RFC 5321, published in 2008.

R's,
John