1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W - X
CRLF
Click on the red underlined text to get to the source
... mailbox'.
The term CRLF, in this document, refers to the sequence of the two
ASCII characters CR ...
... token is that "binary" does not require
adherence to any limits on line length or to the SMTP CRLF semantics,
while the bit ...
... base64 a line break must be converted into a CRLF sequence.
Similarly, a CRLF sequence in base64 ...
... line break must be converted into a CRLF sequence.
Similarly, a CRLF sequence in base64 data must be converted to a
quoted-printable ...
... of the data being encoded, must be represented by a (RFC 822std11(-> 2822prop)) line
break, which is a CRLF sequence, in the Quoted-Printable encoding.
...
... content types directly, as described in
Appendix G. In particular, this may apply to plain text material
on systems that use newline conventions other than CRLF
delimiters. Such an implementation is permissible, but the
generation of line breaks ...
... by the user agent. The 76 character
limit does not count the trailing CRLF, but counts all other
characters, including any equal signs.
...
... CR and LF characters as "=0D"
and "=0A", respectively. In particular, a CRLF sequence in binary
data should be encoded as "=0D=0A". Otherwise, if CRLF were
...
... and "=0A", respectively. In particular, a CRLF sequence in binary
data should be encoded as "=0D=0A". Otherwise, if CRLF were
represented as a hard line break, it might be incorrectly decoded on
...
...
quoted-printable := ([*(ptext / SPACE / TAB) ptext] ["="] CRLF)
; Maximum line length of 76 characters excluding CRLF
...
... quoted-printable := ([*(ptext / SPACE / TAB) ptext] ["="] CRLF)
; Maximum line length of 76 characters excluding CRLF
ptext := octet /<any ASCII character ...
... canonical form. In particular, text line breaks must be
converted into CRLF sequences prior to base64 encoding. The important
thing to note is that this may be done directly by the encoder ...
... that the control characters including DEL (0-31, 127) have no defined
meaning apart from the combination CRLF (ASCII values 13 and 10)
indicating a new line. Two of the characters have de facto meanings
...
... Note that the encapsulation boundary must occur at the beginning of a
line, i.e., following a CRLF, and that the initial CRLF is considered
to be attached to the encapsulation ...
... encapsulation boundary must occur at the beginning of a
line, i.e., following a CRLF, and that the initial CRLF is considered
to be attached to the encapsulation boundary rather than part of the
...
... encapsulation boundary rather than part of the
preceding part. The boundary must be followed immediately either by
another CRLF and the header fields for the next part, or by two
CRLFs, in which case there are no header fields ...
... text/plain).
NOTE: The CRLF preceding the encapsulation line is conceptually
attached to the boundary so that it is possible to have a part
...
... encapsulation line is conceptually
attached to the boundary so that it is possible to have a part
that does not end with a CRLF (line break). Body parts that must
be considered to end with line breaks ...
... CRLF
delimiter := "--" boundary CRLF ; taken from Content-Type field.
; There must be no space
...
... ; between "--" and boundary.
close-delimiter := "--" boundary "--" CRLF ; Again, no space
by "--",
...
... epilogue := discard-text ; to be ignored upon receipt.
discard-text := *(*text CRLF)
body-part := <"message" as defined in RFC 822std11(-> 2822prop) ...
... base64 to quoted-printable and vice versa may be
necessary. This may result in the confusion of CRLF sequences with
line breaks in text bodies. As such, the persistence of CRLF ...
... CRLF sequences with
line breaks in text bodies. As such, the persistence of CRLF as
something other than a line break must not be relied on.
...
... local newline conventions. Local newline conventions may not match
the RFC822std11(-> 2822prop) CRLF convention -- systems are known that use plain CR,
plain LF ...
... ; case insensitive
close-delimiter := "--" boundary "--" CRLF;Again,no space by "--",
content := "Content-Type ...
... case-insensitive matching of type and subtype
delimiter := "--" boundary CRLF ;taken from Content-Type field.
; There must be no space
...
... description := "Content-Description" ":" *text
discard-text := *(*text CRLF)
encapsulation ...
...
quoted-printable := ([*(ptext / SPACE / TAB) ptext] ["="] CRLF)
; Maximum line length of 76 characters excluding CRLF
...
... quoted-printable := ([*(ptext / SPACE / TAB) ptext] ["="] CRLF)
; Maximum line length of 76 characters excluding CRLF
stream ...
... converted to a supported character set and lines must be delimited
with CRLF delimiters in accordance with RFC822std11(-> 2822prop). Note that the
restriction on line lengths implied by RFC822std11(-> 2822prop) ...
... appropriate for the converter's output to be expressed using local
newline conventions rather than using the standard RFC822std11(-> 2822prop) CRLF
delimiters.
...
...
9. The formal grammar for multipart bodies has been changed so that
a CRLF is no longer required before the first boundary line.
10. MIME entities ...