Intermittent error 403 with Email node


NR v2.2.2
node-red-node-email 1.14.0

I've been getting intermittent faults sending emails recently. ~3/10 nearly identical emails fail. Not sure what the cause is. Caught the error using the catch node. As a workaround I added an extra minute delay once a 403 is caught and that usually solves the issue after a retry or 2.

I've unchecked "check server certificate is valid" because the error mentions TLS, but that did not work.

It does not seem to affect text-only emails, rather only emails with attachments, but I'm not sure because of the intermittent nature.

These emails use an attachment specified like this:



{"message":"Error: Invalid status code 403","source":{"id":"28531485.20474c","type":"e-mail","name":"","count":1},"stack":"Error: Invalid status code 403\n    at ClientRequest.<anonymous> (/home/admin/.node-red/node_modules/node-red-node-email/node_modules/nodemailer/lib/fetch/index.js:213:23)\n    at ClientRequest.emit (events.js:400:28)\n    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27)\n    at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)\n    at TLSSocket.socketOnData (_http_client.js:515:22)\n    at TLSSocket.emit (events.js:400:28)\n    at addChunk (internal/streams/readable.js:293:12)\n    at readableAddChunk (internal/streams/readable.js:267:9)\n    at TLSSocket.Readable.push (internal/streams/readable.js:206:10)\n    at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)"}

I don't know what might be causing the problem for you, but you might be interested in this flow which provides guaranteed delivery, with queuing of requests and retries till it works.

Thanks Colin. I will implement this.

I got a 404 as well. It seems to have been caused by an error on the mail server side.

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