|
|
Darren New wrote:
> andrel wrote:
>
>> Me neither.
>> For me that is probably because it is uuencoded
>> end my news reader (netscale 7.1) does not support
>> that for reasons beyond me. Perhaps I should
>> instal a plugin or something.
>
>
> Well, the message looks OK to me, except it doesn't decode into a proper
> image.
>
>> I have this problem
>> too often when using these newsgroups. Anyone some
>> suggestions?
>
>
> Usually what happens is someone posts a uuencoded body inside a message
> tagged as content-type:text/plain, and your news reader (being standards
> compilent) says "Oh, plain text, the sender says so even tho it looks
> like it might actually be a uuencoded message."
>
I am not sure about that. My browser displays it as a broken image.
So it knows it is an image.
Ok, I looked into the message file again. There are no mime headers
at all. Could this be the problem? And if so, why do I get a broken
image image.
Confused,
Andrel
Post a reply to this message
|
|