Hi, everyone.

I'm JS.

I have a big trouble about utf8 setting.

We have installed Exchange Server 2013 sp1 with dag.
And we have to apply OutboundCharset for AlwaysUTF8.

I tried to apply using cmdlet as below.

Set-OwaVirtualDirectory -identity "SERVER1\owa (Default Web Site)" -OutboundCharset AlwaysUTF8

Set-OwaVirtualDirectory -identity "SERVER2\owa (Default Web Site)" -OutboundCharset AlwaysUTF8

Set-OwaVirtualDirectory -identity "SERVER1\owa (Exchange Back End)" -OutboundCharset AlwaysUTF8

Set-OwaVirtualDirectory -identity "SERVER2\owa (Exchange Back End)" -OutboundCharset AlwaysUTF8

And

iisreset /noforce

Server reboot.

Re construct VirtualDirectory.

But... it is not working.

Server's response shows OutboundCharset : AlwaysUTF8
But actually all eml files are not UTF8.

Please help me... How can I do?

Hi,

According to your question and testing, please run below command to check the setting for OWA virtual directory:
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*OutboundCharset*

If there are some VD not setted as expected, run Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories  | Set-OwaVirtualDirectory -OutboundCharset "AlwaysUTF8"
Note: The AlwaysUTF8 character setting on the Outlook Web App virtual directory takes precedence over user-defined settings. Outlook Web App sets the UTF-8 character on all outgoing e-mail messages, regardless of the user's language choice in Outlook Web App.

Meanwhile, to make all Arabic, Asian, Hebrew, and Urdu text display correctly in Outlook Web App, support for languages that are read from right-to-left and script languages must be installed on the client computer. Other languages may also require that the appropriate language pack be installed on the client computer.

Thanks

Dear Mr. Wang,

Thank you for your reply.
I have checked on our server following your instruction.

But the server responded as below

[PS] C:\Windows\system32>Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | fl Identity, *OutboundCharset*


Identity        : CDEX02\owa (Exchange Back End)
OutboundCharset : AlwaysUTF8

Identity        : CDEX01\owa (Exchange Back End)
OutboundCharset : AlwaysUTF8

Identity        : CDEX02\owa (Default Web Site)
OutboundCharset : AlwaysUTF8

Identity        : CDEX01\owa (Default Web Site)
OutboundCharset : AlwaysUTF8

So I think this was applied already on the server.
But all sending emails are not changed to UTF8.

According to our test result, CU8, 9 can be applied that cmdlet properly. But I am wondering that why CU4, 5 are not supported same cmdlet and operation.

We have downgraded from CU8 to SP1 since CU8 does not support charset for iso-2022-jp emails sent from blackberry.

Awaiting for your next reply.

Hi,

It seems great on server configuration.

Do you apply mailbox policy in your environment? Please run Get-OwaMailboxPolicy | FL Identity,OutboundCharset

Dear Wang,

Thank you for your attention.

I have executed following your instruction again.
The servers responded as below.


[PS] C:\Windows\system32>Get-OwaMailboxPolicy | fl Identity, OutboundCharset


Identity        : Default
OutboundCharset : AutoDetect


It's a little bit wierd.
How can I proceed more?
Please let me know regarding this.

I look forward to your next instructions.

Hi,

Sorry for my fault.

We can run Get-CASMailbox | FL Identity,OwaMailboxPolicy to check whether apply relevant policy in your environment.
If so, you can run below to remove: Get-CASMailbox | Set-CASMailbox -OwaMailboxPolicy:$null

Good day.

I have run following your command.
The result was as below.


Identity         : cidoshipping.com/CIDOSHIPPING/CIDOBSN/Users/aaa
OwaMailboxPolicy :

Identity         : cidoshipping.com/CIDOSHIPPING/CIDOBSN/Users/bbb
OwaMailboxPolicy :

Identity         : cidoshipping.com/CIDOSHIPPING/CIDOBSN/Users/ccc
OwaMailboxPolicy :

Identity         : cidoshipping.com/CIDOSHIPPING/CIDOBSN/Users/ddd
OwaMailboxPolicy :

Identity         : cidoshipping.com/CIDOSHIPPING/CIDOBSN/Users/eee
OwaMailboxPolicy :
.
.
.


I think the OwaMailboxPolicy of all accounts were blank.
So I did not execute OwaMailboxPolicy to $null.

We need to send in UTF8 charset.
Please let me know the next attempt.


Awaiting for your reply.

Hi,

For your question, please double ensure the setting for OutboundCharset:
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*OutboundCharset*
Get-CASMailbox | Where {$_.OwaMailboxPolicy -eq $null} | FL Identity,OwaMialboxPolicy

If the issue persists, please post the message header for further troubleshooting.
Note: this parameter only apply for outbound message, therefor we need collect header in external recipient's inbox.

Here's an similar thread about your question, for your reference:
https://social.technet.microsoft.com/Forums/appvirtualization/en-US/1397c6c9-4523-41cd-805f-7e3408bcbac5/change-encoding-in-owa-from-qp-to-utf8?forum=exchangesvradmin

Hi,

Thank you for your help.

But first two cmdlet was already confirmed as before.
And link you mentioned was already attempted but not applied.

Here's external recipient's header.



Subject: test 20150723
Thread-Topic: test 20150723
Thread-Index: AQHQxNrTxiqQg4huuUatrWnBSM8yog==
Date: Thu, 23 Jul 2015 00:02:11 +0000
Message-ID: <29c16ae238d04563b553acda1921901a@CDEX01.cidoshipping.com>
Accept-Language: en-US, ko-KR
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [211.197.128.253]
Content-Type: multipart/alternative;
boundary="_000_29c16ae238d04563b553acda1921901aCDEX01cidoshippingcom_"
MIME-Version: 1.0
X-Naver-ESV: +9FYpB3G1H+YbXFCbHmRKAgmKoEZjJ+Y

--_000_29c16ae238d04563b553acda1921901aCDEX01cidoshippingcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable