LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi,

I am using the experimental email node in 4.1.8 but get Chinese Characters when I receive the email:

Example:

�䠀椀Ⰰ਀਀夀漀甀 栀愀瘀攀 爀攀挀攀椀瘀攀搀 琀栀椀猀 洀攀猀猀愀最攀 愀甀琀漀洀愀琀椀挀愀氀氀礀  瘀椀愀 䰀䄀䔀 愀猀 愀渀 椀渀搀椀挀愀琀椀漀渀 琀栀愀琀 琀栀攀 氀愀猀琀 ㄀㔀 洀椀渀甀琀攀猀  瘀椀攀眀 漀昀 琀栀攀 瀀甀爀挀栀愀猀攀 瀀愀琀栀 昀漀爀 倀愀礀洀攀渀琀猀⼀刀攀最椀猀琀爀愀琀椀 漀渀 愀渀搀 倀甀爀挀栀愀猀攀猀 愀爀攀 ㄀　─ 氀漀眀攀爀 琀栀愀渀 琀栀攀 猀愀洀攀 琀椀洀攀猀 氀漀琀 氀愀猀琀 眀攀攀欀㨀਀਀吀椀洀攀 䘀爀漀洀㨀 䠀漀甀爀

Has anyone experienced this before?

Regards
Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: ejones

I've seen this type of thing before when some system is confused about the character encoding scheme used in a file. I haven't seen this in the E-mail node yet but it is conceivable that this is what happened. If this theory is right then there may be some some non-ASCII character (outside of the range of 0 to 127) in the message that is throwing things off. Or it could be an ASCII control character in the message that is not normally seen in ASCII text, or possibly a null character.

Ernest

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rpigneri

Dear Wayne,

This situation can also occur when the e-mail text follows a few specific patterns. In that case, adding a few extra blank lines to the end of the e-mail or reformatting the beginning of the message can avoid this problem.

Feel free to write back if it does not.

Rocco

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: dwong80

We are experiencing this exact same problem using BRE/LAE 4.5.4. We have changed up the message body several times, but it doesn't resolve the issue. What other solutions are available?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi,

I was able to resolve the issue with re-formatting of the text. It appeared to get a little upset with special characters like additional line feeds, commas etc. Once i removed them it worked fine

Regards
Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: nnaemeo

Hi Xathras,

Please can you throw more light on the text reformatting?

thanks.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: ejones

What I found is that the problem was not the email message itself, but the way Microsoft Outlook is interpreting the characters. Outlook has to figure out for itself how they are encoded and depending on the characters in the message it can make an invalid choice.

I believe that the longer the message is, the better chance Outlook will have identifying the encoding correctly. Xathras pointed out his experience was that characters like line feeds and even commas seemed to make Outlook less likely to interpret the email encoding correctly. So using that information I'd also remove all carriage return characters and any punctuation that could be reasonably avoided.

Another option which is what I ended up doing, was change the node itself. I changed the way the characters are encoded in my own copy of the core experimental node named Send E-mail. If you have the access to the Python code in the node. (There is no guarantee that you have this access)
- Make yourself a copy of this node so that you don't mess up the original.
- In the copy, go into the Python code and change the line that says this, I believe it is line 190
msg = MIMEText(unicode(messageBody, self.characterSet).encode('UTF-16'), 'plain', 'UTF-16')
To this:
msg = MIMEText(unicode(messageBody, self.characterSet).encode('UTF-8'), 'plain', 'UTF-8')
- Save this and try that node.
If it works, Outlook might have an easier time interpreting the email.