Idea Summary
Validate the html so that it doesn't result in getting emails that dump html and convert it to text.

claude is saying that the hand off to oci email srv lacks Content-Transfer-Encoding

Use Case

uploaded html generated by claude which renders fine in gmail. Tried to upload via upload file

that doesn't work. So used data loader to upload each line of the html into a table and then

wrote loop to concate each line of html into html_clob checking to not have any chunk > 998 inclusng CRLF. Results in emails not rending the html. Seems that the html has to be 64 bit encoded ?

Preferred Solution (Optional)
apex is load code. So either validate the html and/or offer an easy html repair method.

would be: "APEX_MAIL.SEND should add _Content-Transfer-Encoding: base64_ and encode _p_body_html_ content when _p_template_static_id_ is not used."