>>>>> Dmitri Paduchikh wrote:
[...]
>> Agreed.  Aren't there any other application/* types that should
>> not be forced to be encoded by 7bit?  Otherwise, is it better not
>> to force the 7bit encoding to all application/* types?

> Hmm... It is unclear to me whether other application/* (or audio/*,
> image/*, video/*) require protection from this behavior. Although binary
> data most likely isn't 7-bit, it may be 7-bit in principle. IMO, in such
> case it would be preferable to provide safe default behavior and means
> to change it if user wants to. 7bit enforcement breaks both of these
> principles (safe default and user control) thus I would rather remove it
> completely as in the patch below. Are there any situations when it is
> desirable to enforce 7bit?

>> Here are two patches; one is for excluding application/octet-stream,
>> the other is for excluding application/*.

> Thank you. The following patch is a variation of your patches.
[...]

I like it.  I think removing the 7bit enforcement makes it simple,
necessary and sufficient.  Even so, it can be controlled by
customizing `mm-content-transfer-encoding-defaults' if necessary
(though I don't think so).

I'd like to make one more change, which enables a user to change
the encoding by adding the `encoding=' component to a MIME tag
manually like this:

< #part type="application/octet-stream" disposition=inline encoding=7bit>

It will be useful for testing with various encodings.  The patch: