[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] corruption when attaching all-null files
From: |
David Levine |
Subject: |
Re: [Nmh-workers] corruption when attaching all-null files |
Date: |
Wed, 07 May 2014 19:12:50 -0400 |
Paul F. wrote:
> aside from the logic aspect: i take it that text with a NUL must
> be treated differently than text with an 8th bit set. i assume it
> must be encoded with q-p? (or base64, but q-p would be sufficient?)
Right, NUL is binary, not 8-bit, data. It can be encoded with
q-p, according to RFC 2045 ยง6.7. If the text has a lot of binary
data, it wouldn't be very readable as q-p, so base64 might be a
better choice.
David
- Re: [Nmh-workers] corruption when attaching all-null files, (continued)
- Re: [Nmh-workers] corruption when attaching all-null files, Chad Brown, 2014/05/07
- Re: [Nmh-workers] corruption when attaching all-null files, Eric Gillespie, 2014/05/07
- Re: [Nmh-workers] corruption when attaching all-null files, Lyndon Nerenberg, 2014/05/07
- Re: [Nmh-workers] corruption when attaching all-null files, Lyndon Nerenberg, 2014/05/07
- Re: [Nmh-workers] corruption when attaching all-null files, Ken Hornstein, 2014/05/07
- Re: [Nmh-workers] corruption when attaching all-null files, Lyndon Nerenberg, 2014/05/07
Re: [Nmh-workers] corruption when attaching all-null files, David Levine, 2014/05/07
Re: [Nmh-workers] corruption when attaching all-null files,
David Levine <=
Re: [Nmh-workers] corruption when attaching all-null files, David Levine, 2014/05/07