RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Reported (1)

RFC 6152, "SMTP Service Extension for 8-bit MIME Transport", March 2011

Source of RFC: yam (app)

Errata ID: 5646
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: HE Zhixiang
Date Reported: 2019-03-04

Section 3 says:

Naturally, the usual SMTP data-stuffing algorithm applies, so that a
content that contains the five-character sequence of
<CR> <LF> <DOT> <CR> <LF>
or a content that begins with the three-character sequence of
<DOT> <CR> <LF>
does not prematurely terminate the transfer of the content.

It should say:

Naturally, the usual SMTP data-stuffing algorithm applies, so that a
content that contains the five-character sequence of
<CR> <LF> <DOT> <CR> <LF>
or a content that begins with the three-character sequence of
<DOT> <CR> <LF>
would prematurely terminate the transfer of the content.

Notes:

RFC 5321, section 4.5.2:
Without some provision for data transparency, the character sequence "<CRLF>.<CRLF>" ends the mail text and cannot be sent by the user.

Report New Errata