# Unable to send PDF report with Recipient Method set to BCC

**URL:** <https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275>\
**Category:** Ignition\
**Created:** [March 2, 2026, 9:54pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275 "2026-03-02T21:54:46Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [March 2, 2026, 9:54pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/1 "2026-03-02T21:54:46Z")

</div>

I have an email profile setup setup in the gateway. I have a project with a report in it that gets run once per month. The actions are to send an email to the email profile in the gateway at this time. The recipient is able to receive an email when the drop down method is set to **To** but not **BCC**. The options are [To, CC, BCC, ReplyTo].

Is this a known issue with Ignition or is this a problem on the SMTP server side? No errors went out when it ran this month. The email just never showed up when set to **BCC**.

This image shows the location in the report that I am looking at.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/d/9da51632f885112a164d256c8aef9ebc57ab757d.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 2, 2026, 10:02pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/2 "2026-03-02T22:02:42Z")

</div>

You can’t technically send an email via SMTP with _just_ CC or BCC recipients. You must fill in the To recipient. Typically a CC/BCC blast will use a dummy To recipient, but Ignition isn’t doing this for you.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [March 2, 2026, 10:18pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/3 "2026-03-02T22:18:21Z")

</div>

> [@Kevin.Herron](#):
>
> You can’t technically send an email via SMTP with _just_ CC or BCC recipients

Do you mean I can't technically do this in Ignition? Because I can do it just fine with my work email.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 2, 2026, 10:24pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/4 "2026-03-02T22:24:42Z")

</div>

I think you just have to provide the dummy "To" address yourself, which is likely what your mail provider does in the background.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 2, 2026, 10:30pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/5 "2026-03-02T22:30:21Z")

</div>

The SMTP profiles in Ignition should also have a debug logging setting you can turn on to see the conversation with the mail server (in wrapper.log), which might also be useful in case I've misunderstood the RFC and the the RCPT command.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [March 2, 2026, 10:40pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/6 "2026-03-02T22:40:09Z")

</div>

I turned on debug for SMTP. Ignition designer threw the following error when using the Run Action Immediately button in the Schedule tab.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/9/591dabc6e8eeb9a4d99bc4f934e139d12e887f3f.png)

and the logs threw two warnings. The first is:

```python
**No 'to' addresses found for Email Action**
```

The second is:

```python
**java.lang.IllegalArgumentException: Incomplete email parameters. You must specify the following: email recipient list**
```

What I then tried is putting a generic, fake email, [Ignition@mail.net](mailto:Ignition@mail.net) in the From Address and in the To field, and then putting the emails I needed in the BCC and it accepted that.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 2, 2026, 11:19pm UTC](https://forum.inductiveautomation.com/t/unable-to-send-pdf-report-with-recipient-method-set-to-bcc/114275/7 "2026-03-02T23:19:36Z")

</div>

I recommend that you set the from address to something like `scriptname.projectname@servername.companyname.com` and construct this programmatically so that it auto-updates if the project is copied or moved to another server. It will be a big help in debugging quickly if the script goes rogue and your company's email gets blacklisted!
