How to send SMTP to multiple email address now?

Configuration
1

Previously before the change to SMTP, I can specify multiple receiver in the action like

notify_monthly_electricity_cost:
  mode: single
  alias: Notify monthly electricity cost
  sequence:
    - action: notify.aws_ses
      data:
        message: "Not used"
        title: "Title"
        target:
          - [email protected]
          - [email protected]
        data:
          html: Content

However, with the new SMTP integration and the following YAML, I’m no longer able to use target under data section

notify_monthly_electricity_cost:
  mode: single
  alias: Notify monthly electricity cost
  sequence:
    - action: smtp.send_message
      target:
        entity_id: notify.aws_ses_xxx_gmail_com
      data:
        message: "Not used"
        title: Title
        target:
          - [email protected]
          - [email protected]
        html: Content

Failed to perform the action script/notify_monthly_electricity_cost. extra keys not allowed @ data['target']
2

I realized there’s a new option for the SMTP integration that adds new recipient. However, when sending emails using multiple notify target, each recipient cannot see other recipients, as if they are the only recipient for that email. I.e., not multiple receivers

        entity_id:
          - notify.aws_ses_aaa_gmail_com
          - notify.aws_ses_bbb

image
image2314×674 24.4 KB

3

Agreed, this is a real regression. I hit the exact same thing today - targeting multiple notify entities on smtp.send_message doesn’t produce one email with multiple To: recipients, it fires a separate individual send per entity. Each recipient sees themselves as the only one on the email, which breaks reply-all and hides who else got it.

The old notify: platform: smtp YAML config accepted an arbitrary target: list of raw addresses and built a single message with all of them in To:. That capability has no equivalent in the new UI-based integration — there’s also no cc/bcc field on smtp.send_message to work around it. This isn’t just a rough edge, it’s a genuine loss of functionality from the old platform. Would be great to see this tracked as an actual issue rather than just discussed here.

5

There are already a couple of related issues/FRs…

… But neither is specifically about cc, bcc, or all recipients being visible to one another. If you want this “tracked” as it’s own issue, you need to create an issue on Github… that’s where issues get tracked.

6

Oh, wow. This is a real step down. I see over on GitHub a couple of links to third-party solutions which other users have gone to, instead of the native SMTP process. When an “update” causes users to abandon the functionality which changed, that says a lot.

Any chance this removed functionality is an oversight or an unintended bug, and someone is already working on a fix?