> Content-Type: application/octet-stream; name="yarn"
> Content-Transfer-Encoding: base64
> Content-ID: <St9XyUID4D/B088yn@vcn.bc.ca>
> Content-Description: DOS transfer from WP
:
> Content-Type: application/octet-stream; name="yarn_g"
> Content-Transfer-Encoding: base64
> Content-ID: <2t9XyUID4jVT088yn@vcn.bc.ca>
> Content-Description: Generic transfer from WP
As you can see, both attachments although of different file format
have the same Content-Type. With the content type the MIME decoders
assigns the corresponding action to a MIME text. Because they are
identical, the decoder has no chance to decode correctly!
I think this is something missing in Yarn: the assignment (perhaps
automagically) of the correct Content-Type depending on user supplied
information or the file extension - or at least the user should have a
chance to setup the content type manually...
BTW: where from does Nwerthy know the type of your data. Do you have
to enter it, if you are including an attachment?
PS: if your editor cant do 'include file' it is time for a change!
(I doubt, that it is not capable of doing that)
-- Hardy Griech, Kurt-Schumacher-Str. 25/1, D-72762 Reutlingen