…-8859-1 charset [ ISO-8859-1 ], supporting other charsets only through use of [ RFC2047 ] encoding. In practice, most HTTP header field values use only a subset of the US-ASCII charset [ USASCII ]. Newly defined header fields SHOULD limit their field values to US-ASCII octets. A …

… ASCII printable characters to be somewhat human readable. It is described in [ RFC2047 ]. < RFC6365 Hoffman & Klensin Best Current Practice [Page 29] RFC 6365 Internationalization Terminology September 2011 The quoted printable syntax is generally considered to be a failure at b…

…ISO-8859-1 charset [ISO-8859-1], supporting other charsets only through use of [RFC2047] encoding. Specifications for newly defined fields SHOULD limit their values to visible US-ASCII octets (VCHAR), SP, and HTAB. A recipient SHOULD treat other allowed octets in field content (i…

…ISO-8859-1 charset [ISO-8859-1], supporting other charsets only through use of [RFC2047] encoding. Specifications for newly defined fields SHOULD limit their values to visible US-ASCII octets (VCHAR), SP, and HTAB. A recipient SHOULD treat other allowed octets in field content (i…

…e ISO-8859-1 charset ISO-8859-1 , supporting other charsets only through use of RFC2047 encoding. Specifications for newly defined fields SHOULD limit their values to visible US-ASCII octets (VCHAR), SP, and HTAB. A recipient SHOULD treat other allowed octets in field content (i.…

…ternet Mail Extensions (MIME) Part Two: Media Types", RFC 2046 , November 1996. RFC2047 ] Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047 , November 1996. RFC2183 ] Troost, R., Dorner, S., and K. Moore, …

…e ISO-8859-1 charset ISO-8859-1 , supporting other charsets only through use of RFC2047 encoding. Specifications for newly defined fields SHOULD limit their values to visible US-ASCII octets (VCHAR), SP, and HTAB. A recipient SHOULD treat other allowed octets in field content (i.…

…ncodings-1.317nb3 Unified interface to MIME encoding and decoding p5-Email-MIME-RFC2047-0.97nb8 Encoding of non-ASCII MIME headers p5-Email-MessageID-1.408nb3 Generate world unique message-ids p5-Email-Outlook-Message-0.921nb3 Read Outlook .msg files p5-Email-Reply-1.204nb10 Repl…

…omponents (such as the charset's name) coupled with the 76-character limit in [ RFC2047 ]. Thus, the "limit" might be 50 or more characters, but it could potentially be quite small. The considerations for assigning a buffer limit are: Implementations SHOULD NOT truncate language …

…x *** Fixed incorrect handling of underscores in Quoted-Printable encoding. *** rfc2047_decode() takes into account input and output character sets. ** mh *** (formataddr): Fixed checking for duplicate addresses. ** pop3d: *** Do not save delete marks when exiting on timeout. ** …

…omponents (such as the charset's name) coupled with the 76-character limit in [ RFC2047 ]. Thus, the "limit" might be 50 or more characters, but it could potentially be quite small. The considerations for assigning a buffer limit are: Implementations SHOULD NOT truncate language …

…components (such as the charset's name) coupled with the 76-character limit in [RFC2047]. Thus, the "limit" might be 50 or more characters, but it could potentially be quite small. The considerations for assigning a buffer limit are: Implementations SHOULD NOT truncate language t…

…commended that it be left disabled unless there is good reason to do otherwise. rfc2047_utf8: If enabled, imapd will parse any non-encoded character sequence in MIME header values as UTF8. This is useful for installations that either advertise the UTF8SMTP ( RFC 5335 ) extension …

…used "indexlevel=medium". Valid keys in $PARAMS include: * raw - do not perform RFC2047 decoding of headers Example: [publicinbox "foo"] indexheader = boolean_term:xlabel:X-Label:raw=1 Support for other parameters is not finalized and subject to change. This is a noop with "index…

…omponents (such as the charset's name) coupled with the 76-character limit in [ RFC2047 ]. Thus, the "limit" might be 50 or more characters, but it could potentially be quite small. The considerations for assigning a buffer limit are: Implementations SHOULD NOT truncate language …