Invalid characters in yahoo mail

We have application being deploy in development to test send an email in Thai character to customer in internet. This application use production Exchange 2007 SP3 to relay email out.

Recently, I have complain from the application owner saying that when they send a test email to yahoo account, it will show invalid Thai characters. To GMAIL, Hotmail is ok.

I had asked him to a postfix smtp (Unix box) and Exchange 2007 relay (testing environment) to relay email to yahoo, the character show just fine.

The mail flow for:

Exchange Testing env. = Application  > Hub > Edge > Internet

Postfix = Application > PostFix SMTP > Internet

Exchange production = Application > Hub >Edge > Symantec Cloud > Internet.

We suspected Symantec cloud issue, logged a case with them but they found no issue.

Kindly help
LVL 19
suriyaehnopAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
It is likely not an issue of relaying, but the format that is being used to send them, double check the encoding on the outgoing side. there are many possibilities.
i.e. are you using UTF-8 or are you using the specific thai encoding?
Does the Content-type: specify the encoding:?
Content-Type: text/plain; charset=UTF-8


You need to look at the raw message i.e. send one message to three/four addresses, then compare the raw message.

Some might be more tolerant than others.

Yahoo seems to convert to UTF-8 which could explain the issue.
suriyaehnopAuthor Commented:
Here is the content-type:

To: <suriyalekpetch@yahoo.com>
Subject: "Corporate Travel Solutions" Company Registration - Received
MIME-Version: 1.0
Content-Type: multipart/mixed;
      boundary="----=_Part_11760_1367641961.1420684492489"
X-Mailer: sendHTMLMail
Content-Length: 9357
arnoldCommented:
There is no Content-Type: characterset in the example you posted.
This is what defines the data within.

The contenet-Tyep: multipart/mixed identifies that there are sections i.e. atttachments (inline or attachments) with the boundary used to separate each one.

Each one will have its own Contenet-type: charset=

----=_Part_11760_1367641961.1420684492489
first

----=_Part_11760_1367641961.1420684492489
second

----=_Part_11760_1367641961.1420684492489
third
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

suriyaehnopAuthor Commented:
What shall i check further?
arnoldCommented:
Look at the content-type charset in the email on each side.
Check the setting when the email come out raw?
suriyaehnopAuthor Commented:
Here is a internet header at yahoo mail, sent via Exchange Testing Env which the Thai character appear fine.

From sales_th@contoso.com Mon Jan 26 08:27:59 2015
X-Apparently-To: suriyalekpetch@yahoo.com; Mon, 26 Jan 2015 08:28:06 +0000
Return-Path: <salessupport_th@contoso.com>
Received-SPF: pass (domain of contoso.com designates 118.143.76.201 as permitted sender)
LCDCosONwqLDjcK6wqTDmMKzwrfDlcOowqHDg8OYwrPDksOjw4vDqcKkw4fD
ksOBw4rCucOjwqjDo8K5w6LCu8ODw6HCocODw4EgQ29ycG9yYXRlIFRyYXZl
bCBTb2x1dGlvbnMgwqLDjcKnIENhdGhheSBQYWNpZmljISDDoMODw5LDpMK0
w6nDg8ORwrrDocK6wrrCv8ONw4PDrMOBwqHDksODw4XCp8K3w5DDoMK6w5XD
gsK5wqLDjcKnwrrDg8OUw4nDkcK3wqLDjcKnwrfDqMOSwrnDoQEwAQEBAQN0
ZXh0L2h0bWwDAzEw
X-YMailISG: _aTXhXIWLDu_SREcP6gjnIA1s6r2P25cCIe2cYO2LDkoXkwu
sNVpTN2_0.egodABSp5SAyFUHLxTLu6vaScq7d4z27FF6Si8l8zdFaYj_ovp
dQ0hWpgcPJ3SGD.hfEvmyQq3fUqBDTL78XFyCAvr7x2HRJH5ZFo9NOwh30Pq
LgrL_5JYopR7M4Nx3uZVGzjNKEaKDCYtJJFzfgBOGO0Z4jUx_L4jUenKhnCQ
BluN.glM78s524zsrEdnoUdVJ4jb9Lgnx2Y7Hnt2BVhg1Tonq0dP9V.lD_VJ
7ZnlPKk2dYs0jPtbd4cCnpI11BlRsE3mmoyl3Ohoq_MdT6xJtr69jbnuF8Y4
0WsKj2YArA8UmkzaOWld1_snzfCNMNv2tfC_1kB8kKTkF2L9MimjFG5VWvuj
e6FkiOf6DXkwUU17yJbkdQJNMsC2cwhguUcxPQG4WHctNcSK0AaLvTexDUaE
9Urgl7dEC57lULch.CHVFZVSoTBmJ1Ub4cMNMH2sqBXLeQFp4KW4qbAriT6k
_wYxv7M1.2LMm3C7i_6Ro2uEbVMDQbpuQYfCbw9sFE8ujHiBaf.77xoI8e2R
EGVE4ac82PAbeYBBNDKAAbD7QAmV7.v21SY7.hH.K7a8EsmxldntLwRFs3Vy
6r2crESs1QhDBYS.BLHQoO.QQTj02lJaOHhA0TvdnoecM9K4jwcF9WVkVXvN
F4gfzOsUshy_7cz1egqWtYFYWEd0oXABUKW51YVkDPXRVK.pKIvKzs6xx1SN
K707Iq49mH2WZK5.4HAr3Is1UyUX.5ylmwRK_.yzL_QuATjByi0DUpgTeVKu
9Lcpw8OvV_pZ380ivOsXHWkTsaItXTK805mmx9MjOazVpN0igADt8tkF_aoy
OpZ616hiKx0Gu9W93ckJKKP6PpZJjTxVO.umXpSSg7GokaG8IDDxE3upQXM9
ot5WAh9qJrqtsW4SHaDIP08bLaeZXs_waIO6cqAqCuMzwOcTUutKhPcmaU7m
_HwGMvNRz7_nmVEX2rQh1NwdwLAWsvJFTieSggTqSDDdzesl0mii_mw5skh8
7mNjEHm2MqFtdrZJ0BRpZ7EK2NAvcVpgpRhD1OF3MZzgutR2PwKYbX7.RbvS
AkGBw.l8Bsl7HFXoAmyDsz8iLDxQyrBNBbYikKuDiMwPANslWBtqrWPhFU9S
RiMo6qGsPFpiYWf_zTwVfwmPQ2eR5o2NODnFysDHlpZOFHeSXch0t9JOZ.5E
N_aSTVclPhDJhzdvCnJSl5Dn6dRA9P8n8yJycrEVn_4td62_.Rnwu0bpoO2o
SL6ZFIMpcPDurWmELkUThxgqjAQg7XUrmWb37XO3CY3x1Q0HPkGHqkWjnXtH
IoVg3ingh6x621nv2Xor8667y5bSM2tgGO0dLY14ca_tsUcmSv4liSy1b.oj
NDc6TkbKq0l5zgoTGFrWznADhkit20eM6YM6qnRBkamUpzyDvdiEiT6CdvBh
xI1i
X-Originating-IP: [100.112.76.211]
Authentication-Results: mta1499.mail.bf1.yahoo.com  from=contoso.com; domainkeys=neutral (no sig);  from=contoso.com; dkim=neutral (no sig)
Received: from 127.0.0.1  (EHLO mail.ete.contoso.com) (100.112.76.211)
  by mta1499.mail.bf1.yahoo.com with SMTPS; Mon, 26 Jan 2015 08:28:04 +0000
