Neil wrote: > Joe wrote: > >> ted jordan wrote: >> >> >>> this used to work...not sure why it's failing now. >>> >>> whenever I put on an attachment, it doesn't convert it properly. For >>> example, if I attach a PDF file (or any other type), when the >>> recipient receives the mail, instead of it being a nicely attached >>> file sitting in the "attachments" window, all you see is the raw data >>> below my typed message. >>> >>> I'll attempt to attach a small file here for u to see. >>> >>> I have checked my mime-types. They all appear to be okay, and this >>> appears to only help me if I have incoming messages. The problem >>> started after I changed my laptop from Mandrake 8.1 to Redhat 7.2. >>> >>> thanx >>> ted >>> >> >> I can see the problem, but have no idea how to solve it in Redhat. The >> source of your message shows - >> >> Content-Type: text/plain; >> name="W0929421.pdf" >> Content-Transfer-Encoding: base64 >> Content-Disposition: inline; >> filename="W0929421.pdf" >> >> The 'Content-Type' indicates that the attachment is 'plain/text' and >> thats the way it is displayed in Netscape 4.x. Should be something >> like 'application/pdf'. Maybe someone will come along and suggest a >> fix. Are you creating the pdf's? Possibly a setting controlling this >> in the software producing the files. >> >> > What happens if you try to open a PDF in Mozilla? Does it display it as > text? Then there's a MIME type mismatch somewhere in your system. > Unfortunately I don't know Linux but you might be able to work around it > by editing your helper application preferences. >
The point here as far as I can see is that mozilla is doing something which is incompatible with itself and other browsers when it sends various types of attatchments. These kinds of attatchments when sent to outlook & other major email clients are coming up as raw data inline - they really shouldn't be doing that. Mails sent from outlook express with attatchments do not show up like that in Mozilla or outlook express. Russell
