Further improve how we handle unsupported encodings when parsing InboundEmail webhooks

[Jericho]

There has been several issues raised over the years regarding sections of the InboundEmail payload being encoded with unknown/unsupported encodings and two improvements have been made to lessen the problem:

• Support additional Encodings #252. Following this improvement, StrongGrid supports 116 encodings.
• Fallback to UTF-8 when an invalid/unsupported encoding is specified

These two improvements have considerably reduced the problem with encoding but I was thinking we could be smarter than blindly fallback to UTF-8 when an invalid/unsupported encoding is specified. I recently found out about the UTF Unknown project which attempts to determine which encoding was used to encode binary data by probing the content. This would enhance our ability to properly decode a given section of a webhook, even if the encoding is unspecified or invalid.

[Jericho]

🎉 This issue has been resolved in version 0.108.0 🎉

The release is available on:

• GitHub Release
• NuGet Package

Your GitReleaseManager bot 📦🚀