Voici une précision (à défaut d'une solution ,hélas) extraite de
http://discussions.info.apple.com
Jon Richardson RE(1): RE: Mail Attachments - Explanation
(msg # 3.2: Posted Sep 19, 02 4:33 am)
Posts: 6
The way this works is as follows:
1. Mail.app encodes attachments as "Appledouble". This means it sends both the data fork and the resource fork in the email. They both have the same name, of course. For a Mac user, this is no problem.
2. For a Windows user receiving such an email, he will see 2 attachments. If they simply save the attachments, the 2nd file will overwrite the first in the destination folder (since they have the same name) and he will be left with what appears to be junk. (It's probably just the resource fork that will be seen, which is the small file). If the Windows user simply opens the attachment directly from the email they may be lucky to see the right file and be able to view the attachment, depending on which of the files they happen to select. Either way, it is not satisfactory for a PC user to have to know where the attachment came from before they can decide how to open it.
3. If you send attachments via the Mac Outlook Express application, it has options to send emails as "Base64/Mime", "Include Windows file extensions", "no compression". With those options set, any PC user can open an attachment from a Mac without any special thought (just as if it came from another PC user). Other Mac emailers such as Eudora and Entourage can also send email attachments this way.
Since Mail does not offer these sort of options, we are forced to have to use OE (Classic) or some other emailer to be able to ensure PC users can reliably view any attachments we send.
This is a big disadvantage to the Mail.app and makes it unusable in many cases. Whether we like it or not, there are, in fact, more PC users than Mac users out there, and we do have to be able to email them. (Well I do, anyway).
