allowing spaces in RFC2047 encoded-word headers?

[Michal Szymanski]

Hi,

If mutt can, through rsf2047_parameters variable, allow for encoding of
MIME parameters which (as stated in the manual)
> is explicitly prohibited by
> the standard, but nevertheless encountered in the wild.

could it not allow for something apparently much less 'evil' as the
improper use of literal spaces (instead of underscores) in
RFC2047-encoded headers (e.g. Subject)?

Looks like some mail clients "in the wild" do not change spaces into
underscores when encoding the header lines. As usual, it is the mutt
user (i.e. me) who is to suffer, getting hard-to-read messages.

regards, Michal.