# ./launcher start app - does not run (need to re-setup SMTP)

**URL:** <https://meta.discourse.org/t/launcher-start-app-does-not-run-need-to-re-setup-smtp/240374>\
**Category:** Self-hosting\
**Created:** [September 29, 2022, 8:43am UTC](https://meta.discourse.org/t/launcher-start-app-does-not-run-need-to-re-setup-smtp/240374 "2022-09-29T08:43:17Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [September 29, 2022, 8:52pm UTC](https://meta.discourse.org/t/launcher-start-app-does-not-run-need-to-re-setup-smtp/240374/13 "2022-09-29T20:52:17Z")

</div>

> [@ideatank](#):
>
> I also see all messages are queued but not sent " `250 Ok: queued as`"

SMTP is transactional, so from the perspective of:

- your system: “the message is sent, the remote system queued it as ABC1234567” → “the message was handed off to the next responsible MTA”
- sendgrid: “the message was accepted and queued with queue ID ABC1234567”

What you don’t (can’t) see is the next step where another agent on sendgrid’s system goes through the queue, picks up your message, and hands it off to the next MTA.

The queue identifier helps with tracking - if it were to get lost you could go to sendgrid’s sysadmin and ask “what happened to queue ID ABC1234567 after your system accepted it?”

---

_[View the full topic](https://meta.discourse.org/t/launcher-start-app-does-not-run-need-to-re-setup-smtp/240374)._