Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Delivery has failed: 550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (UNKNOWN) is invalid or not installed

Answered Delivery has failed: 550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (UNKNOWN) is invalid or not installed

  • Saturday, May 05, 2012 6:07 PM
     
     
    Sign In to Vote
    0

    I've seen this error on other threads, but no solution. SP1 rollup 4 looks to at least send an NDR back when Exchange encounters a particular string of characters in the subject line of an email.  I've tested this with SP2 rollup 1 and 2.  It appears to not be fixed.  Messages of this nature are delivrered to non MS mail systems.

    the character sample in the subject line I'm seeing  is this which causes the deliver failure.

    =?UNKNOWN?B?l=g==?=

    While Exchange does send an NDR back, if the sender is sending from a no reply address, they'll hang in my queues.  I guess the question is...they look to be valid email, why doesn't Exchange deliver them?

    thanks

     

All Replies

  • Saturday, May 05, 2012 6:26 PM
    Moderator
     
     
    Sign In to Vote
    0

    well, its better than what it was doing - crashing the transport service!

    By a no reply address do you mean its FROM <>  ?

    From the Exchange point of view, they are using an invalid charset and should be turfed. You would have to open a case with Microsoft support I suppose to get a more detailed explanation on the specifics of a particular message.

     
  • Saturday, May 05, 2012 10:06 PM
     
     
    Sign In to Vote
    0

    the messages appear to be from valid companies that send out mass email, but the return address doesn't exist, so NDR has no where to go except sit in our queues.

     
  • Sunday, May 06, 2012 12:53 AM
    Moderator
     
     
    Sign In to Vote
    0

    Do you send directly to the Internet from Exchange?

     
  • Monday, May 07, 2012 5:37 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hello,

    The bug should be addressed in SP1 RU4. Please submit a new case to Microsoft to double confirm this issue:

    https://support.microsoft.com/oas/default.aspx?ln=en-us&x=11&y=10&c1=508&gprid=13965&&st=1&wfxredirect=1&sd=gn

    Thanks,

    Simon

                            

     
  • Tuesday, May 08, 2012 11:23 AM
     
      Has Code
    Sign In to Vote
    0

    Same problem here. It happens when using a ISO-8859-10 character encoding and then using one of the 127+ characters in the subject.

    The lower 127 characters do not impeed sending the mail. and the message body encoding do not hinder the mail from being received.

    smtp;550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (ISO-8859-10) is invalid or not installed.; cannot handle content of message with InternalId

    tested with

    Exchange 2010 with sp1 ru 5 ;

    Exchange 2010 SP2

    Zarjazz

     
  • Tuesday, May 08, 2012 11:36 AM
    Moderator
     
      Has Code
    Sign In to Vote
    0

    Same problem here. It happens when using a ISO-8859-10 character encoding and then using one of the 127+ characters in the subject.

    The lower 127 characters do not impeed sending the mail. and the message body encoding do not hinder the mail from being received.

    smtp;550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (ISO-8859-10) is invalid or not installed.; cannot handle content of message with InternalId

    tested with

    Exchange 2010 with sp1 ru 5 ;

    Exchange 2010 SP2

    Zarjazz

    In SP2 RU1, this could potentially crash the transport service. Fixed in SP2 RU2.