…9] . The syntax in this document uses the BNF rules specified in [RFC2045] and [RFC2231]. 3. The 'Codecs' Parameter 3.1. Introduction This section adds a parameter to allow unambiguous specification of all codecs indicated to render the content in the MIME part. This parameter is…

…. The syntax in this document uses the BNF rules specified in [ RFC2045 ] and [ RFC2231 ]. 3 . The 'Codecs' Parameter 3.1 . Introduction This section adds a parameter to allow unambiguous specification of all codecs indicated to render the content in the MIME part. This parameter…

…FC5321], [RFC5322], or the MIME documents [RFC2045], [RFC2047], [RFC2183], and [RFC2231]. This document depends on [RFC5335] and [RFC5504]. Key words used in those documents are used in this document, too. The term "MIME decode" is used for both "encoded-word" decoding defined by…

…, [ RFC5322 ], or the MIME documents RFC2045 ], [ RFC2047 ], [ RFC2183 ], and [ RFC2231 ]. This document depends on [ RFC5335 ] and [ RFC5504 ]. Key words used in those documents are used in this document, too. The term "MIME decode" is used for both "encoded-word" decoding defin…

… }; QTest :: addRow ( "b" ) << QList < QByteArray > { "b" }; QTest :: addRow ( "rfc2231" ) << QList < QByteArray > { "x-kmime-rfc2231" }; QTest :: addRow ( "uuencode" ) << QList < QByteArray > { "x-uuencode" }; QTest :: addRow ( "all" ) << QList < QByteArray > { "b" , "base64" , …

…ns [RFC5321] [RFC5322], or in the MIME documents [RFC2045] [RFC2047] [RFC2183] [RFC2231]. The terms "ASCII address", "internationalized email address", "non-ASCII address", "i18mail address", "UTF8SMTP", "message", and "mailing list" are used with the definitions from [RFC4952]. …

… more restrictive than what is allowed by the ABNF in [RFC2045] and amended by [RFC2231]. Parameter names are case-insensitive and no meaning is attached to the order in which they appear. It is an error for a specific parameter to be specified more than once. There is no defined…

…321 ] [ RFC5322 ], or in the MIME documents RFC2045 ] [ RFC2047 ] [ RFC2183 ] [ RFC2231 ]. The terms "ASCII address", "internationalized email address", "non-ASCII address", "i18mail address", "UTF8SMTP", "message", and "mailing list" are used with the definitions from [ RFC4952 …

…cy systems, this can done by extending the encoding models of [ RFC2045 ] and [ RFC2231 ]. However, our target should be fully internationalized headers, as discussed in [ EAI-UTF8 ]. 4.3 . Downgrading Mechanism for Backward Compatibility As with any use of the SMTP extension mec…

…raditional MIME encoding models for non-ASCII characters in headers RFC2045 ] [ RFC2231 ], but even these should be based on UTF-8, rather than other encodings, if at all possible [ RFC6055 ]. However, the target is fully internationalized message headers, as discussed in RFC6532…

…he IETF EAI working group. o MIME Parameter Value and Encoded Word Extensions [ RFC2231 ] for filenames. Quality IMAP server implementations will automatically combine multipart parameters when generating the BODYSTRUCTURE. There is also some deployed non-standard use of MIME hea…

…" charset "?" encoding "?" encoded-text "?=" Others have been known to follow [ RFC2231 ], to send unencoded UTF-8, or even to send strings encoded in the form-charset. For this reason, interpreting multipart/form-data (even from conforming generators) may require knowing the cha…

…re restrictive than what is allowed by the ABNF in [ RFC2045 ] and amended by [ RFC2231 ]. There is no defined syntax for parameter values. Therefore registrations MUST specify parameter value syntax. Additionally, some transports impose restrictions on parameter value syntax, so…

…cy systems, this can done by extending the encoding models of [ RFC2045 ] and [ RFC2231 ]. However, our target should be fully internationalized headers, as discussed in EAI-UTF8 ]. 4.3 . Downgrading Mechanism for Backward Compatibility As with any use of the SMTP extension mecha…

…he IETF EAI working group. o MIME Parameter Value and Encoded Word Extensions [ RFC2231 ] for filenames. Quality IMAP server implementations will automatically combine multipart parameters when generating the BODYSTRUCTURE. There is also some deployed non-standard use of MIME hea…