Netlify email integration silently fails with bcc

Does the netlify email integration using the @netlify/emails nodejs module is working fine for me. Recently, I added a “bcc” field when sending an email (earlier I was using only “to”) - since then no emails are being sent out. Mailgun logs show no request was received. Netlify function raises no exception either.

Is “bcc” a supported field with the netlify email integration when using the nodejs module?

Testing with netlify dev works fine. But not in production.

@netlify/emails currently only guarantees support for to, from, replyTo, subject, and html/textcc and bcc may behave differently or fail silently in production.

  • If BCC is required, you could bypass @netlify/emails and send directly via Mailgun (or another SMTP) using a Netlify Function
1 Like

Thank you @Kevin_Clark_Cuesta. Will using the ‘fetch’ snippet as described in Netlify Email Integration | Netlify Docs allow to use cc/bcc?

Also, may I request this list of supported/unsupported fields for @netlify/emails be documented somewhere.

Is there a chance that @netlify/emails will be improved at some point to include cc/bcc or is that node module no longer being actively worked on?

Does anyone know if the fetch snippet based code of the Netlify Email integration supports cc and bcc?

cc and bcc are definitely supported fields, at least based on the code. we simply use Mailgun’s client:

Anyways, this emails plugin is not receiving much attention at the moment. I’d recommend setting up Mailgun or any SMTP provider of your choice directly so you have more control over it.

Strange. It didn’t work for me. As soon as I removed “bcc”, it started working.

Switching to direct mailgun/SMTP provider is not simple as I’m using the MJML templates.