YAM - Yet Another Mailer (#2) - Word files trashed (#43) - Message List

Word files trashed
 solved

Hello Jens,

I wrote some Word files within MacOSX on my Pegasos, then sent them with YAM, as attachments, to a PC user. They were delivered trashed.

1) This is not a single PC effect. The same happened with any other PC I sent Word files to.

2) This is not related to the Mac version of Word. The same happened even when I attached Word files created on a PC.

3) This is not an effect of a stupid antivirus program or spam checker on PC side. Files are trashed even with every filtering program turned off.

4) Outlook Express & Windows complain and say that the end of the attachment is cut away. Only AFTER, if an antivirus is active, the attachment is marked as suspicious...

5) The same Word files, sent with YAM within zip archives, are received without problems on the same PCs that were unable to read them when they were plain Word attachments.

Well, this should be enough for you to reproduce the problem. I presume that YAM has a little MIME problem or something related...

Cheers, Dr.Morbius

Tree View Flat View (newer first) Flat View (older first)
  • Message #227

    Dear Jens,

    I agree with your previous comment, and I know that you do not have time to lose writing long explanations. However, your sentence:

    The actual problem was that you attached the files with an incorrect "Content-Type: text/x-msdoc" instead of the required "Content-Type: application/msword".

    may suggest to people that I am a crazy user who imagines new exotic MIME types and put them inside YAM just to make the program fail! :-(

    Of course I know from your private email that you did not intend to say this, so I hope you will appreciate that I add a few details for other users that might be curious about the subject.

    (1) I did not set any MIME type in YAM configuration, except "application/pdf" just to select APDF as default viewer for PDF files.

    (2) YAM always tries to use MultiView as default viewer for unknown files, and MultiView always tries to use Amiga datatypes to display files.

    (3) According to (2), since the standard Amiga datatypes do not recognize Word files, YAM also do not recognize such files and classifies them like "Content-Type: application/binary". When this occurs, everything works fine.

    (4) Incidentally I had DocDatatypes installed, which allowed MultiView to read Word files, but also caused YAM to choose the exotic "Content-Type: text/x-msdoc" set by DocDatatypes for Word files.

    (5) Unfortunately, "Content-Type: text/x-msdoc" is not recognized as a valid MIME type on other computer platforms, so Word files sent by YAM in context (4) appear trashed on PCs.

    (6) Problem (5) can be cured either removing DocDatatypes or setting explicitly "Content-Type: application/msword" for #?.doc files in the "Setting -> Configuration... -> MIME" menu of YAM.

    In principle there is the possibility that other undesired interferences may occur between current/future Amiga datatypes and MIME types in YAM. As explained by Jens in the previous comment, the official current way for curing these hypothetical effects is a procedure similar to (6). Anyway, I know that Jens is also investigating other possible ways to completely prevent such rare problems.

    Cheers, Dr.Morbius

  • Message #226

    (1) I always use the latest build of YAM 2.5 alpha.

    (2) Of course I already sent some test messages to myself. YAM is compatible with itself: it reads the .doc diles and they are equal to the originals (compared byte to byte).

    (3) I have sent two messages to your private address. Remember to read the mail with a PC, or ask me for other messages, if it is necessary.

    Ok, after you sent me some example files in private mail, I would like to state here also that the issue seems to be fixed. The actual problem was that you attached the files with an incorrect "content-type: text/x-msdoc" instead of the required "content-type: application/msword". By explicitly adding a #?.doc MIME type to the YAM configuration the issue seems to be fixed.

    So by posting this here I really hope others might not fall over the very same thing in future :)

  • Message #225

    Dear Jens,

    (1) I always use the latest build of YAM 2.5 alpha.

    (2) Of course I already sent some test messages to myself. YAM is compatible with itself: it reads the .doc diles and they are equal to the originals (compared byte to byte).

    (3) I have sent two messages to your private address. Remember to read the mail with a PC, or ask me for other messages, if it is necessary.

    Cheers, Dr.Morbius

  • Message #224

    I wrote some Word files within MacOSX on my Pegasos, then sent them with YAM, as attachments, to a PC user. They were delivered trashed.

    [...]

    Well, this should be enough for you to reproduce the problem. I presume that YAM has a little MIME problem or something related...

    Can you provide me with more info please? Which version of YAM are you using? Can you provide me an example mail? Just send me two mails with an attachment, one where the .doc file is archived in a zip file and one where the .doc file is directly attached and gets malformed as you said. And then also simply try to send that mail yourself (to YAM) again and verify the problem yourself.

Tree View Flat View (newer first) Flat View (older first)

Attachments

No attachments created.