Bounced email checker

Tomasz Kosinski asked on March 8, 2018 16:55

Bounced email checker has a problem with some emails:

Message: 'ansi_x3.110-1983' is not a supported encoding name. For information on defining a custom 
encoding, see the documentation for the Encoding.RegisterProvider method.
Parameter name: name

Exception type: System.ArgumentException
Stack trace: 
at System.Globalization.EncodingTable.internalGetCodePageFromName(String name)
at System.Globalization.EncodingTable.GetCodePageFromName(String name)
at System.Text.Encoding.GetEncoding(String name)
at OpenPop.Mime.Decode.EncodingFinder.FindEncoding(String characterSet)
at OpenPop.Mime.MessagePart.ParseBodyEncoding(String characterSet)
at OpenPop.Mime.MessagePart..ctor(Byte[] rawBody, MessageHeader headers)
at OpenPop.Mime.Message..ctor(Byte[] rawMessageContent, Boolean parseBody)
at OpenPop.Pop3.Pop3Client.GetMessage(Int32 messageNumber)
at CMS.Newsletters.Extensions.Pop3ClientExtensions.GetSafeMessage(Pop3Client pop3Client, Int32 
messageNumber)

Any Idea how to resolve it?

email marketing

Recent Answers

Peter Mogilnitski answered on March 8, 2018 22:45 (last edited on March 8, 2018 22:51)

It is probably a problem with bounced email encoding. There is Check bounced emails scheduled task, which runs once per hour by default. The class responsible for it is CMS.Newsletters.BounceChecker, in there we have an a event OnFallbackDecoderEvent - which occurs when a character set from email content type header could not be mapped to the encoding. This allows to map given character set name to the encoding manually. I would raise this issue with support and ask them if it is possible to attach your custom handler to this event.

0 votesVote for this answer Mark as a Correct answer

Tomasz Kosinski answered on November 13, 2018 15:15

Any news on this. We have a lot of such error messages in an event log.

0 votesVote for this answer Mark as a Correct answer