Overview

The goal of this appjar is to provide a centralised tool for composing, queuing, sending, and tracking outgoing emails from within the application.

Sending emails is a common requirement in enterprise applications: password resets, notifications, reports, and system alerts all depend on reliable email delivery. Implementing and maintaining this functionality — including retry logic, attachment handling, and delivery tracking — adds recurring effort to every project. The Email Manager appjar covers this requirement with a ready-made administration interface that manages the full lifecycle of an outgoing email.

Email Lifecycle

An email progresses through a defined set of statuses from the moment it is composed to the moment it is delivered. After being created, an email can be sent immediately or placed in a queue to be delivered by a background mail sender service. If delivery fails, the email transitions to a failed state and can be retried. This lifecycle model gives administrators full visibility and control over every email the application attempts to send.

Composition and Delivery

The Email Manager supports all standard email addressing options, including recipients, carbon copy, and blind carbon copy. A message body can be sent as plain text or as HTML, and HTML bodies can be previewed before delivery. Up to ten file attachments can be included per email, each up to 200 MB. When the application is configured with multiple sender addresses, the sending address can be selected at composition time.

Saving an email does not send it immediately. Administrators can choose to send it on demand or add it to the delivery queue, allowing for review before dispatch.