The error that you’re getting looks like a tnef one. I presume that you
have the same problem with all emails from Foxmail? Try sending an email
from something like Thunderbird:
http://www.mozilla.org/en-US/thunderbird/
and see if you get the same problem. Foxmail:
http://en.wikipedia.org/wiki/Foxmail
is also a bit naughty in that it violates various RFCs, so may also be
an issue. (Outlook at least is rfc 822 compliant)
Be aware that the setup process tests for the existence of the binary,
and doesn’t actually run it. Particularly if you are on a shared server,
the permissions/restrictions are different (include path/open base dir
and no doubt others). I presume that there are no errors associated with
this in your log files?
If you are getting no errors in your log files, then I suspect this is a
failure of the felamimail to cope with the attachment, and therefore is
presenting it as raw base64.
Worst case scenario is that you get the base-64 gunge and have to
manually transalate them:
http://www.motobit.com/util/base64-decoder-encoder.asp
giving:
-------8X------------
ä½ å¥½
-------8X------------
I notice some funny characters in there - odd? I see that you’ve tried
foxmail sending ‘plain text’ rather than html, but can you try
selecting a more ‘common’ character set?
other base64 code gives:
-------8X------------
panther£¬ÃúºÃ£¡
heo
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÃÃ
Ãñ£¡
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡zhenglq
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡zhenglq@189.cn
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2012-03-14
-------8X------------
…the ! marks are because I can’t match up the character set correctly,
which leads me to think that there may be a character set issue here.
Interestingly also from the Microsoft Website:
http://msdn.microsoft.com/en-us/library/cc815781(v=office.12).aspx
-8X--------------
If 25% or more of the characters have the high bit set, the
attachment is binary. It is encoded using the Base64 algorithm.
/Content-type: application/octet-stream/ (by default; based on file
extension)
/Content-Transfer-Encoding: base64/
-8X------------------
Being that Foxmail does abuse the standards and possibly also because I
suspect you are using a multi-byte char set, everything it sends is
probably going to be base64 encoded. You’d need to look at the data
stream to the server from the Foxmail client to be 100% sure.
If you haven’t got any errors in the log file, then I suspect you need
to look at what char sets are available to the felamimail webclient.
These will be those that are installed in the system and are available
to the webserver concerned. Adding the charsets that you are missing has
a fairly good chance of resolving the issue.
HTH
Peter