# Email node shows "invalid properties: token", but works

**URL:** <https://discourse.nodered.org/t/email-node-shows-invalid-properties-token-but-works/84401>\
**Category:** General\
**Tags:** possible-bug\
**Created:** [8 January 2024 22:19 UTC](https://discourse.nodered.org/t/email-node-shows-invalid-properties-token-but-works/84401 "2024-01-08T22:19:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dennishvo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dennishvo/32/2896_2.png) [@dennishvo](https://discourse.nodered.org/u/dennishvo)\
**Post date:** [8 January 2024 22:19 UTC](https://discourse.nodered.org/t/email-node-shows-invalid-properties-token-but-works/84401/1 "2024-01-08T22:19:05Z")

</div>

I'm upgrading from NR 3.0.2 to NR 3.1.3 and everything has been working well except for one odd issue with the email node (node-red-node-email v2.1.0).

Here's how I have the email node configured:

- Name -- empty
- To -- empty (set by msg.to
- Server -- a gmail server
- Port -- 465
- Use secure connections -- checked
- Auth Type is a new field, which I set to Basic.
- User id -- yes
- Password -- yes
- TLS option -- not checked

When I configure the node this way, a red triangle appears on the node with the message "invalid properties: token". When I try to deploy, I get the prompt:

"The workspace contains some nodes that are not properly configured: [User Edit Page] email (e-mail) Are you sure you want to deploy?"

I force it and the node works fine. Interestingly, when I refresh all flows, the red triangle goes away. So not a serious bug, but certainly misleading.

---

<div class="post-metadata">

**Author:** ![mickym2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mickym2/32/36128_2.png) [@mickym2](https://discourse.nodered.org/u/mickym2)\
**Post date:** [9 January 2024 04:41 UTC](https://discourse.nodered.org/t/email-node-shows-invalid-properties-token-but-works/84401/2 "2024-01-09T04:41:07Z")

</div>

I have the same problem - it seems to be again a bug after NodeRed Version 3.1.1. It seems that the general check of the editor to detect misconfigured nodes - was not tested with all nodes.

I hope this will not happen for other nodes again and again.

I opened an issue: [Another editor bug when checking misconfigured nodes · Issue #1043 · node-red/node-red-nodes · GitHub](https://github.com/node-red/node-red-nodes/issues/1043)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [9 March 2024 04:41 UTC](https://discourse.nodered.org/t/email-node-shows-invalid-properties-token-but-works/84401/3 "2024-03-09T04:41:31Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.