…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 …

…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 …

…utt's features include: color support message threading MIME support (including RFC2047 support for encoded headers) PGP/MIME (RFC2015) various features to support mailing lists, including list-reply active development community POP3 support IMAP support full control of message h…

…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 …

…n Section 3.3 of [RFC822]), according to the recognition rules in Section 6 of [RFC2047], any time they appear in appropriate places in message headers. Notes: Section 4 of RFC 2049 was not the correct citation. RFC 2060 , "Internet Message Access Protocol - Version 4rev1", Decem…

…n Section 3.3 of [RFC822]), according to the recognition rules in Section 6 of [RFC2047], any time they appear in appropriate places in message headers. Notes: Section 4 of RFC 2049 was not the correct citation. RFC 2060 , "Internet Message Access Protocol - Version 4rev1", Decem…