# Continue flow after mail queuing

**URL:** <https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080>\
**Category:** General\
**Tags:** node-red-node-email\
**Created:** [4 January 2026 08:06 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080 "2026-01-04T08:06:59Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![beatstieger](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/beatstieger/32/104893_2.png) [@beatstieger](https://discourse.nodered.org/u/beatstieger)\
**Post date:** [4 January 2026 08:06 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/1 "2026-01-04T08:06:59Z")

</div>

Using node-red-node-email, I need to wait till the mail has been successfully accepted by the mta bevor continuing my flow. As the sending node seems not allow to continue flows, I tried using the status node as workaround, which unfortunately does not contain info which can be linked to the initial msg/flow. Nor the docs nor the forum had useful information about this. May someone point me to further information / a working example?

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [4 January 2026 08:39 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/2 "2026-01-04T08:39:41Z")

</div>

Send yourself a BCC and then have a mail receiver flow that gets triggered once the BCC mail arrives in your mailbox 😉

I don't think there is a mail received node (which actually would be a nice thing) and this idea isn't to be taken too seriously.

> [@beatstieger](#):
>
> accepted by the mta bevor continuing

But isn't that the point where the send-mail node sends its message, i.e. after successful submission doesn't the node send a message? I'm not familiar with the email node.

> [@beatstieger](#):
>
> a working example

You could also provide what you have done so far to make it easier to figure what your using to send emails and how you're doing it.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2026 09:32 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/3 "2026-01-04T09:32:21Z")

</div>

The node [@colinl/node-red-guaranteed-delivery](https://flows.nodered.org/node/@colinl/node-red-guaranteed-delivery) includes an example of its use for guaranteeing the delivery of email to the MTA. It copes with queuing and retry on failure.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 January 2026 10:17 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/4 "2026-01-04T10:17:26Z")

</div>

Wont a **complete** node do the trick for you?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/5/65c86dad0e5f9ab224215f3bac3d64d3775950ac.png)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [4 January 2026 11:49 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/5 "2026-01-04T11:49:58Z")

</div>

> [@Colin](#):
>
> The node [@colinl/node-red-guaranteed-delivery](https://flows.nodered.org/node/@colinl/node-red-guaranteed-delivery) includes an example of its use for guaranteeing the delivery of email to the MTA. It copes with queuing and retry on failure.

Isn't the issue that the MTA/Mail server may not actually provide the information? I don't think that SMTP sends have anything that responds once the MTA has actually _sent_ the email? Though I may well be wrong, been a long time since I did much with that side of things.

The BCC idea seems a more robust solution. Though you would also need to take account of never receiving any response so you would need a timeout as well.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [4 January 2026 12:07 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/6 "2026-01-04T12:07:12Z")

</div>

> [@TotallyInformation](#):
>
> MTA has actually _sent_ the email

Indeed it doesn't, SMTP does not support that. But I think the OP only wants to know that the MTA accepted the email for delivery and my suggestion with BCC would actually be a step beyond what they want because that then is notification of email delivery.

> [@TotallyInformation](#):
>
> you would need a timeout as well.

Or you just accept it as being event driven programming and the event never happened - depends on the use case.

---

<div class="post-metadata">

**Author:** ![beatstieger](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/beatstieger/32/104893_2.png) [@beatstieger](https://discourse.nodered.org/u/beatstieger)\
**Post date:** [4 January 2026 12:17 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/7 "2026-01-04T12:17:37Z")

</div>

Thx for your replies \<3, I'll take a closer look as soon as there is more time, and maybe also provide an example if still needed.

To precise myself: I only count on the MTAs reply saying something like '250 message queued'. I know, he/she won't tell me when it is delivered into the mailbox. It is OK to know, the message has been accepted by the MTA, independent of what is going in later with it.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2026 12:17 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/8 "2026-01-04T12:17:49Z")

</div>

> [@TotallyInformation](#):
>
> Isn't the issue that the MTA/Mail server may not actually provide the information?

It guarantees that the message has been received by the mail server. Not that it has been send to the recipient.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2026 12:18 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/9 "2026-01-04T12:18:18Z")

</div>

> [@Steve-Mcl](#):
>
> Wont a **complete** node do the trick for you?

It is necessary to deal with errors too.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2026 12:26 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/10 "2026-01-04T12:26:45Z")

</div>

> [@Steve-Mcl](#):
>
> Wont a **complete** node do the trick for you?

To amplify my previous post, the email node is well behaved in that it triggers either a Complete or a Catch node, not both. So it is easy to know what has happened. The example with the guaranteed delivery node handles the queuing of messages and retries in case of errors, such as network failures.

---

<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:** [23 January 2026 04:50 UTC](https://discourse.nodered.org/t/continue-flow-after-mail-queuing/100080/11 "2026-01-23T04:50:34Z")

</div>

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