> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/communications-and-notifications.md). # Communications & Notifications Durable in-app messaging, SMTP delivery, push hints, and optional subscriber synchronization. ISLAMU Event decouples authoritative in-app notification state from transient transport hints, SMTP email delivery, and external newsletter synchronization. Each communication channel maintains its own independent readiness probes, retry mechanisms, and recovery runbooks. *** ## In this Section * [**In-App Notifications**](/islamu-event/documentation/readme/communications-and-notifications/in-app-notifications.md) — Authoritative user notification inbox, SSE badge refresh hints, and Web Push notifications. * [**Email SMTP**](/islamu-event/documentation/readme/communications-and-notifications/email-smtp.md) — MailKit transactional dispatch outbox, SMTP configuration, transient retry loops, and Mailpit testing. * [**Listmonk Integration**](/islamu-event/documentation/readme/communications-and-notifications/listmonk.md) — Automated attendee newsletter synchronization into self-hosted Listmonk mailing lists. *** ## Channel Authority Boundaries * The **In-App Inbox** is the primary source of notification truth; Server-Sent Events (SSE) and Web Push are merely lightweight hints directing the client to refresh its inbox. * **SMTP Email** is reserved for explicit transactional intents (e.g. ticket delivery, password reset, payment receipts) and is not mirrored for every minor in-app event. * **Listmonk** receives opt-in newsletter subscriber syncs; it never acts as a platform notification store. *** ## Related Guides & Next Steps * [**Ticketing & Check-In**](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md) — Ticket delivery and lost-ticket capability emails. * [**Environment Variables Reference**](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#6-email-smtp--outbox) — SMTP host, port, credentials, and TLS dials. * [**Secrets Management**](/islamu-event/documentation/readme/configuration-and-operations/secrets.md) — Securely store SMTP passwords and Listmonk API tokens. * [**Webhooks & Callbacks**](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md) — Distribute operational events to external webhook subscribers. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://islamu.gitbook.io/islamu-event/documentation/readme/communications-and-notifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.