Hello
Thanks for your post.
According to your post, I understand that client cannot access to accented charters-namedfolder by IMAP after upgrade to Exchange 2013 CU6.
That's correct
How about access to other name-type folder? Is it only occur on French locale?
Not quite sure how I would go to test it - as far I can see, regardless of the IMAP client used, other folders are accessible. To be really sure I guess I should telnet into the Exchange server on the IMAP port and run a few commands ?
Please try to run below command to double check the state of Exchange system component:
Get-ServerComponentstate -Identity servername
Here we go:
[PS] C:\Users\admin\Desktop>Get-ServerComponentstate -Identity "exch-au-01.domain.local"
Server Component
State
------ ---------
-----
exch-au-01.domain.local ServerWideOffline
Active
exch-au-01.domain.local HubTransport
Active
exch-au-01.domain.local FrontendTransport
Active
exch-au-01.domain.local Monitoring
Active
exch-au-01.domain.local RecoveryActionsEnabled Active
exch-au-01.domain.local AutoDiscoverProxy
Active
exch-au-01.domain.local ActiveSyncProxy
Active
exch-au-01.domain.local EcpProxy
Active
exch-au-01.domain.local EwsProxy
Active
exch-au-01.domain.local ImapProxy
Active
exch-au-01.domain.local OabProxy
Active
exch-au-01.domain.local OwaProxy
Active
exch-au-01.domain.local PopProxy
Active
exch-au-01.domain.local PushNotificationsProxy Active
exch-au-01.domain.local RpsProxy
Active
exch-au-01.domain.local RwsProxy
Active
exch-au-01.domain.local RpcProxy
Active
exch-au-01.domain.local UMCallRouter
Active
exch-au-01.domain.local XropProxy
Active
exch-au-01.domain.local HttpProxyAvailabilityGroup Active
exch-au-01.domain.local ForwardSyncDaemon
Inactive
exch-au-01.domain.local ProvisioningRps
Inactive
exch-au-01.domain.local MapiProxy
Active
exch-au-01.domain.local EdgeTransport
Active
exch-au-01.domain.local HighAvailability
Active
exch-au-01.domain.local SharedCache
Active
Seems fairly normal to me ?