[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] warning when attaching rfc822 message
From: |
David Levine |
Subject: |
Re: [Nmh-workers] warning when attaching rfc822 message |
Date: |
Sun, 13 Apr 2014 20:46:46 -0400 |
> Okay, so I looked at this. It looks like the simplest thing to do
> is make init_decoded_content() set a default CTE (probably 7bit is
> appropriate).
But 8bit would be safe more often. Is there any harm nowadays
in saying that a 7bit message is 8bit?
> But as always ... there's a wrinkle. It looks like we always set a
> CTE of 7bit for message/rfc822 parts. But as I read it, that's not
> correct if the message/rfc822 contains 8-bit characters; in that
> case it should be 8bit (or perhaps binary, but we don't really
> handle encoding anything in binary). Do other people agree with my
> reading of RFC 2046? If so, that change should be simple.
I'd say go for it if it's simple. It certainly seems like
an improvement.
David
- Re: [Nmh-workers] warning when attaching rfc822 message,
David Levine <=