--981873195-1048915661-1129044955
9446
Content-Type: MULTIPART/MIXED; BOUNDARY="981873195-1048915661-1129044955=:19446"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--981873195-1048915661-1129044955
9446
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <Pine.LNX.4.61.0510111736261.19446 / merlin.cs.kuleuven.ac.be>

On Tue, 11 Oct 2005, David A. Black wrote:

> Hi --
>
> Every time I reply to Brian Schroeder (hi Brian! :-) my post gets
> turned into a multipart mime document, and when I view it (in Pine) I
> get told that it's "Empty or malformed".
>
> And today it happened when I replied to Peter v. N.  See
> http://www.wobblini.net/~dblack/raw.txt to see the whole thing.
>
> Brian posted to that thread too... but I guess that's just coincidence
> (?).
>
> If anyone knows what's causing this, or how to make it stop, please
> let me know.  (I'm not in the market to stop using Pine, so we can
> bypass the discussion of mail readers :-)

I think it has to do with non-ascii characters. Brian Schröäer's name 
contains one such character, and Peter v. N.'s email contains one too ("
la"). My Pine reacts the same (creates a multipart message when replying), 
except it doesn't complain about malformed messages anymore after I 
upgraded to 4.61. I don't know how to make it stop though. I just went 
through all options and didn't see anything relevant, but that may be 
because I haven't got a clue as to why Pine actually does it that way.

Peter
--981873195-1048915661-1129044955
9446--
--981873195-1048915661-1129044955
9446--