Received: from HT03.local.ete.contoso.com
(10.10.103.28) by EG01.local.ete.contoso.com
(10.10.103.200) with Microsoft SMTP Server (TLS) id 8.3.389.2; Mon, 26 Jan
2015 16:28:01 +0800
Received: from webx20 (10.10.10.35) by mail.ete.contoso.com
(10.10.103.28) with Microsoft SMTP Server id 8.3.389.2; Mon, 26 Jan 2015
16:28:00 +0800
Message-ID: <1524066931.1422260879251.JavaMail.root@webappaix20>
Date: Mon, 26 Jan 2015 16:27:59 +0800
From: <sales_th@contoso.com>
To: <suriyalekpetch@yahoo.com>
Subject: "Corporate Travel Solutions" Company Registration - Received
MIME-Version: 1.0
Content-Type: multipart/mixed;
                boundary="----=_Part_904_1055517299.1422260879136"
X-Mailer: sendHTMLMail
Return-Path: sales_th@contoso.com
Content-Length: 9392
arnoldCommented:
The point of interest is when each part is individually defined/set.

The header you posted is informative only when looking to determine the path the message took to get to the destination.

Nothing here points to the content other than the content-type that indicates the message has multiple parts.
suriyaehnopAuthor Commented:
Where do i check then..check at the application layer?

Look at the content-type charset in the email on each side.
Check the setting when the email come out raw?

I don't get where to check above? at Exchange ? Application?
arnoldCommented:
the application is the simplest to see whether the output it is transmitting.
Search for the boundary in the header you posted.  Copy the boundary marking and search for it further I. The message.  There you should see another content-type and charset for this section depending on what the content here is. Each again and you will see another ...

What encoding is it using quoted-printables, base64? Does it use UTf-8 for charsetphp/encoding?

When looking in yahoo what is the font that is used versus the font used in the others.?
Unfortunately, I do not know thai, so not sure.

Is there a single invalid character or the entire message is unreadable.  For one determining where it is coming from might be .....
suriyaehnopAuthor Commented:
The entire message was unreadable.
Message
The source email came from same application. If this application user Exchange on ETE/Postfix (unix box), the entire message is fine.
arnoldCommented:
The issue might be with the client, I am not able to tell from what you've posted what is going on.
The user may have their settings such that it is preset with a specific encoding and their settings are such that the application can not correct for the change.

Does it happen to every yahoo recipient?
You have to look at the message headers (raw message where you can see the content-type: of each part of the multi-part attachment).

Unfortunately, if the issue is on yahoo's side, unless the person is paying for their services, he can raise the issue with them and based on their ,.. prioritization it will be looked at.

Not sure whether you are also using HTML to layout the content and whether that is where the issue is.
suriyaehnopAuthor Commented:
Does it happen to every yahoo recipient? try with 2 yahoo account same issue. The issue not happening on GMAIL or hotmail.

Do you know how do i raise the issue with Yahoo?
arnoldCommented:
the recipients can, I do not believe unless they have a specific type of account that it is an issue on their side.

Try the following if you can , a message received on gmail, forward to yahoo.

Is the issue with one specific character/glyph/symbol?
suriyaehnopAuthor Commented:
Please closed this question, problem solved, the issue due to forefront security in ht sever, when i add the sender email address and ip address of the application to trusted sender
suriyaehnopAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for suriyaehnop's comment #a40780495

for the following reason:

I solve the issue
arnoldCommented:
Weren't comments/post I made help focus your search for the culprit?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
suriyaehnopAuthor Commented:
Sine you gave some comment to mt question then i gave you a point
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.