When an email has empty charset value in the header for Content Type an exception will occur but not be shown in logs
Last updated 2020-12-02 ·Reference W-6113114 ·Reported By 11 users
If you are using something like Email-To-Case or Email-To-Lead and your own Apex Email Handler, if you get emails with multi-part attachments you may see that these emails can fail the first time.
There will not be an exception in the debug logs.
But internally Support will be able to see:
ParseException: In parameter list <; charset=>, expected parameter value, got "null"
This is because the email being sent to Salesforce does not have a charset value in the header for Content Type
Send multiple emails to create leads, some with attachments and some without but which also do not have a defined charset value in the header
some of these emails will fail but no exception will be seen in the debug logs. But when you compare them to the success logs, you'll see that the email handler did not fully run
Ensure that emails have a charset value defined in the Content Type Header
Since these emails are often coming from externally this is difficult to achieve
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.