After Node Red restart all email-send nodes not connected

Hello,

does anyone have the same problem? How do you solve it?

The following:

We have configured some flows that work perfectly. Notifications via mail/mail2SMS also work.

However, if the computer is restarted and Node Red is restarted, all email-send nodes are disconnected. Message in Node Red:

[error] [email-send:9b9e827895d66596] Error: Invalid greeting...

too many connections from [ext.IP].

I asked the mail provider. They only allow 3 simultaneous connections to prevent misuse.

My complicated solution: I deactivate all email-send nodes and activate them again. Does anyone have a better solution? Thanks

Try sending all emails through one email node. Use Link nodes to send the messages to the email flow.

Sorry, I don't understand. At the moment I have about 10 flows with dozens of devices that send notifications to different recipients. (see screenshot)
What is your solution?

Send them to one email node. You can set the recipient in the message to the email node.

What node is that?

As far as I remember, node-red-node-email does not actually make a connection to the email server until it receives a message on its input.

node-red-contrib-email

Is there a reason that you are using that node rather than the node-red core supported node? If not then use the standard node.

However, even in that node, according to the docs, the recipient can be set in the message, so you should be able to use just one email node.

Do you have an example for me? But I still don't understand how you can create a link (Link Out??) from all flows and then create a separate flow (Link In from all flows and then send it via node-red-node-email. Is that correct? How can I configure the individual recipients in all flows?
Basically MQTT - reading the data - notification with text and recipient - Link out
Next flow: Link-In -Send Mail with node-red-node-email.

Hey Colin,

I can use a change node to generate a text and a topic (see screenshot)
How can the recipient be configured here?

Add a Link out node on the tab you want to send the message from, give it a meaningful name. Add a Link In node on the new tab and link it to the Link Out. Connect the Link In to the email node.

See the docs for node-red-node-email:
The default message recipient can be configured in the node, if it is left blank it should be set using the msg.to property of the incoming message. If left blank you can also specify any or all of: msg.cc , msg.bcc , msg.replyTo , msg.inReplyTo , msg.references , msg.headers , or msg.priority properties.

Set msg.to in the change node. If you want to use the other email node then look at its docs.

1 Like

I understand that. So I have a separate tab with link in and email node. So far so good. But I have different recipients.
Flow 1 passes via link out to a separate tab after link in and then to the email node.
Flow 2 is the same scenario
Flow 3 and so on
Where is the recipient defined? That can't happen in the email node because I have about 25 different recipients but only 1 email node. The msg.cc and msg.bcc functions don't interest me.

You are not limited to setting msg.topic and msg.payload in the change node.
You can add as many message properties as you like, including msg.to.

1 Like

hi jbudd,

I tried that in the change node. msg.to is not displayed at all (see screenshot).Only topic, tofront and responseTopic. But if I can still do it like that and use msg.cc here too
and under to the value: a/z [email address] then it's not a problem. Then I understand it now. Then I can really solve the problem with Link IN/OUT. Thanks. Feedback will follow if it works.

The dropdown offers you suggestions not the only available options.

Just type in "to" and ignore the dropdown.

1 Like