Re: should mbox be opened in unibyte mode

[Shenghuo ZHU <zsh@cs.rochester.edu>]

>>>>> "VV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:

VV> "ZSH" == Shenghuo ZHU writes:
ZSH> Multibyte is intentionally enabled in the mbox buffer. I don't
ZSH> know the reason.

VV> i thought a bit on this, and it seems that mbox MUST be opened in
VV> unibyte mode, otherwise the results will be broken.

VV> mbox may contain arbitrary 8-bit data (coming from 8-bit CTT mime
VV> parts e.g. in utf-8). these 8-bit char sequences must not be
VV> interpreted by mule as multibyte chars because this is plain wrong:
VV> these sequences come from random standard registered charsets which
VV> have nothing to do with internal mule encoding. so, the mbox should be
VV> treated as a raw (uni)byte sequence, but not as something that has
VV> relation to internal mule encoding.

I think unibyte mode does not really matter how mbox is opened, but
the coding-system does. Have you tried

(setq nnmbox-file-coding-system 'binary)
(setq nnmbox-active-file-coding-system 'binary)

It might solve the problem.

-- 
Shenghuo