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
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
ASKER
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_136764196 1.14206844 92489"
X-Mailer: sendHTMLMail
Content-Length: 9357
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_136764196
first
----=_Part_11760_136764196
second
----=_Part_11760_136764196
third
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_136764196
first
----=_Part_11760_136764196
second
----=_Part_11760_136764196
third
ASKER
What shall i check further?
Look at the content-type charset in the email on each side.
Check the setting when the email come out raw?
Check the setting when the email come out raw?
ASKER
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)
LCDCosONwqLDjcK6wqTDmMKzwrfDlcOowqHD g8OYwrPDks Ojw4vDqcKk w4fD
ksOBw4rCucOjwqjDo8K5w6LCu8ODw6HCocOD w4EgQ29ycG 9yYXRlIFRy YXZl
bCBTb2x1dGlvbnMgwqLDjcKnIENhdGhheSBQ YWNpZmljIS DDoMODw5LD pMK0
w6nDg8ORwrrDocK6wrrCv8ONw4PDrMOBwqHD ksODw4XCp8 K3w5DDoMK6 w5XD
gsK5wqLDjcKnwrrDg8OUw4nDkcK3wqLDjcKn wrfDqMOSwr nDoQEwAQEB AQN0
ZXh0L2h0bWwDAzEw
X-YMailISG: _aTXhXIWLDu_SREcP6gjnIA1s6r2P25cCIe2 cYO2LDkoXk wu
sNVpTN2_0.egodABSp5SAyFUHLxTLu6vaScq 7d4z27FF6S i8l8zdFaYj _ovp
dQ0hWpgcPJ3SGD.hfEvmyQq3fUqBDTL78XFy CAvr7x2HRJ H5ZFo9NOwh 30Pq
LgrL_5JYopR7M4Nx3uZVGzjNKEaKDCYtJJFz fgBOGO0Z4j Ux_L4jUenK hnCQ
BluN.glM78s524zsrEdnoUdVJ4jb9Lgnx2Y7 Hnt2BVhg1T onq0dP9V.l D_VJ
7ZnlPKk2dYs0jPtbd4cCnpI11BlRsE3mmoyl 3Ohoq_MdT6 xJtr69jbnu F8Y4
0WsKj2YArA8UmkzaOWld1_snzfCNMNv2tfC_ 1kB8kKTkF2 L9MimjFG5V Wvuj
e6FkiOf6DXkwUU17yJbkdQJNMsC2cwhguUcx PQG4WHctNc SK0AaLvTex DUaE
9Urgl7dEC57lULch.CHVFZVSoTBmJ1Ub4cMN MH2sqBXLeQ Fp4KW4qbAr iT6k
_wYxv7M1.2LMm3C7i_6Ro2uEbVMDQbpuQYfC bw9sFE8ujH iBaf.77xoI 8e2R
EGVE4ac82PAbeYBBNDKAAbD7QAmV7.v21SY7 .hH.K7a8Es mxldntLwRF s3Vy
6r2crESs1QhDBYS.BLHQoO.QQTj02lJaOHhA 0TvdnoecM9 K4jwcF9WVk VXvN
F4gfzOsUshy_7cz1egqWtYFYWEd0oXABUKW5 1YVkDPXRVK .pKIvKzs6x x1SN
K707Iq49mH2WZK5.4HAr3Is1UyUX.5ylmwRK _.yzL_QuAT jByi0DUpgT eVKu
9Lcpw8OvV_pZ380ivOsXHWkTsaItXTK805mm x9MjOazVpN 0igADt8tkF _aoy
OpZ616hiKx0Gu9W93ckJKKP6PpZJjTxVO.um XpSSg7Goka G8IDDxE3up QXM9
ot5WAh9qJrqtsW4SHaDIP08bLaeZXs_waIO6 cqAqCuMzwO cTUutKhPcm aU7m
_HwGMvNRz7_nmVEX2rQh1NwdwLAWsvJFTieS ggTqSDDdze sl0mii_mw5 skh8
7mNjEHm2MqFtdrZJ0BRpZ7EK2NAvcVpgpRhD 1OF3MZzgut R2PwKYbX7. RbvS
AkGBw.l8Bsl7HFXoAmyDsz8iLDxQyrBNBbYi kKuDiMwPAN slWBtqrWPh FU9S
RiMo6qGsPFpiYWf_zTwVfwmPQ2eR5o2NODnF ysDHlpZOFH eSXch0t9JO Z.5E
N_aSTVclPhDJhzdvCnJSl5Dn6dRA9P8n8yJy crEVn_4td6 2_.Rnwu0bp oO2o
SL6ZFIMpcPDurWmELkUThxgqjAQg7XUrmWb3 7XO3CY3x1Q 0HPkGHqkWj nXtH
IoVg3ingh6x621nv2Xor8667y5bSM2tgGO0d LY14ca_tsU cmSv4liSy1 b.oj
NDc6TkbKq0l5zgoTGFrWznADhkit20eM6YM6 qnRBkamUpz yDvdiEiT6C dvBh
xI1i
X-Originating-IP: [100.112.76.211]
Authentication-Results: mta1499.mail.bf1.yahoo.comfrom=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.comwith 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.r oot@webapp aix20>
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. 1422260879 136"
X-Mailer: sendHTMLMail
Return-Path: sales_th@contoso.com
Content-Length: 9392
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.
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.
ASKER
Where do i check then..check at the application layer?
I don't get where to check above? at Exchange ? Application?
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?
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 .....
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 .....
ASKER
The entire message was unreadable.
The source email came from same application. If this application user Exchange on ETE/Postfix (unix box), the entire message is fine.
The source email came from same application. If this application user Exchange on ETE/Postfix (unix box), the entire message is fine.
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.
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.
ASKER
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?
Do you know how do i raise the issue with Yahoo?
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?
Try the following if you can , a message received on gmail, forward to yahoo.
Is the issue with one specific character/glyph/symbol?
ASKER
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
ASKER
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
Accepted answer: 0 points for suriyaehnop's comment #a40780495
for the following reason:
I solve the issue
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sine you gave some comment to mt question then i gave you a point
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.