On Fri, 23 Feb 2001 11:27:08, Christof Lange wrote:
> On 22 Feb 01 at 6:01, owner-arachne-digest@arachne wrote:
>> Date: Wed, 21 Feb 2001 23:08:08 -0500
>> From: "Glenn McCorkle" <[EMAIL PROTECTED]>
>> Subject: Re: mime.cfg stuff...
> Thank you, Glenn, for your detailed instructions on how to proceed
> rtf files. I am already used to change mime.cfg once time and again.
> But so far I have never been knowing what I do. Now, with your
> description I have only one problem: it does not work as you
> predicted. I tested it with an email with this attachment:
> Content-Type: application/rtf;
> name="=?iso-8859-2?Q?CHARAKTERISTIKA_=A9KOLY.rtf?="
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: attachment;
> filename="=?iso-8859-2?Q?CHARAKTERISTIKA_=A9KOLY.rtf?="
> My mime.cfg contains:
> text/rtf RTF
> text/enriched >HTM|@call $esystem\\dgi\\rtfview.bat $1 $2
> text/richtext >HTM|@call $esystem\\dgi\\rtfview.bat $1 $2
> application/rtf >HTM|@call $esystem\\dgi\\rtfview.bat $1 $2
> file/.rtf >HTM|@call $esystem\\dgi\\rtfview.bat $1 $2
> Arachne's GUI shows the attachments at the bottom of the email
> with correct declaration, but with wrong file name
> CHARAKTERISTIKA.
> Consequently file/.rtf will not be called to display it. If I change
> the line with application/rtf to its default shape:
> application/rtf RTF
> the attachment proceeds and displays correctly. With this
> change I probably lost another function, but I have tested only
> email.
> Where is the mistake?
You made no mistake.
That is the correct "work-around" to get attachments to decode properly.
The only "lost function" will be the viewing of RTFs on the web which
are sent with "content-type: application/rtf"
Any of them sent with the other 3 content-types will still be viewable.
--
Glenn
http://arachne.cz/
http://freedos-32.sourceforge.net/
http://www.delorie.com/listserv/mime/
http://www.angelfire.com/id/glenndoom/download.htm
