Hi,
Tillmann Steinbrecher wrote:
>> FWIW, I believe (and hope) that Mozilla doesn't care about the file
>> extension at all, but goes by MIME type. So if you have control over the
>> program that is *sending* the mail, you can send the file with the
>> extension .nfo but MIME type text/plain, and Mozilla will display it
>> just fine.
>
>
> Yeah, but I sent a .nfo file to myself using Mozilla, and Mozilla didn't
> display it correctly.
Ok I've experimented a little more and here are my findings:
- If I _send_ the file using NS4, then both NS4 and Mozilla display it
inline correctly.
- If I _send_ the file using Mozilla, then both NS4 and Mozilla _don't_
display it inline.
- If the file is sent using Mozilla, the text will be not visible in the
source (just the usual tyBlTWlzc2lvbi stuff); if I send it using NS4,
the text is visible inline all right.
So obviously the problem is not the way text files are displayed, but
the way they sometimes are sent with Mozilla. So my first posting about
this topic was wrong. Still I think the way such files are sent should
be changed.
I think Katsuhiko's [BTW why isn't cut&paste possible from the 'From'
header field with Mozilla? This would be especially useful for pasting
foreign names!] suggestion is also very good; it would be nice to have
an "View attachment as text" menu item, that displays a file as text
_even_ if it's marked as application/octet-stream.
bye,
Tillmann
Additional info, the source of the email sent with Mozilla looks like this:
Subject: test2
Content-Type: multipart/mixed;
boundary="------------080207000102090104000203"
X-Sender: [EMAIL PROTECTED]
X-Mozilla-Status: 8001
X-Mozilla-Status2: 00000000
X-UIDL: em5e9W*Be94(f!!;(od9
This is a multi-part message in MIME format.
--------------080207000102090104000203
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
test2
--
Tillmann Steinbrecher
Webmaster - The Heatsink Guide AnandTech Editor
http://www.heatsink-guide.com http://www.anandtech.com
--------------080207000102090104000203
Content-Type: application/octet-stream;
name="00_nfo_file_from_some_evil_mp3_release_group.nfo"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="00_nfo_file_from_some_evil_mp3_release_group.nfo"
tyBlTWlzc2lvbiC3IGVNaXNzaW9uILcgZU1pc3Npb24gtyBlTWlzc2lvbiC3IGVNaXNzaW9u
... and so on.
