[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Exchange 2010 rejects messages witch UNKNOWN charset

Posted on 2011-03-25
4
Medium Priority
?
4,739 Views
Last Modified: 2012-05-11
My transport server fails to deliver messages which have wrong charset in message subject or attachment description. Example:

Content-description: =?UNKNOWN?Q?=22statystyki_wg?= metod

RecipientStatus from Message Tracking:
550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (UNKNOWN) is invalid or not installed.; cannot handle content of message with InternalId xxx

I understand why would someone want to reject these messages on antispam or antivirus server - but  forcing rejection on hub transport is wrong. This is messaging server - I don't want it to reject any messages. I have edge antispam for that!

Does anyone has an idea how to turn it off? Or at least replace UNKNOWN to proper charset string in header?
0
Comment
Question by:mpilarczyk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 26

Expert Comment

by:e_aravind
ID: 35308914
Can you check after upgrading the servers to Exchange server 2010 sp1 rollup 2.
0
 
LVL 3

Author Comment

by:mpilarczyk
ID: 35313752
I didn't install Rollup 2. None of the issues it repairs happens to my system.
0
 
LVL 3

Accepted Solution

by:
mpilarczyk earned 0 total points
ID: 36137983
FYI:

http://exchangeserverpro.com/microsoft-releases-update-rollup-4-exchange-2010-sp1

Update Rollup 4 contains patch 2394554:
You have a Microsoft Exchange Server 2010 mailbox.
You send an email message to a recipient by using this mailbox.
The subject line of the email message contains unsupported encoded characters, such as ISO-2022-JP-2 encoded characters.

In this scenario, the email message is not delivered to the recipient. Additionally, you do not receive a non-delivery report (NDR) message.

This issue occurs because Exchange Server 2010 does not process an email message if the subject line contains unsupported encoded characters. Additionally, an exception occurs when Exchange Server 2010 tries to generate a NDR message.
0
 
LVL 3

Author Closing Comment

by:mpilarczyk
ID: 36164589
UR4 solves this
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question