Paul J Stevens <[EMAIL PROTECTED]> said: > Ok so probably the mimeparser is adding spurious \r characters > in the string send to the client. > What's your take Aaron?
Yep, it's in the MIME parser. Somewhere, in the MIME parser. Early in the 2.0rc series, I had a fairly elegant and unified mechanism for receiving messages, but the \r, \r\n, \r\r\n, etc. problems with the MIME parser forced us to change to much heftier code that handled messages differently if they came in over the network or from stdin. Once we move to a more robust MIME parser in 2.1, we'll be able to throw differently formatted messages at it and get better results. As for 2.0, we'll just have to figure out a robust hack... Aaron --
