Email notifications have empty CC: field even if there are no CC: recipients
See original GitHub issue📣 Notification Service(s) Impacted EMail
🐞 Describe the bug The email has a CC: field even if there are no CC recipients.
💡 Screenshots and Logs
Cc:
💻 Your System Details: NetBSD, python 3.10
🔮 Additional context In NotifyEmail.py, I see
base['Cc'] = ','.join(cc)
and that should only be added if cc is non-empty.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Email not getting sent if the 'to' address is miss... - ServiceNow
I used a notification email script and I am cc'ing the members i.e. when the email is sent the members appear under Copied...
Read more >How did I get this email without a "To" field?
The usual way for a mail client to work is that the user types recepient addresses into three fields within the mail client...
Read more >Automatically Cc (carbon copy) someone on every email you ...
In Microsoft Outlook, you can specify that for all messages that you send, an automatic carbon copy (Cc) is sent to other people...
Read more >How to identify recipient address when To and CC are blank?
1 Answer 1 ... The only possible way is to look at message's internet headers. Some email servers save original recipient in one...
Read more >email sending error with cc and bcc - CodeProject
Expanding on Amits solution: C#. foreach (string emailCC in txtCc.Text.ToString().Split(splitter)) { if(!string.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I tested with 1.1.0 and there is no spurious CC: header. Sorry for the noise.
And about xmpp, my point was really just that while it is missing in releases (including the one installed by HA’s integration), it was in the wiki, so I was baffled by the parse error.