On Mon, Sep 06, 2010 at 10:27:24PM -0400, Ed Blackman wrote:
I've been running all weekend with this patch. It works for both
unencoded "?" and SPACE characters in RFC2047 header lines. I
searched my mail corpus for RFC2047 encoded headers (both strictly
conformant and non-conformant), and co
On Thu, Sep 02, 2010 at 05:10:37PM -0700, Michael Elkins wrote:
On Thu, Sep 02, 2010 at 07:20:18PM -0400, Ed Blackman wrote:
I forwarded the message I copied the headers from, along with a one
that had spaces in the encoded-text, to my work Outlook and to my
Gmail account. Both Outlook and G
On Thu, Sep 02, 2010 at 07:20:18PM -0400, Ed Blackman wrote:
Does mutt rely on the fact that encoded-text shouldn't have "?" or
SPACE because it makes the implementation easier? Or is it just
following the RFC strictly? Reading the RFC, it's not clear to me
*why* encoded-text can't have "?" o
