Email delivery, attachments and read receipts

Handle a skipped Letter Manager enclosure

Respond correctly when the optional file fails without assuming the letter failed.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → submit letter → warning alert

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

Respond correctly when the optional file fails without assuming the letter failed. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Read the warning reason: upload error, type, size, invalid upload, folder writability or save failure.
Open Sent Letters History and verify whether the letter/PDF/email processed.
Correct the file or storage issue.
Use a controlled new letter or resend strategy after confirming what the original recipient received.

Fields, choices and supported possibilities

Action scopeRespond correctly when the optional file fails without assuming the letter failed.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → submit letter → warning alert

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 enclosure helper returns without aborting generate_and_send.
A warning does not mean the generated PDF was skipped.

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.