Email delivery, attachments and read receipts

Handle Letter Manager email send failure

Diagnose an email_sent=0 record after the PDF and history row were created.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Sent Letters History → Internal Full View; Admin Area → Setup → Settings → Email

Before you begin

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide covers

Diagnose an email_sent=0 record after the PDF and history row were created. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm a target email was available.
Test the CRM SMTP configuration.
Review the module error_log and host mail logs through authorised access.
Correct the issue.
Use Resend Email and verify the stored send result.

Fields, choices and supported possibilities

Action scopeDiagnose an email_sent=0 record after the PDF and history row were created.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Internal Full View; Admin Area → Setup → Settings → Email

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Code-backed validations and workflow rules

The module logs send result and email debugger headers to its error_log file.
On failure, email_sent remains 0 and email_sent_at is null.

Expected result and verification

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.