I’ve managed to follow Terry’s videos and successfully use a Rio & node-RED to send a file to my gmail address. Yay! But here is the but… I’ve been asked to get it sent to an (outlook) email address that ends in @nrcan-rncan.gc.ca; and it’s not working.
I thought I had read somewhere that the rio / EPIC will only send to gmail & yahoo accounts, but now I can’t find it anywhere so not sure if that’s even true. The Rio user guide & the knowledge base articles / technical notes I can find seem to pertain to the changes where you need to make the application password (which I’ve done), and nothing about how the “To:” field works.
I am also not a network person, so from a little bit of googling it seems like the smtp should stay as the gmail server, since that’s how I’m sending it, and the port can only be a few specific ones that don’t necessarily seem tied to the email account type.
But that means I don’t know what to change / configure to get it to send to a non-gmail account.
I asked our IT guy and he says, “it doesn’t make sense, the system is sending an email just like you would if you were using gmail in the web browser”, which I take to mean that it should work using anything after the @?
If it helps, this is the error message I’m getting from the gmail send account:
Nope, not true. We recommend using them as your email servers, but you can use outlook with the help of the IT guys ad’minig the server. (You usually have to whitelist the device sending the email).
Before we get to the meat of the issue… Lets be clear… The email config in your screen shot is primarily for the SERVER, not who you are sending the email to.
Yes, you can put the recipient in up the top, or you can leave it blank and send it via the msg.payload, but the guts of that config dialog is for the email server that will be used to send the email.
So, in regards to your specific problem address, can you send it via gmail.com in a browser that is logged in as your ‘Userid’??
If not, there is your first problem to solve.
If so, then we can get back to Node-RED…
Once you are sure you can send it via a browser, can that person send a reply so you can look at the email headers and just be sure that their server address is correct?
I’m wondering if that email address you have issues with is an alias.
Lastly, is your gmail account setup to use 2FA (two factor authentication) and you have generated an application specific password and are using that password for the Node-RED config?
If not, that might be the issue. Your gmail will only send emails to very specific address in that case, it’s not until you setup the account to be 2FA and get that app-specific password in play will it send emails more freely.
If you log into the sending account directly and try to message an @nrcan-rncan.gc.ca address, do you get the same blocked message?
i.e, is the sending account blocked entirely, or is it the Node-RED send that’s causing the issue?
My best guess is that there’s a blacklist or whitelist on the receiving end, but it’s hard to tell for sure without knowing more about how that account / organization is configured.
Confirmed yes, I can send to & from the @nrcan address without issue, through a browser, from the same gmail address I’m using as the userID in NodeRED
I checked the reply, and the server address matches.
The only thing that stands out to me in the email header is that it does specifically say “Security: Standard encryption (TLS)”; so maybe I will try changing the port to 587 instead of 465 and see if that works.
and Yes to the 2FA & application specific password - I did all of that setup according to Terry’s walkthroughs; I for sure have the app specific 4 x4 letter key in the password field.
Ok, when I do port 587 instead, nodeRED immediately gives me a send failed error.
It says: Error: 306181968:error:1408f10b:SSL routines, wrong version number.
