Mails

The Mails resource provides a paginated list of every email that your application has dispatched. Use this page to confirm successful delivery, diagnose failed sends, and navigate directly to the context (request, job, command, etc.) where each email was generated.

Navigation: Access Mails via the sidebar under the “Mails” section.

---

1. Mails Index Table

By default, the Mails page displays 25 entries, ordered by Sent At in descending order (most recent first). Scroll down and click Load More to retrieve additional entries.

1.1 Columns

1. Sent At

   • Timestamp when the email was sent (e.g., 2025-05-30 16:22:45).

2. Mailable

   • The class or identifier of the Mailable (e.g., WelcomeEmail, PasswordResetMail).

3. To (Email Address)

   • The recipient’s email address (e.g., [email protected]).

4. Subject

   • The subject line of the email (e.g., Welcome to Our Service!).

5. Occurrence

   • The context that triggered the email, such as:
     • Request (e.g., Request #1023)
     • Command (e.g., Command newsletter:send)
     • Scheduled Task (e.g., Task daily:report)
     • Queued Job (e.g., Job SendInvoiceEmailJob)
   • Clicking the occurrence link navigates to the corresponding details page (e.g., Request Details), where you can see the full event timeline surrounding this email send.

Note: If the email was dispatched outside of those contexts (for example, in a global bootstrapping routine), Occurrence may display “System” or “Boot.”

---

2. Filters

Above the Mails table, you’ll find controls to refine the displayed entries:

1. Search (Mailable / Subject)

   • A free-text search field that matches against both the Mailable name and Subject line.
   • Partial matches and substrings are supported (e.g., searching “reset” will match PasswordResetMail and subject lines containing “reset”).

2. Date Range

   • Select Start Date & Time and End Date & Time to show only emails sent within that window.

Tip: Combine Search and Date Range filters to locate all welcome emails sent during a specific campaign period.

---

3. Load More

• The Mails table initially shows the 25 most recent entries.
• Click Load More at the bottom to fetch the next batch of 25 emails, ordered by Sent At descending.
• This incremental loading ensures fast initial page rendering while still giving you access to your full email history.

---

4. Best Practices

• Confirm Critical Sends

  • Use the Search filter to find transactional mailables (e.g., InvoiceMail, OrderConfirmationMail) and verify that they were sent as expected.

• Audit Recipients

  • Search for specific recipient addresses or domains (e.g., @example.com) to confirm that batch emails reached the correct audience.

• Diagnose Silent Failures

  • If an expected email doesn’t appear in the index, check the associated occurrence (request, job, or task) for errors or exceptions—often visible in Logs or Exceptions.

• Track Seasonal Campaigns

  • Narrow your Date Range to the timeframe of a marketing campaign to ensure all scheduled newsletters were dispatched.

• Correlate with Parent Context

  • Click the Occurrence link to jump directly into the detailed timeline of the sending event (request, command, etc.) and review related queries, logs, or errors.

• Monitor Delivery Trends

  • Over time, watch for spikes or drops in email volume by loading additional pages and filtering by date. Sudden changes may indicate system misconfigurations or SMTP server issues.

By leveraging the Mails index, its filters, and occurrence links, Laritor helps you ensure that every email—transactional or campaign—reaches the intended recipient and that any sending issues can be traced back to their origin.