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".
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枚der'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
路路路
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".
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
sorry for the bad magic. I'm using gmail if that is of any helpfull information.
regards,
brian
路路路
On 11/10/05, David A. Black <dblack@wobblini.net> 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".
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
Scratch that comment. I just looked at Brian's reply to Peter's post and it was not malformed, but yours supposedly is and so is Ara's, yet Martin's is not. Ara seems to use Pine too. Funny how Pine complains about something it created itself.
Peter
路路路
On Tue, 11 Oct 2005, Peter Vanbroekhoven wrote:
except it doesn't complain about malformed messages anymore after I upgraded to 4.61.
sorry for the bad magic. I'm using gmail if that is of any helpfull information.
I don't think it's related to gmail, I think it's your name that's the
problem. Or more specifically the 枚. Peter v. N.'s post contained an
脿. So I suspect non-ASCII characters to be the cause of this behavior
in Pine. I have no idea how to turn it off though.
I've actually already posted this to ruby-talk, but it hasn't shown up
there yet (or ta least not in my inbox), while it has arrived in clr
for two hours already.
my post gets
my post gets